How Product Information Gets from a Brand to a Retailer

When a retailer agrees to stock your product, your product's name appears on its shelf labels, website and receipts within days or weeks. Many brand teams assume this comes from GS1 or from the barcode itself. In fact it travels through a chain of data hand-offs that you largely control. Understanding the chain helps you avoid listing delays, wrong descriptions and mismatched pack data.

The starting point: your product master data

Every product has a definitive record somewhere in the brand's own systems, usually an ERP or a product-information management (PIM) system. This is your product master data. For each GTIN it holds things like:

• brand, product name and description;
• net content, dimensions and weight;
• pack hierarchy: how many units in a case, how many cases on a pallet;
• ingredients, allergens, safety or regulatory statements;
• images and marketing copy;
• recommended or list price, and trade terms.

The GTIN is the key that ties all of this together. Every downstream copy of your data, whether at a retailer, distributor or marketplace, is supposed to describe the same product. The GTIN is how everyone knows they mean the same thing. For the basics, see what is a GTIN?

The destination: each retailer's item file

Retailers don't share one global catalogue. Each one keeps its own item file, a product database keyed by GTIN, which feeds its stores, warehouses and website. When it lists your product, it creates a record and fills it from three sources:

1. Data from you: description, sizes, pack hierarchy, images.
2. Its own decisions: selling price, promotions, which stores stock it, shelf position, its own internal item code.
3. Operational data it generates: stock levels, sales, reorder points.

The price is the clearest example of the split. You may recommend a price, but the retailer sets and stores its own. GS1 explains that when retailers scan a barcode, they use it "to look up their own information in their IT systems, exactly as they do today."

The product journey above shows the physical flow from factory to store. The data flow runs alongside it, and usually starts earlier, because the retailer needs your item set up before the first delivery arrives.

How the data travels

There are three common routes from your master data to a retailer's item file. Most brands use more than one.

Spreadsheets and supplier portals

The simplest route: the retailer sends a new-item form or opens a supplier portal, and your team fills it in for each GTIN. It works for a few products and a few retailers. It becomes painful at scale: every retailer asks for slightly different fields, every change has to be re-entered, and typing errors creep in.

Data pools and syndication services

To avoid re-keying the same data for every customer, many brands publish their product data once to a data pool or syndication service. Retailers that subscribe receive it in a structured, consistent format. The GTIN is the common key, so a retailer's systems can match incoming data to the right item automatically.

The specific services available differ by country and sector, and some GS1 offices run their own. GS1 India, for example, runs DataKart, which it describes as "India's National Product Data Repository". Ask your main retail customers which services they use before choosing one.

Direct integration

Large brands and retailers sometimes connect their systems directly, sending product data and updates electronically between ERPs. This is the most automated route and the most work to set up.

Where GS1 fits in the chain

GS1 provides the shared identifier that makes all three routes work. Without a common GTIN, every retailer would need its own code for your product, and matching data would be guesswork.

GS1 also provides a way to check the basics. Through Verified by GS1, a retailer or marketplace can confirm that your GTIN is properly structured, issued by GS1 and licensed to your company. It can also check a small set of core attributes, such as brand, description, image link and net content. Marketplaces rely on this: Amazon's seller guidance says it verifies product UPCs "by checking the GS1 database". What GS1 does and doesn't keep is covered in does GS1 store all my product data?

What GS1 does not do is carry your full catalogue to every retailer, or hold any retailer's price.

At the checkout: a lookup, not a download

When a shopper buys your product, the point-of-sale system reads the GTIN from the barcode and looks it up in the retailer's item file. That gives the description on the receipt and the price on the bill. Nothing is fetched from GS1, from you or from the internet.

This stays true with 2D codes. When a checkout reads a QR code carrying a GS1 Digital Link, the scanner software extracts the GTIN from the web address and passes it on. GS1 notes this works "without any need for an online connection". The till does not visit the link. Step by step, see what happens when a product is scanned at the checkout?

A worked example

Maison Ardent is launching Ambre Nuit 100 ml with a department-store chain and an online marketplace.

1. Master data. Its product team creates the GTIN in the ERP with description, 100 ml, carton dimensions, 12 units per case and pack images.
2. Registry. It uploads the core attributes to its GS1 office's registry, so partners can confirm the GTIN belongs to Maison Ardent.
3. Retailer setup. The department store uses a data pool, so Maison Ardent publishes the item there. The store's systems pick it up and create an item record keyed by the GTIN.
4. Retailer decisions. The store's buyer adds its own selling price, a launch promotion and the list of stores that will stock it.
5. Marketplace. Maison Ardent lists on the marketplace using the same GTIN. The marketplace checks it against GS1 data before accepting the listing.
6. Checkout. A shopper buys a bottle. The till reads the GTIN, finds the store's record and charges the store's price.
7. Change. Six months later, Maison Ardent updates the pack image. It changes the master record once and republishes; each retailer applies the update on its side.

If the bottle is reformulated in a way that changes the declared ingredients, the GTIN rules call for a new GTIN, and the whole chain starts again for the new item. For how marketplace listings differ, see how product identity works on marketplaces like Amazon.

Practical advice for brands

• Get the master data right first. Errors in your master record are copied into every retailer's file.
• Keep one GTIN per product. Using different numbers for the same product with different customers breaks the shared key.
• Keep pack and data consistent. The net content, dimensions and images in your data should match what is physically in the box.
• Plan for updates. Decide who owns each field and how changes reach retailers.

For the organisation behind the shared identifier, start with What is GS1?