GDSN data pools: what synchronisation actually requires from your catalog.
GDSN is not a file format you export to. It is a subscription network, and joining it exposes exactly how complete and consistent your product data is. Most of the work happens before the data pool is chosen.
Publish
Suppliers publish item data into a certified data pool.
Subscribe
Retailers subscribe and receive updates automatically.
Keys
GTIN, GLN and target market identify what goes where.
How it works
Publish once, and every subscribed retailer receives the change.
The Global Data Synchronisation Network connects certified data pools through a registry operated by GS1. A supplier loads item data into its own data pool. The registry records that the item exists. A retailer subscribes through its data pool, and from then on receives the current data and every subsequent change without asking for a file.
The advantage over sending spreadsheets is that corrections propagate. The cost is that errors propagate too, and that validation is strict: a rejected item is rejected for every subscriber at once. This is why GDSN readiness is a data quality project rather than an integration project.
| Element | What it does | What you supply |
|---|---|---|
| Data pool | A certified service that holds and transmits your item data | Your item records |
| Registry | Records which items exist and where they are held | Nothing directly |
| Publication | Makes an item available to a specific recipient | GTIN, GLN, target market |
| Subscription | A retailer's standing request for matching items | Nothing directly |
| Validation | Rule checks applied before an item is accepted | Complete, typed, consistent data |
The three keys
GTIN, GLN and target market decide whether a publication matches.
Every publication is addressed by three values. The GTIN identifies the trade item. The Global Location Number identifies the party, meaning your company and the recipient. The target market identifies the country the data is valid for. A mismatch in any of the three means the retailer simply does not receive the item, with no error that looks like an error.
The most common failure is the target market. Data published for one country does not satisfy a subscription for another, and the same product often needs different data per market because of language, regulatory declarations and pack configurations. Model target market as a real dimension of your catalog rather than assuming one set of values serves everywhere.
- GTIN normalized and valid at every packaging level
- GLN held for your own company and for each trading partner
- Target market treated as a data dimension, not a footnote
- Packaging hierarchy published consistently with the barcodes
Readiness
What has to be true about your catalog before you publish.
GDSN validation checks structure, not marketing quality. Attributes must be present, typed, in the right units, and internally consistent, and the packaging hierarchy has to add up: the case must contain a stated number of the units it says it contains, and the dimensions and weights have to be plausible against each other.
That means the preparation is the same work a PIM does anyway. Attributes defined per product type with units, completeness measured before submission, a review step that catches a supplier value that contradicts another, and a history that shows what was published when a retailer disputes a value.
- Attribute completeness measured per product type before submission
- Units and measurement precision defined on the attribute
- Packaging hierarchy quantities and dimensions reconciled
- Change history retained so a published value can be traced
Choosing a pool
Follow your retailers, then check the sectors and markets.
Data pools are commercial services certified by GS1, and several are well established internationally, including 1WorldSync, Syndigo, atrify and EDICOM among others. The certified list changes, so confirm current certification and coverage against the list GS1 publishes rather than against a vendor page.
The practical selection criteria are which pool your largest retailers already use, whether the pool supports your target markets and product sectors, how it handles validation feedback, and what it costs per item and per publication. Ask for a validation report against a sample of your real data before committing, because that report is a free measurement of your catalog quality.
- Ask which pool your largest retail customers subscribe through
- Confirm the pool covers your target markets and sectors
- Request a validation run against a real sample first
- Check the certified pool list published by GS1 before signing
Frequently asked questions
Clear answers before you evaluate a PIM.
Do I need GDSN if I only sell through my own channels?+
No. GDSN exists to synchronise data with trading partners who subscribe to it, mainly grocery, pharmacy, foodservice and large general retail. If no partner asks for it, the standards discipline is still useful but the network is not.
Is GDSN a file format?+
No. It is a network of certified data pools plus a registry, exchanging structured item data continuously. Your data pool provides the interface you load data through, and formats differ by pool.
Can a PIM publish directly to GDSN?+
A PIM prepares and governs the data, and the data pool performs the publication. The useful division is that the PIM owns the approved values, completeness and history, and the pool owns transmission and validation feedback. Nexodo covers the first half and exports the approved record for the pool.
Why was my item rejected when the data looks complete?+
Usually a consistency rule rather than a missing field: a case quantity that does not match the hierarchy, a weight that contradicts the dimensions, or a target market for which a required declaration is absent. Read the validation report field by field before changing anything broad.
Continue your product data research
Find the catalog problems that block a confident purchase.
Read more →GTIN format referenceGTIN formats, digit lengths, and how to store them without breaking them.
Read more →Channel requirementsMarketplace product data requirements, side by side.
Read more →Supplier product data onboardingOnboard supplier product data without surrendering control.
Read more →Test Nexodo with a supplier file your team already uses.
Tell us how your supplier files arrive and what your channels reject, and we will tell you whether this workflow fits.
- A person replies, normally within one business day
- Use a representative product sample
- We will say plainly if Nexodo is the wrong fit