Product Data for Fresh Food: Origin and Labelling Done Precisely

A jar of pasta sauce and a tray of sea bass are both grocery SKUs — but as product data, they could not be more different. The sauce needs a name, a nutrition table and a good photo. The sea bass needs a country or FAO catch zone, the catch method, allergen flags and a batch-dependent origin that can change with the next delivery. Fresh food is the corner of grocery where product data stops being marketing content and becomes a compliance obligation.

Product data for fresh food is compliance-first: origin, catch zone, farming method, allergens and nutrition are mandatory fields, not optional content. That single fact reshapes the whole workflow — because a missing or wrong mandatory field doesn't just look bad, it makes the article non-compliant to list. This is a focused sub-branch of the broader food & beverage retail challenge.

What makes product data for fresh food so difficult?

The general grocery problem — many suppliers, no two feeds alike — is sharpened in fresh by two things: the fields are legally mandatory, and the values are volatile.

• Origin is mandatory and category-specific: country of origin for fruit, vegetables and meat; rearing and slaughter country for meat; region for many protected products.
• Fish carries its own regime: FAO catch zone, catch method (gear), and whether the product is caught or farmed — all required, all batch-dependent.
• Farming method and welfare data: the farming method for eggs, husbandry labelling for meat — fields that must match the exact article, not the product family.
• Allergens and nutrition: for pre-packed goods the full nutrition table and allergen list are mandatory, and errors here carry real liability.

Now multiply that across dozens of regional producers and direct farms, each sending a different Excel layout or a delivery note, and the job becomes a permanent manual audit. Doing it by hand does not scale — the fix is to read the data out of whatever format it arrives in and enforce completeness centrally.

Which standard covers fresh food data — and where does it stop?

Food retail does have a backbone for master data: GDSN, the Global Data Synchronisation Network, exchanged through pools like 1WorldSync and Atrify. GDSN carries GTIN, nutrition, allergens and many regulatory attributes cleanly for the big listed brands, and it's the right source for the branded core. But it's worth being honest about the gaps.

In short: GDSN gives you a clean, standard structure for the branded core, and it's genuinely valuable. What it doesn't give you is guaranteed completeness across every supplier — and in fresh, an empty mandatory field is the whole problem. For a deeper look at the standards landscape, see GDSN, ETIM and eCl@ss explained.

How does Productbay keep mandatory fields complete for fresh food?

The throughline in fresh isn't just enriching data — it's proving every compliance-relevant field is filled and current. That's exactly what Productbay is built to enforce:

• Consolidate: import every source once — GDSN pool export, supplier CSV, Excel, delivery data, feed — and match by GTIN so records update instead of duplicating. Branded core and regional longtail land in one structure.
• Enforce completeness: define mandatory fields per category — origin, FAO catch zone, farming method, allergens, nutrition — and Productbay blocks publication while any of them is empty. Completeness becomes a rule, not a hope.
• Enrich with review: AI fills gaps from the source document or whitelisted references, reads origin and labelling data out of PDF spec sheets and product passports, translates via DeepL, and flags anything uncertain — always with a review queue before anything goes live.
• Publish: two-way sync to shop and ERP systems with per-channel transformations, so the compliant record reaches every channel in the format it expects.

Productbay starts where GDSN ends: it takes over the suppliers outside the pool, guarantees the mandatory fields no pool checks for you, and turns the unstructured fresh longtail into complete, audit-ready records. It's built for specialist retailers running multi-supplier, multi-channel catalogs.

Frequently Asked Questions