What is GDSN? Global Data Synchronization Network, explained
Global Data Synchronization Network (GDSN) is a GS1 standards-based network for exchanging and continuously synchronizing product master data between trading partners.
It connects GDSN-certified data pools through the GS1 Global Registry, so suppliers and recipients can publish, subscribe to, and update standardized item and party information.
GDSN handles product identity, descriptions, classifications, dimensions, and other master data. EDI handles business documents, while EPCIS handles supply-chain event data.
What GDSN means in practice
GDSN is a network of interoperable data pools that use GS1 standards to exchange product master data. GS1 describes the network as being built around the Global Registry and data pools, with the Data Quality Framework and GPC providing supporting quality and classification practices.
The shared standards are the point. A supplier and a retailer can use different internal software and still exchange a common set of identifiers, fields, codes, and rules. GS1 standards are developed through the community-based GSMP standards process, then maintained through GS1 governance. The GDSN standards hub contains the current standards and implementation material. GDSN is therefore a network implementation of shared standards, rather than a private file format owned by one vendor.
The data is usually item information, such as a product's description, brand, manufacturer, dimensions, weight, packaging, classification, and other attributes required for the product and market. GDSN can also synchronize party and location information. The exact fields depend on the product category, target market, applicable GS1 standards, and the recipient's implementation requirements.
The network uses a publication and subscription model. A supplier publishes through a source data pool. A retailer, distributor, wholesaler, foodservice operator, or other recipient subscribes through its own data pool. The recipient receives the records and subsequent changes that match its subscription. Publishing once does not automatically make a product available to every trading partner.
How GDSN publication and subscription works
GS1 describes a five-step flow. The short version is:
Supplier → source data pool → Global Registry match ← recipient subscription ← recipient data pool
- The supplier prepares its data. The supplier aligns internal product and party records with the applicable GS1 standards. That includes using the right GTINs, GLNs, target markets, classifications, measurements, and required attributes.
- The supplier loads data to a source data pool. The source can be an in-house solution or a third-party service, as long as it is GDSN-certified. The pool validates and manages the data for network exchange.
- The source pool registers basic information. It sends catalogue-item or party information and the location of the detailed record to the GS1 Global Registry. The Registry helps the network identify where the source record lives.
- The recipient subscribes through a recipient pool. The recipient chooses the products or party information it wants and submits the subscription through its own certified data pool. The Registry matches the subscription to the relevant source pool.
- The pools exchange the subscribed data. The source pool publishes the applicable record to the recipient pool. Later changes can then be synchronized automatically and continuously for that subscription, subject to the connected systems, validation, and trading-partner rules.
The recipient still owns its subscription scope and acceptance process. A retailer may request a particular target market, product category, packaging level, or set of attributes. It may also apply additional onboarding or commercial rules after the data arrives.
Certified data pools and the Global Registry
What a GDSN-certified data pool does
A data pool is the service or access point a company uses to participate in GDSN. It connects the company's product-data systems to the network and handles the publication or subscription exchange. Suppliers and recipients must use certified pools to register or subscribe to items in the Registry.
GS1 defines certification as compliance with GS1 standards and tested interoperability within GDSN. Only trading partners using a certified data pool can synchronize through the network. Companies can review the current certified data-pool list when evaluating providers.
Certification answers a specific question: can the pool interoperate with GDSN under the required standards and tests? It does not certify every product value a customer enters. It does not prove that a description, dimension, claim, or image is accurate. It does not guarantee that a retailer will accept an item. GS1's Data Quality Framework is a separate best-practice guide for managing and inspecting data quality.
What the Global Registry does
The Global Registry is the network's directory and matching layer. It helps trading partners find the source data pool for an item or party and route subscriptions to that pool. GS1 describes three important functions:
- Catalogue-item uniqueness: it supports uniqueness for a catalogue item identified by the GTIN, information-provider GLN, and target market combination for a particular source.
- Source reference: it records which data pool holds the detailed record for that item or party.
- Subscription routing: it records subscriptions so the network can match a recipient's request to the right source pool.
The Registry is not a central warehouse containing every full product record. Detailed product data stays with the source data pool and moves to recipient pools when the subscription and publication rules match.
The identifiers and classification behind GDSN
GDSN depends on shared identifiers and classification. Each one has a different job.
| Term | Meaning | Role in GDSN |
|---|---|---|
| GTIN | Global Trade Item Number. A GS1 identifier for a trade item that can be priced, ordered, or invoiced. | Identifies the product or packaging level being published. A GTIN is a number, not the barcode image and not the product data around it. Read the GS1 GTIN definition. |
| GLN | Global Location Number. A GS1 identifier for a party or location, such as a company, warehouse, factory, or store. | Identifies the information provider and other parties or locations in the data relationship. GS1 groups GLN with its other identification keys. |
| Target market | The geographic market where the trade item is intended to be sold. | Distinguishes market-specific product records and helps determine which subscriptions and attributes apply. |
| GPC | Global Product Classification. A shared hierarchy for classifying products by category. | Gives trading partners a common product-classification language. GPC is a classification, not a product identifier. See how GPC works. |
The identifier combination matters. The same physical-looking product can have different trade-item records when packaging, count, or other conditions make it a separate item for ordering or invoicing. A supplier should preserve each assigned identifier and its relationship to the product record instead of deriving values from a SKU or barcode image.
GDSN attributes also need context. A measurement needs a unit. A description needs a language and market. A product classification needs the correct category. A value can be valid in one target market and incomplete for another. Recipient implementation guides add another layer of required fields and business rules.
Practical GDSN use cases
GDSN is useful when multiple organizations need the same product facts and those facts change over time. It creates a repeatable handoff between a supplier's product-data operation and a trading partner's catalog or operational systems.
| Use case | What GDSN supports | What the team still owns |
|---|---|---|
| New-item onboarding | A supplier publishes standardized item data for a retailer, distributor, or foodservice partner to subscribe to. | Complete source records, correct identifiers, approved content, target-market scope, and the recipient's onboarding requirements. |
| Product changes | Updates to descriptions, measurements, packaging, classifications, or other subscribed attributes can flow through the network. | Change control, effective dates, approvals, and the decision about which partners should receive the change. |
| Distributor and wholesale exchange | Multiple partners can work from the same standardized product master data instead of maintaining separate manual files. | Partner-specific assortment, pricing, inventory, ordering, and commercial terms. |
| Merchandising and catalog operations | Retailers can receive structured attributes that support item setup, category placement, search, filters, and downstream catalog work. | Local merchandising decisions, channel presentation, enrichment, and quality review. |
| Foodservice or industry-specific data | A supplier can share category-specific fields when the relevant standards and partner requirements call for them. | The required attributes, evidence, and regulatory rules for the category and market. |
| Builder and integration workflows | Engineering teams can connect source systems and recipient systems around stable identifiers, structured fields, and subscription state. | Mapping logic, retries, monitoring, provenance, and the behavior of systems outside the GDSN exchange. |
For example, a beverage supplier may publish a unit, a multipack, and a case as separate trade items, each with its own GTIN and measurements. A retailer subscribes to the packaging level it orders and sells. If the supplier changes a case dimension or product description, the updated record can move to that subscribed retailer through the data-pool connection. The retailer still decides whether the item is ready for its assortment and operations.
GDSN can give a downstream catalog a stronger product-data starting point. It does not replace the catalog's own rules for enrichment, inventory, price, digital assets, content, or AI-shopping experiences.
GDSN vs. EDI, EPCIS, PIM, and product feeds
These systems often work together. They solve different data problems.
| System or term | Primary job | Typical information | How it relates to GDSN |
|---|---|---|---|
| GDSN | Exchange and continuously synchronize product and party master data. | GTINs, GLNs, descriptions, brand, manufacturer, dimensions, packaging, classification, and category attributes. | The network for standardized product master-data publication and subscription. |
| EDI | Exchange standardized business documents between companies. | Purchase orders, order confirmations, advance ship notices, invoices, and other transaction messages. | EDI can use the product identifiers and partner information maintained through GDSN. It does not replace GDSN's product-master-data exchange. |
| EPCIS | Share supply-chain event and visibility data. | What happened, when, where, and why, such as a shipment, receipt, or movement event. | EPCIS describes events involving products or assets. GDSN describes the product and party information those events reference. |
| PIM | Manage product information inside a business. | Product content, attributes, variants, media references, workflows, approvals, and channel views. | A PIM can prepare data for a data pool or receive synchronized information. It is an internal system or workflow, not the GDSN network. |
| Product feed | Deliver product data to a particular destination. | A file, stream, or API payload with destination-specific fields for a marketplace, ad platform, retailer, or AI-shopping surface. | A feed can use GDSN data as an input. It follows the destination's format and rules and does not automatically become a GDSN exchange. |
GS1 US describes EDI, GDSN, and EPCIS as different ways to share information electronically. The practical distinction is simple: GDSN keeps product master data aligned, EDI moves business transactions, and EPCIS records supply-chain events. A PIM and a product feed sit at different layers around those exchanges.
Common GDSN mistakes and claim guardrails
Calling GDSN a barcode or GTIN
A barcode is a scannable data carrier. A GTIN is the identifier it can encode. GDSN is the network and process for sharing product and party data. Store the GTIN as a structured identifier and keep its product, packaging, market, and source context with it.
Treating certification as proof that every value is correct
Pool certification tests standards compliance and interoperability. It does not inspect every supplier value or make a product claim true. Keep ownership, source evidence, measurement procedures, validation, approvals, and correction workflows outside the certification claim.
Assuming one publication reaches every retailer
A recipient has to subscribe through a data pool, and the subscription must match the source record. Target market, product scope, classification, partner rules, and recipient acceptance can limit what arrives and what gets used. GDSN improves the exchange; it does not force a retailer listing.
Calling synchronization “real-time” without a defined implementation
GS1 describes automatic and continuous synchronization for subscribed partners. Actual timing depends on source systems, pool processing, validation, partner configuration, and the recipient's import schedule. Use “continuous synchronization” when describing the network and reserve “real-time” for a documented system behavior.
Treating the Global Registry as the full product database
The Registry helps identify the source pool, support uniqueness, and route subscriptions. The detailed product record remains in a data pool and is exchanged with the relevant recipient. A Registry entry is not proof that every product attribute is present or current.
Mixing up identifiers, packaging levels, or target markets
Do not put an internal SKU, MPN, or barcode file in a GTIN field. Do not reuse a unit GTIN for a case when the case is a separate trade item. Do not drop the target market when the product data or requirements differ by geography. These errors can create duplicates, incorrect dimensions, wrong ordering units, or rejected partner data.
Assuming a PIM is automatically a data pool
A PIM can organize and govern internal product information. A certified data pool provides the GDSN connection and interoperability. A business may use both, with mappings and ownership between them.
Promising that GDSN alone satisfies healthcare obligations
Healthcare data needs extra care. GDSN participation does not by itself satisfy every UDI or regulatory submission duty. For example, the FDA's GUDID instructions list the GUDID web application and HL7 SPL submission through the FDA Electronic Submissions Gateway as its submission options. Follow the current regulator and trading-partner requirements for the country and product category, and treat any GDSN-to-UDI mapping as implementation-specific.
Where Catalog fits
Catalog is a structured product-data layer for merchants, merchandising teams, and builders who need product facts to work across storefronts, feeds, APIs, search, recommendations, and AI-shopping surfaces. It can help normalize, enrich, validate, and expose product information as machine-readable product objects while keeping context such as identifiers, variants, attributes, sources, and freshness visible.
Catalog is not a GDSN-certified data pool. It does not replace GS1 identifiers, the Global Registry, or the certified data pool a trading partner uses. A merchant with a GDSN requirement still needs an appropriate certified pool and still has to meet the recipient's implementation guide.
| Layer | Job |
|---|---|
| Source systems | Hold supplier, ERP, ecommerce, PIM, DAM, inventory, and merchandising inputs. |
| Catalog | Normalize and enrich product facts, preserve provenance and relationships, and make the records usable across machine-facing surfaces. |
| GDSN-certified data pool | Handle GDSN publication, subscription, validation, and synchronization with trading partners. |
| Trading-partner systems | Receive subscribed product master data and apply local onboarding, assortment, operations, and commercial rules. |
| AI-shopping and other channels | Consume approved, channel-ready product data through the outputs and integrations that support each surface. |
For a merchant, this separation keeps the GDSN exchange from becoming the only place product data is understood or maintained. For a builder, it makes the data contract clearer: GDSN fields and identifiers can enter a structured product model alongside channel, content, policy, and AI-commerce data. Each output can then use the same durable product facts without treating a partner-specific feed as the source of truth.
Related terms
FAQ
What does GDSN stand for?
GDSN stands for Global Data Synchronization Network. It is a GS1 standards-based network for publishing, subscribing to, and continuously synchronizing product and party master data between trading partners.
How does GDSN work?
A supplier prepares product data to GS1 standards and loads it into a certified source data pool. The pool registers basic item or party information with the Global Registry. A recipient subscribes through its own certified pool, the Registry matches the request to the source, and the pools exchange the relevant record and later updates.
What is a GDSN-certified data pool?
A certified data pool is a GDSN service or access point that complies with GS1 standards and has passed interoperability testing. Suppliers and recipients use certified pools to register and subscribe to data. Certification does not verify every product value or guarantee retailer acceptance.
What identifiers does GDSN use?
GDSN uses GTINs to identify trade items and GLNs to identify parties and locations. Target market identifies the geographic market for the item. GPC provides shared product classification. The exact attributes and rules depend on the product category, market, and recipient.
Is GDSN the same as EDI or EPCIS?
No. GDSN synchronizes product and party master data. EDI exchanges business documents such as purchase orders and invoices. EPCIS shares supply-chain event data such as what happened, when, where, and why. Businesses can use all three together.
Does GDSN guarantee compliance or retailer acceptance?
No. GDSN certification supports network interoperability. It does not certify the truth, completeness, legal compliance, or retailer acceptance of every product record. Suppliers and recipients still own data quality, regulatory duties, implementation guides, and commercial onboarding.
Is GDSN real-time?
GDSN supports automatic and continuous synchronization for subscribed partners. The time a change takes to reach a recipient depends on source and recipient systems, data-pool processing, validations, and import schedules. “Continuous synchronization” is more precise than a blanket real-time promise.
Does GDSN replace a PIM?
No. A PIM manages product information and workflows inside a business. GDSN connects trading partners through certified data pools. A PIM may prepare data for GDSN, receive synchronized records, or manage additional content that GDSN does not cover.
Is Catalog a GDSN-certified data pool?
Catalog is a structured product-data layer, not a GDSN-certified data pool. It can help merchants and builders make product information normalized, enriched, and machine-readable around their existing systems and channel connections. A GDSN participant still needs the certified data pool required by its trading partners.
When product data has to serve both trading partners and AI-shopping surfaces, see how Catalog structures product data for AI commerce.
