Build your GS1 trade item data inside Microsoft Dynamics 365 Business Central — structured to the global GDSN and GS1 Benelux data models, ready for publication through a GS1-certified data pool.
GDSN is a network of certified data pools, not an endpoint you can call. Product data always travels through a data pool — for Belgium & Luxembourg that is atrify (1WorldSync), the pool behind GS1 BeLux "My Product Manager". The connector prepares your data in Business Central and talks to that data pool; the data pool talks to GDSN.
Prerequisites you need to hold yourself
A GS1 BeLux membership, your own company GLN and GTINs, and a data pool subscription that includes API access — some plans are web-interface only. These are contracts between you and GS1; the app cannot provide them.
GDSN does not synchronise items — it synchronises trade items, where every packaging level is its own trade item with its own GTIN. The connector builds that model from the product data StarFood 365 already holds.
It is built to both the GS1 global GDSN model and the GS1 Benelux datamodel 3.1.36: the unit descriptor flags, UNECE Rec 20 measurement codes, GS1 packaging type codes, packaging hierarchy and referenced-file types are all there because those two standards require them.
Consumer unit, case and pallet each become a trade item, generated from the GTINs and pack quantities already in StarFood 365.
Check digits are validated on entry using StarFood's own GTIN logic, so a bad barcode is caught before it ever reaches a data pool.
Parent/child links with quantities, so the same case can sit under more than one pallet configuration.
Import the official GS1 Global Product Classification publication and assign the mandatory brick code per item.
Register product image and document URLs per trade item, with the file types GDSN expects.
The authenticated connection to the atrify data pool is built in: OAuth2 client credentials, a Test Connection action and a full message log.
Getting your product data GDSN-ready is the groundwork, and it is the part that takes the longest. It is also the part you can start on today. Here is what we are building on top of it.
Sending your trade items to the data pool and on to your retail partners — the CIN and CIP flows.
Taking in trading-partner product data and returning confirmations — the CIC flow.
BeLux local attributes and validation rules, with Luxembourg, the Netherlands, Germany and France to follow.
The first target market is Belgium (056), via GS1 BeLux and the atrify data pool. The architecture separates the shared GDSN core from the per-market rules, so each further market is a layer we add rather than a core we rebuild.
Use the links below for setup support, help resources and contact options.
Browse the documentation hub for setup and operational guidance.
Find troubleshooting steps and support channels.