Retail buyers in food, beverage and beauty do not only care about price and pack size. They need allergen data wholesale catalogue fields they can trust before they commit stock—ingredients, major allergens, nutrition where required, and INCI for cosmetics—inside the same B2B catalogue they use to order.
Shelf life and FEFO inventory for food and beauty still matter. They are not enough on their own. If allergen and ingredient facts live only in scattered product specification sheets, retailers delay orders, mislabel shelf talkers, or refuse lines they cannot risk.
This guide covers what to expose in the catalogue and order flow, how EU-oriented disclosure differs for F&B versus beauty, and how structured data supports recalls and reorders.
What allergen data must appear in a wholesale catalogue?
Allergen data in a wholesale catalogue is the set of structured fields that tell a retailer which major allergens a product contains or may contain, plus the full ingredient context they need to sell or relabel lawfully downstream.
For prepacked foods and many beverages, buyers typically expect:
- A clear ingredient list with allergens emphasised the same way you would on a consumer pack
- Explicit flags or structured values for each relevant major allergen (present, not present, or may contain / cross-contact where you choose to declare it)
- A nutrition declaration where the finished product requires one for consumer sale
- Linked documents: product specification or tech sheet, and any short “may contain” policy note your quality team stands behind
- Stable product identifiers (including GTIN at unit and case level) so the same facts attach to every pack hierarchy
For non-prepacked or food-service style lines, retailers still need enough detail to brief their own staff and labels. The catalogue should not assume the buyer already has your latest kitchen or plant sheet.
Checklist icons for ingredients allergens and nutrition on a simple product card
Which EU rules govern allergens, nutrition and INCI for B2B sales?
Which EU rules govern allergens, nutrition and INCI for B2B sales? The main consumer-facing food framework is the EU Food Information to Consumers (FIC) regime, which sets out how foods are labelled—including a defined list of major allergens and rules for ingredient and nutrition information on prepacked foods.[1]
FIC is aimed at information to consumers, but wholesale brands still feel it every day: retailers can only meet their own duties if suppliers give them accurate, up-to-date product data. National food authorities also expect business-to-business information to be sufficient for the next operator in the chain.[2]
Beauty and personal care follow a different track. Ingredient listing for cosmetics is organised around INCI (International Nomenclature of Cosmetic Ingredients) under the EU cosmetics framework, not the food allergen list.[3] Fragrance allergens and other restricted substances have their own disclosure patterns; they should not be forced into a food-style “14 allergens” widget.
In short:
| Category | Core disclosure in B2B data | Typical anchor regulation mindset |
|---|---|---|
| Food & many drinks | Ingredients, major allergens, nutrition where applicable | FIC-style food information |
| Beauty / cosmetics | Full INCI list, responsible person / product identifiers as you already use | Cosmetics ingredient listing |
| Both | Spec/tech sheet, batch/lot traceability hooks, GTIN hierarchy | Commercial + traceability practice |
Do not blur the regimes in one free-text “allergens” box. Separate food allergen fields from cosmetic INCI fields so filters, exports and retailer portals stay honest.
How should brands structure allergen and ingredient fields in product data?
How should brands structure allergen and ingredient fields in product data? Treat them as first-class attributes in your product information model—ideally mastered in a PIM for wholesale brands—then publish them into the B2B catalogue and distributor portal.
A practical structure:
- Identity — SKU, name, brand, net quantity, and GTIN setup for units and cases so case pads inherit the same core facts as singles.
- Ingredient narrative — Full ingredient list text (language variants if you sell cross-border).
- Allergen matrix (F&B) — Controlled values per major allergen rather than one ambiguous sentence.
- Nutrition block (F&B) — Standard nutrition declaration fields for prepacked foods that need them, stored as data, not only a screenshot.
- INCI list (beauty) — Ordered INCI text plus any mandatory highlight ingredients your retailers expect to see early.
- Cross-contact / precautionary statement — Separate field with owner and last-reviewed date, so it is never mixed into “contains”.
- Documents — Current product specification / tech sheet, linked by version, not an old attachment buried in email.
- Change control — Effective date, reason for change (recipe, supplier, label artwork), and who approved it.
Keep free text for nuance; keep codes and booleans for search, compliance exports and portal filters. Retailers who run their own POS or label tools will thank you when your feed is predictable.
Structured database nodes linking a bottle SKU to ingredient and allergen fields
Where in the order flow should retailers see allergens and ingredients?
Where in the order flow should retailers see allergens and ingredients? At every decision point where a buyer might add, substitute or approve a line—not only after checkout.
Minimum surfaces:
- Search and browse — Filter or badge for key allergens; show INCI or “contains” summary on cards where space allows
- Product detail — Full ingredients, allergen matrix or INCI, nutrition, and downloadable tech sheet
- Cart and approval — Snapshot of allergen/INCI highlights so a second approver does not open ten tabs
- Order confirmation and documents — Same facts frozen to what was ordered, with product version or spec reference
- Reorder screens — Call out any formula change since the last order so repeat buys are conscious, not blind
A branded distributor portal works best when these fields are native catalogue data. Brandgate is one option for a branded B2B storefront aimed at wholesale for food & beverage and related categories, where approved retailers can see that product data in the same flow they use to order.
If sales reps still place orders on behalf of accounts, give them the same view. Shadow spreadsheets recreate the PDF problem inside the CRM.
What differs between food, beverage and beauty ingredient disclosure?
What differs between food, beverage and beauty ingredient disclosure? Food and most drink lines centre on FIC-style ingredient lists, the major allergen set, and nutrition declarations for prepacked consumer products.[1] Beverages may add alcohol strength, compounds, or other drink-specific particulars your quality team already prints on labels—mirror those in data rather than inventing a parallel story.
Beauty and personal care centre on INCI order and cosmetic compliance artefacts.[3] “Allergen” language means something different (for example fragrance allergens under cosmetics rules) and should not reuse food allergen enums. Shelf-life and period-after-opening style attributes often matter more than a nutrition table.
Shared needs across both worlds:
- Versioned product specifications
- Batch/lot traceability when something goes wrong
- Clear pack hierarchy (unit vs case) so warehouse and store teams talk about the same product
- Language handling for multi-market EU retailers
Health claims, organic marks, or other trust badges belong in their own fields. Mixing them into ingredient text makes updates fragile.
How do allergen updates and recalls connect to catalogue data?
How do allergen updates and recalls connect to catalogue data? Catalogue data is the source retailers will quote when a recipe changes or a withdrawal starts. If the live B2B catalogue still shows the old ingredient list, every open order and every reorder email becomes a dispute.
Operational link-up:
- Recipe or supplier change — Update PIM/catalogue fields and spec version first; then refresh portal visibility and notify active buyers
- FEFO picking — Allergen identity must match the lot you ship; date codes alone do not fix a wrong ingredient story
- Recall or withdrawal — Use the same GTIN and lot hooks you already publish so notices map to catalogue SKUs; see a practical walk-through of the wholesale product recall process in the EU
- Post-recall — Mark superseded specs read-only; keep the historical version attachable to past orders for audits
A parcel and an invoice joined by one continuous looping line to a recall notice
What breaks when allergen data lives only in PDFs or spreadsheets?
What breaks when allergen data lives only in PDFs or spreadsheets? Everything that depends on a single source of truth.
Common failure modes:
- Stale attachments — Buyers order from last year’s tech sheet still sitting in a shared drive
- Copy-paste drift — Sales edits a cell for one retailer; finance and warehouse never see it
- No pack hierarchy — Case GTIN and unit GTIN disagree on ingredients because only one row was updated
- Slow onboarding — New retailers wait on email threads instead of self-serve catalogue checks
- Weak recall reach — You cannot filter “who bought SKUs containing X” without forensic spreadsheet work
- Portal mistrust — If the web shop shows less than the PDF, serious buyers ignore the shop
Spreadsheets are fine as a temporary extract. They are a poor master for allergen labelling wholesale B2B duties that change with every reformulation.
How does rich product data improve retailer onboarding and reorders?
How does rich product data improve retailer onboarding and reorders? It shortens the path from “interest” to “first order” and makes the second order safer.
New accounts can validate range fit against their own allergen policies without a week of back-and-forth. Existing accounts reorder faster when product pages still answer ingredient questions, and when change banners explain what moved since last time. Your team spends less time resending the same product data sheet B2B food buyers already asked for twice.
Rich data also supports cleaner assortment conversations: which SKUs are nut-free by recipe, which beauty SKUs share an INCI pattern, which lines need special store handling. That is commercial hygiene, not decoration.
Practical checklist before you publish a line
- Ingredient list and (for F&B) major-allergen structure reviewed by quality
- Nutrition or INCI block complete for the product type
- Tech sheet version matched to catalogue effective date
- Unit and case GTINs point at the same core disclosure
- Portal product page shows data without a mandatory download
- Recall and FEFO processes know which field is authoritative
Get those right and allergen data stops being a compliance afterthought. It becomes part of how retailers browse, buy and stay with the brand.
When you want retailers to see allergens, INCI and nutrition inside a clean ordering experience, Book a demo.