Guides

How to Translate Shopify Store Age Verification and Restricted Product Compliance Pages for International Markets

Selling age-restricted products internationally — alcohol, tobacco, CBD, vaping, adult content, certain pharmaceuticals — means your age gate is a legal document, not a UX detail. Getting the translation wrong can mean a gate that fails to satisfy local regulations, or one that confuses customers badly enough that they abandon before they ever see a product.

This guide focuses specifically on the compliance copy: the strings customers actually read, the thresholds you declare, and the workflow for keeping those translations accurate as regulations evolve.

Why Shopify Age Verification Translation Is a Distinct Problem

Most translation guides treat pages as content. Age verification pages are closer to terms of a contract. They make a factual claim ("you must be 18 to proceed") and record a user's affirmative consent. If that claim is wrong for the jurisdiction — or phrased so awkwardly that a user doesn't understand it — you have a compliance gap.

Three things make this harder than translating a product description:

  • Age thresholds vary by country and by product category. You cannot use a single global string.
  • The legal standard for "clear consent" varies. Some regulators expect explicit, affirmative language; others have guidance on what passive or pre-ticked gates will and won't satisfy.
  • Mistranslation carries different stakes. A mistranslated product description costs you a conversion. A mistranslated age gate can be cited in an enforcement action.

The Age Threshold Problem: Country- and Category-Specific Minimums

Before you write a single translation, map your thresholds. Do not assume 18 applies everywhere. Here are representative examples — always verify against current local law or qualified legal advice, because these rules change:

Alcohol

  • USA: 21
  • UK, most EU countries: 18
  • Germany: 18 for spirits; 16 applies to on-premises consumption of beer and wine under adult supervision — this does not apply to online retail sales, where 18 is the operative threshold for all alcohol purchases
  • Japan: 20 (the 2022 Civil Code reform lowered the general age of majority to 18 but explicitly left alcohol and tobacco at 20)
  • South Korea: 19

Tobacco and nicotine/vaping

  • USA: 21 (federal, as of 2019)
  • UK, Australia, most EU: 18
  • Japan: 20

Cannabis/CBD — thresholds and legality vary enormously. In some jurisdictions online sales are prohibited entirely regardless of age. Treat this category as requiring individual legal review per market.

The practical implication: if you sell alcohol and tobacco and ship to Japan and the USA, you need locale-specific threshold values in your gate strings, not a single translated template.

Storing Per-Locale Thresholds in Shopify

If your age gate is implemented via a Shopify page or a theme section, the most maintainable approach is to store the threshold as a metafield on the page or on a global shop metafield, then reference it in your Liquid template. In the Shopify admin, go to Settings → Custom data → Pages, add a metafield definition with namespace compliance, key age_threshold, type Integer, and mark it as translatable if you want locale overrides. Then in your Liquid:

{% assign threshold = page.metafields.compliance.age_threshold %}
{% if threshold %}
  {{ 'age_gate.must_be_years' | t: age: threshold }}
{% endif %}

Your locale .json file then contains the translatable string with the age as an interpolated variable rather than hardcoded into each translation. This means updating the threshold for Japan from 18 to 20 is a single metafield edit, not a find-and-replace across 47 translation files.

This approach is described in detail in the Shopify translationsRegister documentation and is the same pattern covered in our guide to translating Shopify metafields, metaobjects and custom data.

What a Compliant vs. Non-Compliant Age Gate String Looks Like

Here is a concrete before-and-after to illustrate the difference between a gate that is translated and one that is translated and compliant.

Original English (adequate):

"You must be 21 or older to enter this site. By clicking 'Enter', you confirm that you are at least 21 years of age."

Problematic French translation (machine output, unreviewed):

"Vous devez avoir 21 ans ou plus pour entrer sur ce site. En cliquant sur 'Entrée', vous confirmez que vous avez au moins 21 ans."

The language is grammatically correct. But "Entrée" is the French word for entry as a noun (as in a restaurant course), not the imperative Enter you'd put on a button. A French speaker clicking a button labelled "Entrée" would find it odd. More importantly, the gate still says 21 — which is correct for the US market this merchant originally targeted, but if this translation is shown to French customers purchasing alcohol, the French legal threshold is 18. A French customer who is 19 would be incorrectly blocked. This is a conversion loss, not a safety issue in this direction — but the logic also works in reverse if the threshold is too low.

Corrected French (reviewed, locale-specific threshold):

"Vous devez avoir 18 ans ou plus pour accéder à ce site. En cliquant sur 'Entrer', vous confirmez avoir au moins 18 ans."

Changes: threshold corrected to 18, button label corrected to "Entrer" (the infinitive verb, standard on French UI buttons), sentence restructured to match natural French phrasing for consent declarations.

This is the level of review that matters. AI translation will get you close, but a human reviewer — ideally a native speaker with awareness of the product category — should sign off on the final gate copy for each major market.

Practical Workflow for Translating Age Gates and Compliance Pages

Step 1: Audit every page that contains age-restricted or compliance content

Your age gate is the obvious one, but compliance copy often appears in other places:

Step 2: Separate threshold values from translatable strings

As described above, use variables in your translation strings rather than hardcoding numbers. This prevents the scenario where a developer updates the English threshold but the translated versions lag behind.

Step 3: Use AI translation as a first draft, not a final output

For general product content, AI translation quality is high enough that many merchants publish directly. For legal and compliance copy, treat AI output as a first draft that requires human review. The reason is specific: AI models are trained on general language distributions; legal phrasing patterns in, say, German consumer protection contexts are underrepresented in training data compared to everyday German text. The translation will be grammatically correct but may not carry the precise register or phrasing that local users expect from a compliance declaration.

StoreLingo's review queue lets you hold translated compliance pages in draft before they go live, which is the right workflow here — translate first, review before publishing, rather than auto-publishing directly. This is not unique to StoreLingo; any responsible translation workflow for legal content should include a review step.

Step 4: Maintain a glossary for regulated terminology

Terms like "age verification," "restricted access," "controlled substance," and product category names have specific legal meanings that should be translated consistently. A glossary prevents the situation where one page uses one translation of "age verification" and another uses a different term, creating inconsistency that could matter in a compliance review. StoreLingo includes a glossary feature for this purpose; if you manage translations manually, a shared spreadsheet serves the same function.

Step 5: Set up change detection

Regulations change. When Germany updated its age verification requirements for online alcohol sales, every merchant selling into Germany needed to update their gate copy. If you have a process for detecting when your source-language compliance page changes and flagging it for re-translation review, you catch these updates before they create a gap. This applies equally to your terms and conditions and return policy pages.

Don't Neglect the Restricted Product Listing Copy

If you sell restricted products, the compliance copy on the product listing itself matters too. This includes warning labels, regulatory disclaimers, and any certification statements. These should be treated with the same care as the age gate. Our guide to translating Shopify product descriptions without losing conversions covers the general translation approach; for restricted products, add a review step specifically for the disclaimer and warning sections.

Add StoreLingo on the Shopify App Store →

FAQ

Does Shopify's native translation system handle age verification pages automatically? Shopify's Translations API supports translating page content, including pages that contain age gate copy, but it does not know which pages are compliance-critical or which thresholds apply per locale — that logic is yours to implement. You still need to manage threshold values and review the translated strings for accuracy before publishing.

Should I use machine translation alone for my age gate copy? No. Machine translation is a useful starting point that will produce grammatically acceptable output in most major languages, but compliance and legal copy benefits significantly from human review by a native speaker familiar with the regulatory context. Publishing unreviewed AI-translated legal declarations carries real risk if a regulator scrutinises your localisation.

What happens if my age threshold is wrong in a translated market? If the threshold is too high for the local legal minimum, you block customers who are legally permitted to purchase — a conversion problem. If the threshold is too low, you are failing to enforce the local legal requirement — a compliance problem. Both scenarios are avoidable by mapping thresholds per locale before translation begins and using interpolated variables rather than hardcoded numbers in your translation strings.

Choose from 47 languages

StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.

Add to Shopify →