Supplement Labeling Requirements on Shopify: EU and US Rules at Catalog Scale

Your Product Page Is Part of the Label Now

For most supplement brands, compliance work ends at the physical label. A regulatory owner signs off the artwork — ingredient order checked, allergens emphasized, warnings present — the file goes to the printer, and everyone relaxes. Then the same product gets listed on Shopify by someone in ecommerce, working from an old spreadsheet, and none of that reviewed data makes the trip intact.

That gap matters because the law follows the product online. In the EU, Article 14 of Regulation (EU) No 1169/2011 covers distance selling directly: for prepacked food sold online, the mandatory food information — everything except the date of minimum durability — must be available before the purchase is concluded, on the material supporting the sale. Your product page is that material. In the US, the FDA has long treated website content that promotes a product as labeling under the FD&C Act, and its warning letters to supplement companies routinely cite product pages, not just printed labels.

So the data behind your listings is regulatory data. The rest of this guide covers what the EU and US rules actually require on a supplement listing, why catalogs drift out of compliance as they grow, and how to run labeling data as structured, quality-gated catalog fields on Shopify.

The EU Rules That Decide What a Supplement Listing Must Say

Food supplements are regulated as foods in the EU, which means two layers apply at once: the general food information rules in Regulation 1169/2011, and the supplement-specific requirements in Directive 2002/46/EC. Both produce data that has to appear, correctly, on every product page.

Ingredients in descending weight order

Article 18 of Regulation 1169/2011 requires the ingredient list to run in descending order of weight, as recorded at the time the ingredients were used in manufacture. The order is a legal fact about the formulation — and it changes. When a supplier swaps an excipient or a formulation is adjusted, the order can shift, and every copy of that list becomes wrong at once: the label, the product page, the print catalog, the retailer's copy.

The 14 allergens and the emphasis rule

Article 21 and Annex II list fourteen substances that must be emphasized within the ingredient list through a typeset that clearly distinguishes them — in practice, almost always bold: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphur dioxide and sulphites above 10 mg/kg, lupin, and molluscs. Note that the requirement is formatting, not just presence — an ingredient list that names milk but doesn't emphasize it is non-compliant, which makes this the most fragile piece of data in the catalog. A single plain-text copy-paste destroys it silently.

What the Food Supplements Directive adds

Directive 2002/46/EC layers supplement-specific particulars on top: the product must be sold under the designation “food supplement”, state the categories of nutrients or substances that characterize it, give the recommended daily portion, and carry three mandatory warnings — do not exceed the stated recommended daily dose, supplements are not a substitute for a varied diet, and keep out of reach of young children. Vitamin and mineral amounts are declared per daily portion, with percentages of the EU nutrient reference values (NRVs). Supplements are exempt from the standard back-of-pack nutrition declaration — this per-dose format replaces it.

Member states layer national procedures on top. Belgium is the clearest example: before a food supplement goes on sale there, it is notified to the FPS Public Health, Food Chain Safety and Environment, and the product receives a notification number — NUT, PL, or AS depending on its composition — that appears on the label. Belgian buyers and retailers actively look for it, which makes it one more field your catalog has to carry correctly on every listing.

Claims and languages

Two more layers round out the EU picture. Nutrition and health claims must come from the register authorized under Regulation (EC) 1924/2006 — a product description that promises anything beyond an authorized claim is a violation, no matter how carefully the label was reviewed. And under Article 15 of Regulation 1169/2011, mandatory information must appear in a language easily understood in each member state where the product is sold — a brand selling into Belgium typically needs Dutch and French, and adding Germany adds German. Every language is a full copy of every mandatory field.

The US Rules: Supplement Facts and Nine Major Allergens

US requirements are structured differently but create the same catalog problem. Dietary supplements carry a Supplement Facts panel under 21 CFR 101.36 — serving size, amount per serving, percent Daily Value where one is established, and other dietary ingredients — rather than the standard Nutrition Facts panel. The ingredient list follows the same descending-order-by-weight principle as the EU.

Allergens are governed by FALCPA, extended by the FASTER Act: nine major allergens — milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame — must be declared in plain English, either within the ingredient list or in a separate “Contains” statement. Unlike the EU, no bold emphasis is required — a detail that matters when one catalog serves both markets, because the two allergen declarations are different fields, not one field displayed twice. Structure/function claims add one more mandatory string: the verbatim FDA disclaimer that the statement has not been evaluated by the Food and Drug Administration.

Why Supplement Catalogs Drift Out of Compliance

None of the rules above is hard to meet on one product. The failure mode is scale. In a typical supplement business, the reviewed, legally correct data lives in the label artwork PDF — and everywhere else it exists as a re-typed copy: a master spreadsheet, the copacker's spec sheets, Shopify product descriptions, a trade catalog in InDesign, a distributor's onboarding form. Every re-type is an opportunity to reorder an ingredient, lose the bolding, or drop a warning, and nobody notices because nobody reviews product pages the way they review label artwork.

Run the numbers on a typical mid-size brand: 600 SKUs selling in three EU markets and one US store. Each SKU carries an ingredient list, an allergen declaration, three mandatory warnings, a daily-dose statement, and an NRV or Supplement Facts table — call it seven legally significant fields — in up to three languages. That is roughly 12,600 values that must each match the reviewed spec. At that scale, “someone checks every page by hand” is not a QA plan; it's a hope.

Reformulations make it worse. When a supplier substitutes an ingredient, the descending order changes, the allergen picture may change, and the update has to land in every copy at once. Brands that manage this in spreadsheets typically find pages that were missed months later — usually because a customer, a retailer, or an authority found them first.

Store Labeling Data as Structured Attributes, Not Website Copy

The structural fix is the same one we describe for cosmetics in our guide to INCI compliance on Shopify: stop treating regulated data as website copy and store it as structured product data, written once from the approved spec. In Catalog Hub, each product carries up to 250 attributes and metafields — all types, mapped to Shopify metafield definitions and synced both ways — so the ingredient list, allergen declaration, warnings, and dose data live as named fields on the product record, not as sentences buried in a description that each channel rewrites.

Once the data is structured, every downstream surface — the Shopify page, a second storefront, a channel feed, a print export, a retailer portal — draws from the same record. A reformulation becomes one edit that propagates, instead of a hunt across five tools. It's the same approach we apply for beauty and wellness brands, where INCI lists play the role that ingredient declarations play here.

Keep the Ingredient Order Intact from Spec Sheet to Product Page

To be clear about the division of labor: the legal ingredient order comes from your formulation, and your regulatory owner signs it off — no catalog tool decides that for you. The catalog's job is to make sure the approved list is entered once and never re-typed. That starts at intake: when the copacker or supplier sends specs as a CSV or spreadsheet, Supplier Bridge imports it with AI Column Mapping matching their column headers to your attributes, so “Zutaten” or “ingredient_list_v3” lands in the right field instead of being copied cell by cell.

For corrections that touch many products at once — a warning reworded by legal, a supplier's allergen note updated — Bulk Edit works like a spreadsheet across the whole catalog, with variants and inventory inline and a preview of every change before it saves. What used to be an afternoon of page-by-page edits in Shopify admin becomes one reviewed operation.

Make Allergen Emphasis Survive Every Copy-Paste

EU allergen emphasis deserves its own habit because the compliance lives in the formatting. Bold type survives nothing by default: paste an ingredient list into a plain-text field, a feed column, or an email, and the emphasis is gone with no error message. The only reliable pattern is to maintain the formatted ingredient list in exactly one place and let software carry it everywhere else.

In Apimio that place is the product's rich-text field, which syncs to the Shopify description HTML — the bolding your regulatory reviewer approved arrives on the storefront because no human re-typed it in between. Apimio doesn't choose which words to bold; your regulatory review does. What the catalog removes is the re-typing, which is where approved formatting goes to die.

Hold Non-Compliant Listings Before They Go Live

Structure gets the data right; enforcement keeps it that way. Quality Guard scores every product 0–100 on the Store Health screen — 74 checks across four pillars, with root-cause findings so a missing image surfaces as one fix, not five stacked penalties — and treats 80 as Channel-Ready. Fix cards show what each repair is projected to be worth for your store, in hours and revenue ranges computed from your own sales data.

The piece that matters most for a supplement brand is the Publish Gate. With the gate in enforce mode, products below your quality bar sync to Shopify as drafts, not live listings — an incomplete product page stops being “something someone should catch” and becomes something the system holds by default. There's a preview mode that shows what would have been held before you commit, and per-store overrides for markets with different bars. For most catalogs the gap this closes is exactly the one described in our guide to stopping bad product listings going live — except here, a bad listing isn't just a weak page; it's regulatory exposure. Quality Guard is included in Apimio Basic from $199/mo.

Among those checks are per-attribute format rules — preset formats or custom regex on specific fields — so a rule can require uppercase allergen names in the ingredient data, or the presence of a market-specific notification number such as Belgium’s NUT number, and the gate holds a product that fails the pattern just as it holds an incomplete one. That turns “the reviewed format made it to the listing” from a spot-check into a rule.

Selling in More Than One Market: Languages, Stores, and Diverging Rules

Multi-market selling multiplies every mandatory field by language, and EU language rules make that non-optional. Apimio's Multi-Language module (on the Advanced plan) holds per-language content on the same product record, so the Dutch and French versions of an ingredient list are siblings of the source field, not forks in separate spreadsheets. AI translations handle the volume — each one previewed before it saves and metered so you know what it costs — with the workflow covered in our guide to AI product translations for Shopify.

When the US store is a separate Shopify store, Store Sync manages both from one catalog with per-store overrides — the same product carries its EU fields on the EU store and its Supplement Facts and Contains statement on the US store, without duplicating the catalog. Identity matching keeps the two listings recognized as one product, so a reformulation still propagates to both.

One Catalog Feeding Web, Feeds, and Print

Supplement brands that supply retailers usually run a print workflow alongside the web — a trade catalog or price list built in InDesign, often with a data-driven plugin such as EasyCatalog. Apimio exports the catalog as CSV in seven formats, so the same structured fields that fill your product pages can feed the print pipeline as a file. There's no native EasyCatalog connection — it reads the exported file — but that's precisely the point: the print catalog stops being a separate, re-typed copy of the data and becomes another rendering of the reviewed record.

For advertising channels, Product Feeds (Advanced and Enterprise plans) generates Google Shopping and Meta catalog feeds hosted at a stable URL that the channel polls, refreshed on schedule. Because feeds are built from the same scored catalog, the quality checks sit upstream of the feed — the incomplete products that trigger disapprovals are the same ones the Publish Gate already flagged.

Sharing the Compliant Catalog with Retailers and Distributors

If you manufacture and sell through retailers, the compliance chain extends past your own store: every retailer re-typing your product data from a PDF is re-introducing the errors you just eliminated. The Trade Portal (available as an add-on on any plan) gives each retail buyer a branded space showing current catalog data — when a formulation changes, their view updates because it is your catalog, not a copy of it.

Line Sheets — included on every plan — build wholesale sheets from live catalog data: pick products, set wholesale price, MOQ, and case pack, and share a public buyer link or an email-gated PDF that captures the buyer's address as a lead. Wholesale fields are a special internal attribute class excluded from every Shopify sync path, every feed, and every public surface, so a trade price can't leak to your storefront by design. For label artwork and product imagery, the Image Library (Advanced plan) shares folders through secure view-only or download links instead of zip attachments — so a retailer always pulls the current approved artwork, not the version someone emailed last spring.

Moving Off a Legacy Catalog System

Many supplement manufacturers arrive at this problem from an older on-premise catalog system that was never built for Shopify — a tool that treats the store as one export target among many, with no view of what actually went live. The move is undramatic: export your products to CSV, import through Supplier Bridge with AI Column Mapping, and the two-way Shopify sync is live from day one. The 14-day free trial runs on the Advanced feature set, so scheduled imports, feeds, and multi-language are all testable against your real catalog before you commit.

Lock-in cuts the other way, too: your data stays exportable at all times — CSV in seven formats plus the API — and if a subscription lapses, automations pause rather than delete. Ecommerce and regulatory teams both get to keep their source of truth.

What Apimio Doesn’t Do

Honesty about boundaries, because compliance tooling attracts overclaims. Apimio is not a regulatory advisor: it doesn’t determine your legal ingredient order, decide which substances require emphasis, or approve your claims — your regulatory owner or consultant does, and their approved output is what the catalog preserves and enforces. Validation rules fire because you defined the pattern, not because the system read Article 18 — the legal judgment stays with your team, and Quality Guard makes sure the judgment, once made, is applied to every listing.

There's no live marketplace API sync — Google, Meta, Amazon, and Walmart are served as hosted feed files and URLs plus CSV export, and Shopify is the only live two-way sync. And print tools read exported files rather than connecting natively. If those boundaries fit how your team works — regulatory decides, the catalog preserves, the gate enforces — everything above works today.

Frequently Asked Questions

What legislation regulates allergen labeling on food products?

In the EU, Regulation (EU) No 1169/2011 — Article 21 with Annex II — requires fourteen listed allergens to be emphasized within the ingredient list. In the US, FALCPA as extended by the FASTER Act requires nine major allergens to be declared in plain English, in the ingredient list or a “Contains” statement. Apimio stores each market's allergen declaration as its own structured attribute so both versions stay correct on their respective storefronts.

When should precautionary allergen labeling (“may contain”) be used?

Precautionary allergen labeling is voluntary in both the EU and US, and should only be used when a risk assessment shows a real, unavoidable risk of cross-contamination that good manufacturing practice can't eliminate — not as a blanket disclaimer. Because it's a deliberate, reviewed statement, it belongs in a maintained catalog field; in Apimio it's an attribute applied to the affected SKUs, not ad-hoc text someone adds to descriptions.

Do allergens have to be in bold on supplement labels?

In the EU, yes in effect: Annex II allergens must be emphasized through a typeset that clearly distinguishes them from the rest of the ingredient list, and bold is the near-universal choice — including where mandatory information is provided online before purchase. The US has no emphasis requirement; it requires plain-English declaration instead. In Apimio the formatted EU ingredient list is written once and synced to Shopify, so the emphasis survives instead of being lost in a copy-paste.

What must a food supplement label include in the EU?

Beyond the general mandatory particulars of Regulation 1169/2011 (name, ingredient list, allergens, net quantity, business address and so on), Directive 2002/46/EC requires the designation “food supplement,” the characterizing nutrient or substance categories, the recommended daily portion, nutrient amounts per portion with %NRV, and three warnings: don't exceed the stated dose, supplements are not a substitute for a varied diet, and keep out of reach of young children. Apimio holds each of these as a structured field so no listing ships without them.

What goes on a US Supplement Facts panel?

Under 21 CFR 101.36: serving size, the amount of each dietary ingredient per serving, percent Daily Value where established, and other dietary ingredients — followed by the ingredient list and any FALCPA “Contains” statement. Structure/function claims additionally require the verbatim FDA disclaimer. In Apimio these live as per-market attributes on the product record, feeding the US store without disturbing the EU fields.

Does my Shopify product page have to show the same information as the physical label?

In the EU, substantively yes: Article 14 of Regulation 1169/2011 requires mandatory food information — everything except the date of minimum durability — to be available before the purchase is concluded, which for an online store means on or via the product page. In the US, the FDA treats promotional website content as labeling in enforcement practice. Apimio's Publish Gate makes this operational: listings missing required data are held as drafts instead of going live.