# WEB-111 — Alcohol delivery must gate the ordering flow, not just a splash page

> An alcohol delivery brand must present the age gate on the ordering flow itself, not only on a marketing splash page.

- **Rule ID:** WEB-111
- **Layer:** Website (`WEBSITE`)
- **Checks:** `checkout and ordering flow`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the crawled website or policy page
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** Twilio
- **Applies:** Applies when the vertical is alcohol_delivery.
- **Canonical URL:** https://ekas.io/rules/10dlc/website/web-111/

## Why this rule exists

Delivery is the case where the gate has to hold, because the transaction ends with alcohol arriving at a door rather than with someone standing at a counter. A splash gate on the marketing site is satisfying to build and does nothing for the ordering app or the checkout subdomain, which is usually a different system entirely.

## How to fix it

Add the date-of-birth gate to the ordering flow — the cart, the checkout, and the app — as well as to the marketing site, and verify age again at handover. Done when the order path itself refuses an under-21 date of birth.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen2) | `30956` | yes |

## Notes

Twilio scopes 30956 to "all linked websites and opt-in flows", which is what makes a splash-page-only gate insufficient here. Tagged to the alcohol_delivery vertical per the catalog condition; the general alcohol threshold rule is WEB-112 and applies whether or not delivery is involved.