Shopify age verification: gates, checks and order flow

Choose a Shopify age-verification method around the actual product and region, then check access, checkout, failed verification and customer-data handling.

Shopify age verification needs a method that meets the rules for your product and destination, with purchase controls that stop an unverified customer. A storefront age gate records what someone says about their age. A verification check establishes an age result using the chosen evidence. Delivery can require another check before you hand over the goods.

Choose the method by the decision it must make: whether this customer can buy this restricted product through this route. Then test the allowed purchase and the purchase you must stop, through to fulfilment.

Define the product, region and required control

Write down what you sell, where you sell it and how the customer receives it before choosing an age-control app. Include your business location, the delivery destination and whether collection or same-day delivery is available. A rule for alcohol in one state does not establish the rule for another product or jurisdiction.

Shopify’s alcohol guidance directs Australian sellers to the applicable state or territory laws. It identifies preventing purchase and receipt by people under 18 as a common Australian alcohol requirement. That is an alcohol-specific reference, not a universal minimum age for every restricted product.

Separate the controls by what they establish:

  • An age gate asks the visitor to confirm an age or enter a date of birth. A self-declared answer alone supplies no independent evidence.
  • An age-verification method checks the evidence accepted for the applicable requirement and returns a result. Define which products and customers that result covers.
  • A delivery-stage control determines whether the goods can be handed to the recipient. An approved purchase does not remove a separate handover requirement.

For example, New South Wales same-day alcohol guidance requires age checks for purchasers and recipients. Its purchase options include an accredited digital identity service or AI-based verification of acceptable proof of age. It also permits a purchaser statement that they or their nominated adult will present proof of age at delivery. Drivers must follow the recipient and identification requirements at handover. A generic “I’m over 18” button does not capture that complete process.

Record the chosen requirement as an operating instruction. Name the evidence or declaration required, when it must be obtained and who can release the order. Keep alcohol promotion and shopping answers within their separate alcohol advertising boundaries too.

Choose the supported store method

Use a storefront prompt for the declaration it actually collects, and add purchase enforcement wherever the required result must control checkout. Choose an app or service only after its documentation identifies the evidence checked and the result your store receives.

Compare the control you receive

MethodWhat you can observeBoundary to establish
Storefront age promptA visitor submits an answer or birth dateWhether direct product links and other buying routes reach the prompt
Verification serviceA documented age result from the serviceAccepted evidence, supported countries and how the result reaches checkout
Cart and checkout validationA purchase is allowed or blocked by a ruleWhich result the rule trusts and which sales routes it covers
Delivery checkThe authorised recipient satisfies the handover processCourier instructions, refusal handling and required records

Shopify supports app-based cart and checkout validation. Public apps built with Shopify Functions are available from Basic upwards. Custom apps using Functions require Shopify Plus. Extensions on checkout’s information, shipping and payment pages also require Plus. A visible checkout field and a rule that blocks checkout are different capabilities.

For a compatible validation app, open Settings > Checkout > Checkout rules, then add and configure its rule. Activate it and save. Shopify also has a setting to block checkout when the app encounters a problem. Decide whether the configured error behaviour preserves the required restriction. Shopify’s documentation says draft-order validation can be overridden, so restrict that override in your staff procedure.

The Cart and Checkout Validation Function API supports server-side checks, including accelerated checkout. Its surface list excludes point of sale, recurring subscription orders and order edits. A checkout validation therefore needs a separate control for any excluded route you use.

Before installation, confirm the app’s supported plan and verification countries. Establish whether it requires sign-in, which customer-account version it supports and how it behaves on phones. Identify browser permissions needed for document capture and the supported alternative when a customer cannot use them.

Check sales-channel compatibility separately. Shop’s eligibility requirements include restrictions on age-verification apps. Selling through Shop and using Shop Pay on your online store are different routes. List each route you actually enable and assign its control.

Verify allowed and stopped purchases

Run fictional cases through product access, cart and checkout, then inspect the resulting order and fulfilment state. Use the provider’s test mode or approved test identities. Never submit invented identity documents to a live verification service.

Fictional purchase cases

The following cases describe expected outcomes to check, not completed tests. Assume a restricted product requires an approved age result before purchase and a separate recipient check at delivery.

Fictional caseProduct and cart checkCheckout result to requireFulfilment outcome
Eligible customer with an approved resultCorrect restricted item remains identified in a mixed basketPurchase proceeds with the result tied to the relevant customerOrder carries the required delivery instructions
Ineligible customerA dismissed prompt does not remove the item’s restrictionRestricted purchase stopsGoods remain unreleased
Check fails to establish ageCustomer sees a recovery route without being labelled underageRestricted purchase remains blockedStaff cannot treat the failed attempt as approval
Customer closes verification or loses connectionReturning to the basket preserves the restrictionMissing or pending result prevents purchaseNo unverified order enters automatic fulfilment
  1. Open a direct link to the restricted product in a fresh browser session. Add it to the cart and confirm that its restriction follows the item.
  2. Try every enabled checkout entry, including an accelerated button that bypasses the cart page. Confirm that a missing result stops the restricted purchase.
  3. Complete an approved test check. Reload and inspect the saved order, including the customer reference and the delivery instruction your process requires.
  4. Change customer state. Sign out, switch accounts and try another device. Confirm that a result is reused only under the method’s documented identity and expiry rules.
  5. Change the basket after verification. Add another restricted product or change the destination and confirm the purchase is assessed against the new requirements.
  6. Exercise the app-error path and a staff-created draft order. Inspect whether an override or integration failure can release the restricted goods.

Incorrect: a fictional customer closes the age prompt and completes accelerated checkout without the required result. Correct: the purchase remains stopped until the chosen process establishes the required result. Save the observed order state for each case, not just a screenshot of the prompt.

Keep automatic fulfilment off for any route whose restriction fails these checks. For a delivery-controlled sale, pass the nominated recipient instructions to the courier and rehearse refusal handling before enabling that route.

Control customer data and recovery

Choose the least intrusive evidence that satisfies the actual requirement, and document where each piece of information goes. A provider-hosted check can still return personal information to your store.

For organisations covered by the Australian Privacy Principles, the Office of the Australian Information Commissioner’s age-assurance guidance explains data-minimisation and transparency duties. Its guidance covers inputs such as document images as well as the resulting age assertion. Temporary processing can still count as collecting information.

Review the chosen provider’s privacy terms alongside its app permissions. Identify the raw evidence collected, the result stored in Shopify and any information exposed in order notes or customer records. Establish retention periods and deletion procedures. Limit staff access to the result and records their job requires, subject to any mandatory record-keeping obligations.

Show the collection notice before the customer submits evidence. State who performs the check, why information is collected and where to find the retention and complaint process. Establish which processing requires consent under the applicable rules. Keep marketing permission separate from the age-check process.

A failed check must leave the customer a usable next step. Show the documented retry path for an unreadable image or interrupted session. Direct unresolved cases to staff who can explain an accepted alternative without guessing eligibility. Keep a refusal distinct from a technical failure: neither supplies an approved age result.

If a purchase cannot proceed, explain how to abandon the attempt. Where payment has already been taken, use the store’s documented cancellation and refund process while keeping the goods unreleased. Before reopening a failed route, repeat its stopped-purchase case and inspect the saved order and fulfilment state.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup