Alcohol delivery must gate the ordering flow, not just a splash page

The requirementstatement

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

Severityseverity
BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
checkout and ordering flow
Where it liveslayer
WebsiteWEBSITE
How Ekas settles itdetectability
AI · crawlCRAWL
Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
What the fix involvesfailureClass
Fix the websiteTERMINAL_WEBSITE
The fix lives on your site. No amount of rewording the form clears it.
Who requires itauthorities
Twilio
When it appliesapplicabilityText
Applies when the vertical is alcohol_delivery.

Why this rule existsrationale

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 itremediation

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 codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

ProviderCodeResubmit
Twiliogen230956Yes

Notesnotes

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.

Rules you will hit next

Other website rules at the same severity. A registration is judged as a whole, not rule by rule.

All website rules

WEB-111 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.