Product Data for Beverages: Deposit, Packaging Units and Mandatory Fields

Beverages look simple on the shelf and are anything but in the data. A single bottle of mineral water can arrive as a single, a six-pack and a crate — each a separate saleable unit, each with its own GTIN, its own deposit and its own base price per litre. Add alcohol content, allergens and a nutrition table on top, and one drink turns into a small stack of interlocking data fields that no fashion or hardware system was ever designed to hold.

Product data for beverages is defined by special fields — deposit, packaging units and base price per litre — layered on top of the regulated mandatory data every food product carries. This is a focused sub-branch of the wider food & beverage data challenge: the food logic of allergens and nutrition, plus the deposit-and-packaging logic that is unique to drinks.

Which deposit and packaging attributes do beverages need?

The part that trips up generic systems is that a beverage is rarely one thing. It is a hierarchy of packaging units, and several attributes have to travel down that hierarchy correctly:

• Deposit type: one-way (Einweg) vs. returnable (Mehrweg) vs. none — a hard classification that drives both price and legal handling.
• Deposit amount per level: the bottle carries a deposit, the crate carries its own deposit, and a crate total is the crate deposit plus the deposits of the bottles inside it. It stacks.
• Packaging unit: single, six-pack, crate, layer, pallet — with the count per unit, so quantities and prices resolve per saleable unit.
• Fill volume: the litre or millilitre value that feeds the base price and often the nutrition reference.
• Base price per litre: a legal must in most markets, and one that has to stay in sync with price and volume automatically.

Try to hold this in a flat product table and it breaks: the deposit ends up as a stray column, the crate math is done by hand, and the base price drifts out of sync the first time a price changes. The clean model is an attribute group per packaging level.

Where does GDSN help — and where does it stop?

Beverages do have a real standard. GDSN — the Global Data Synchronisation Network, fed through data pools like 1WorldSync or Atrify — transports the standardised master data of listed brands: GTIN, the full packaging hierarchy, net content, nutrition values and many of the regulated declaration fields. For the branded core of a beverage range, GDSN genuinely does a lot of the work.

But GDSN covers the listed core, not the whole assortment:

So the real setup is GDSN for the branded core plus a manual rest: regional breweries, wineries, direct and private-label suppliers who still send an Excel or a PDF price list. The pool solved the easy part; the deposit mapping, the base price and the longtail content are still on you.

How does Productbay handle beverage data?

The throughline is to model the special fields once and then automate the rest — and that is what Productbay is built for:

• Attribute groups for deposit and packaging: define deposit type and amount per packaging level, and the single / six-pack / crate / pallet hierarchy, so the correct total deposit resolves per saleable unit instead of being retyped.
• Computed base price per litre: derive the base price from sales price and fill volume as a calculated field, so it recalculates automatically whenever price or volume changes — no drift, no manual maths across thousands of SKUs.
• Ingest GDSN plus the rest: import pool data (1WorldSync, Atrify) alongside supplier Excel and PDF price lists, matching by GTIN so listed and non-listed suppliers land in one catalog.
• AI enrichment: AI fills gaps — alcohol content, allergens, tasting notes, descriptions — from whitelisted sources and reads specs out of PDF price lists, always with a review queue before publishing.
• Publish everywhere: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for Amazon, OTTO and Kaufland, each with per-channel transformations.

Productbay starts where GDSN ends: it complements the pool for your listed core and takes over the deposit and packaging logic, the computed base price, and the regional and private-label longtail no standard carries. Productbay is built for specialist retailers running multi-supplier, multi-channel beverage catalogs. For the wider food picture, see the food & beverage overview, and for the standards themselves, GDSN, ETIM and eCl@ss explained.

Frequently Asked Questions