GDSN Data Pool
A GDSN data pool is a GS1-certified service that acts as a company's connection point into the Global Data Synchronization Network (GDSN) — it receives a supplier's standardized item data, validates it against GS1 rules, and publishes it through the GS1 Global Registry so subscribing trading partners can pull it. There is no public, direct-access point into GDSN: every participant, supplier or retailer, connects through a certified pool, and the pool — not GS1 itself — is who you subscribe to, pay, and troubleshoot a failed sync against.
Where a data pool sits in GDSN
GDSN is a network of interoperable data pools plus one central directory, the GS1 Global Registry. The registry doesn't store item data — it stores pointers, matching each item's GTIN to the data pool that actually holds the record, and matching companies' GLNs to the subscriptions that should receive it.
Data itself moves on a publish-subscribe pattern between two data pools, not through the registry. A supplier's pool pushes an item record; a retailer's pool, having registered a subscription for that supplier's GLN, pulls it down. If the two companies use different pools, the pools — not the companies — are the ones exchanging the record.
What a data pool actually does
A data pool is a certified electronic catalog of standardized item data, and it can act as a source, a recipient, or both for a given company. Concretely, that means:
- Validation. Incoming records are checked against GS1's data-quality and mandatory-attribute rules before they're allowed onto the network, not after.
- Hosting. The pool stores the actual item record; the registry only stores the lookup pointer.
- Subscription matching. When a new subscription is registered, the pool handles getting the matching published items to the subscriber.
- Certification maintenance. GS1 periodically re-certifies pools against current standards, so a pool's behavior can change on a cycle outside your control.
Picking (or inheriting) a data pool
Companies subscribe to a certified data pool rather than building a connection to GS1 directly, and the choice isn't always free: a major retail trading partner may require suppliers to publish through a pool it already recognizes, which means the pool decision is sometimes made by your biggest customer rather than by you. Well-known pools include 1WorldSync (now part of Syndigo) and SA2 Worldwide; several PIM and syndication vendors operate or partner closely with a specific pool, which can simplify the publish step if that's already where your product data lives.
Where it breaks in practice
The most common support ticket in GDSN operations is "my item isn't showing up at my retailer," and it's rarely the network's fault:
- No subscription registered. Publishing an item does nothing for a trading partner who hasn't registered a subscription for your GLN in the registry.
- Validation rejection. The pool silently holds or rejects a record missing a GDSN-mandatory attribute for that item's classification, and "published" in your pool's dashboard isn't the same status as "received and confirmed" at the recipient.
- Different pools, different timing. Cross-pool syncs add a hop and a reconciliation step that same-pool syncs don't have, so delays are more common when supplier and retailer use different providers.
Frequently asked questions
What's the difference between a GDSN data pool and the GS1 Global Registry?
The registry is a directory, not a database — it stores pointers that match a GTIN to the data pool holding the record and a GLN to the subscriptions that should receive it. The data pool is where the actual item data lives, gets validated against GS1 rules, and gets published or subscribed to. You contract with and troubleshoot against the pool, not the registry.
Do I need my own data pool, or can I use my retailer's?
You need to subscribe to a GS1-certified data pool, but it doesn't have to be the same one your retail trading partner uses — the publish-subscribe model works across pools. That said, some large retailers require or strongly prefer suppliers to publish through a specific recognized pool, which can make the choice less open than it first appears.
Why isn't my published GTIN showing up at my retail trading partner?
The two most common causes: the trading partner hasn't registered a subscription for your company's GLN in the GS1 Global Registry, or your pool rejected or held the record during validation because a GDSN-mandatory attribute for that item's classification was missing. "Published" in your own pool's dashboard doesn't confirm receipt on the other end — check subscription status and the validation report separately.
Is GDSN the same thing as EDI?
No. GDSN synchronizes master item data — the descriptive record of what a product is — through a publish-subscribe model between certified data pools. EDI transmits transactional documents like purchase orders and invoices directly between two trading partners. A company commonly uses both: GDSN to keep item master data aligned, EDI to move orders and shipment notices.