GS1 & GDSN

PIE speaks GS1. It validates identifiers, projects your product data into the GS1 Global Data Model (GDM), scores readiness, and — when enabled — exchanges product data with trading partners over a GDSN data pool.

Identifiers

PIE validates GTIN (trade item), GLN (location/party), and SSCC (logistics unit) including check digits. A bad GTIN check digit is warned on draft and blocked at publish; during AI ingestion review, a wrong check digit is flagged inline with a one-click fix that applies the expected digit.

GDM mapping

The GS1 Global Data Model is the standardized attribute set trading partners expect. PIE projects your product and its linked reference entities into a GDM record. You map your category attributes to GDM fields once; entity-sourced data (allergens, nutrients) projects into the corresponding GDM groups automatically.

On a fresh producer organisation, the seeded "Food (built-in)" category ships with nine default GDM mappings, and four more mandatory codes are projected directly from product columns (GTIN, target-market country code, trade-item description, GPC category code). The result: a new producer can reach GS1 readiness without creating a single mapping by hand. Where you do need mappings, the GS1 page offers name-based "Suggest mappings ✨" — it proposes matches (for example zutaten → ingredient statement, marke → brand name), mandatory-first, with confidence badges, and creates them through the normal CRUD only after you confirm.

Readiness

GS1 readiness scores whether a product carries everything the GDM projection needs. Readiness runs before identity checks; it blocks publishing when mandatory GDM data is missing and warns on draft. Use the readiness panel to see exactly which fields are outstanding.

GDSN data-pool exchange

With GDSN enabled, a GS1-ready product can be published to a data pool:

• Outbound — publishing sends a CIN (Catalogue Item Notification) as GS1-XML to the pool; the CIC (Catalogue Item Confirmation) lifecycle then advances as the recipient responds, updating PIE via a signed callback. An optional simulated AS2 transport produces an MDN receipt with a content MIC.
• Inbound — an item sent to PIE creates a shadow product in a managed supplier organisation, and the receiving buyer is auto-granted access — preserving the producer-produces / buyer-reads model.

Optional GLN and GTIN ownership gates block a publish only on a confirmed cross-org conflict (checked against a registry), and fail open when the registry is unknown or unreachable.