A common worry when brands start with GS1, especially before a 2D-barcode or traceability project, is that they are handing their product data to a central database. Some people hope the opposite: that GS1 will hold everything, so they don't have to. Neither is true. GS1 holds a deliberately small amount of data, and most of what matters to your business stays with you.
What GS1 does hold: core identity data
GS1's main data service is Verified by GS1, a lookup service built on the GS1 Registries. The data comes from the owner of each identifier, meaning the brand, and is uploaded through the local GS1 office.
Verified by GS1 is designed to answer four questions about a number:
- Is it properly structured?
- Was it issued by GS1?
- Which company is it licensed to?
- Does the product or location data held against it match yours?
It organises information in three levels: licensee company information, core product, location or company data, and links to other sources.
The core product attributes
For a GTIN, the core data is short. GS1 US lists seven core attributes:
| Attribute | Example for a fictional perfume |
|---|---|
| GTIN | 09501101530003 |
| Brand name | Maison Ardent |
| Product description | Ambre Nuit eau de parfum |
| Product image URL | A link to the brand's own pack image |
| Global Product Classification (GPC) | GS1's standard category for the product |
| Net content and unit of measure | 100 ml |
| Country of sale / target market | Where the product is sold |
That is enough for a retailer or marketplace to confirm that a GTIN exists, belongs to Maison Ardent and broadly describes a 100 ml perfume. It is not a full product catalogue. Even the image is a link to a file you host.
Some GS1 offices run additional national product-data services. GS1 India's DataKart, for example, describes itself as "India's National Product Data Repository". If your local office offers such a service, check what it holds and who can see it. It is still product master data, not production or supply-chain records.
What GS1 does not hold
None of GS1's own descriptions of its registries include the following, and you should not assume they are stored centrally:
- Serial numbers. Each brand creates and keeps its own serial numbers. There is no global GS1 register of every unit.
- Batch and expiry records. Which batches you made, when and where, stays in your ERP and production systems.
- Prices. Every retailer sets and stores its own price against your GTIN.
- Supply-chain events. EPCIS, GS1's standard for supply-chain event data, is about sharing events "across, between and within enterprises". Events are captured by businesses and exchanged between trading partners, not uploaded to GS1. See does EPCIS mean sending all my data to GS1?
- Scan and sales data. Checkout scans, consumer phone scans and stock movements belong to the retailers, partners and platforms that collect them.
Where the rest of your data lives
If GS1 holds only the core, where does everything else sit? With you and your partners, each holding the part they are responsible for:
| Data | Usually held by |
|---|---|
| Full product master data (ingredients, dimensions, marketing copy) | The brand's ERP or product-information system, shared with partners |
| Retail price, stock and shelf location | Each retailer's own systems |
| Batch, serial and production records | The brand's ERP, line systems and serialization platform |
| Shipments, receipts and aggregation | The brand's and partners' traceability systems |
| Consumer scans and engagement | The brand's connected-packaging platform |
How full product data travels from brand to retailer is covered in how product information gets from a brand to a retailer. How each retailer gets its name and price data is explained in where does the retailer get the product name and price?
How resolvers fit: pointing, not storing
With GS1 Digital Link, a product's identity becomes a web address, and a resolver connects that identity to online information: a product page, instructions, a recall notice, a traceability record.
This doesn't create a new central store. GS1's 2D-at-retail guideline describes a network of GS1-conformant resolvers in which product information "remains within [the] data owner's own system", with resolvers acting as a discovery service. A resolver can even point to a brand's own EPCIS repository through a standard link type. The data stays where it is; the resolver tells a phone or a partner where to find it. Read more in what is a GS1 resolver?
A worked example
When Maison Ardent launches Ambre Nuit, its data ends up in several places:
- GS1 registry: the GTIN, brand, description, image link, classification, 100 ml and target market, uploaded through its local GS1 office.
- Maison Ardent's ERP: full product specification, every batch made and every serial printed.
- The retailer's systems: the GTIN, the retailer's own description, its selling price and stock.
- Maison Ardent's traceability system: which cartons went on which pallet, and where each pallet was shipped.
- Its consumer platform: the pages a shopper sees when scanning, and the scan history.
If a marketplace checks the GTIN, it sees the registry facts. If a regulator asks where batch L2609 went, the answer comes from Maison Ardent's records, not from GS1.
Why this matters
This split has practical consequences:
- You own and must maintain your data. Wrong registry data is your problem to fix, and gaps in serial or batch records can't be filled from GS1.
- You choose what to share. Supply-chain data moves between partners by agreement, which protects commercially sensitive information.
- You need your own systems for serialization, traceability and consumer engagement. GS1 provides the standards and the identity layer, not the operational platform.
To see where these standards come from and how the identifiers fit together, start with What is GS1?
See how AIQR records traceability events