We want to publish to GDSN / GS1, how to arrange this with SyncForce?
The workload for implementing a publication to GDSN depends on the target market, sector, and data pool. If SyncForce already publishes to the relevant market, sector, and data pool, the workload is clear and limited. Otherwise, the level of impact increases with the number of new components involved.
Sales units & trade units managed in SyncForce can be published to GDSN (the network) in accordance with GS1 standards.
Target markets
Currently, sales units across SyncForce customers are published to the following target markets:
-
The Netherlands
-
Austria
-
Belgium
-
Denmark
-
France
-
Germany
Sectors
GS1 supports multiple sectors, each with its own regulatory and sustainability requirements.
SyncForce currently has experience in the following sectors:
-
Food, Health & Beauty (FMCG)
-
Do-It-Yourself (DIY), Garden & Pet
GS1 also supports the following sectors:
-
Healthcare
-
Agriculture & Fresh
-
Textile & Apparel
-
Marketplaces & e-commerce
Data pools
Sales unit data is published from SyncForce to a GDSN data pool.
A data pool is a service provider that connects companies to the GDSN and manages the exchange of data with recipients.
Currently, SyncForce publishes sales units & trade units to the following data pools:
-
Trade Connectors (https://www.tradeconnectors.org/)
-
Atrify Belgium (https://1worldsync.com/)
- Atrify Germany (https://1worldsync.com/)
Implementation scenarios
Known target market, sector, and data pool
If the target market, sector, and data pool are already supported by SyncForce, the setup of the GDSN / GS1 connection is straightforward, and the workload is clear and limited.
New target market, known sector and data pool
When sales units & trade units need to be published to a new target market, but for a sector and data pool already supported by SyncForce, additional work may be required. This typically involves implementing new fields and/or validations to comply with target market–specific GS1 rules.
There are two ways to identify what is missing:
-
Full analysis of the target market–specific GS1 rules.
-
Trial-and-error approach by configuring the GDSN connection for the new target market and publishing products to the data pool’s acceptance (test) environment.
While option 1 may seem preferable, experience shows it can be time-consuming and difficult to scope upfront.
In practice, option 2 is often the fastest and most effective approach.
New sector, known target market and data pool
When publishing sales units & trade units for a new sector that SyncForce does not yet support, new fields and/or modules may need to be implemented in SyncForce.
If it is clear which GDSN fields are required, your SyncForce Implementation Partner can perform the analysis based on existing GDSN documentation.
If this is not yet clear, the trial-and-error approach is again an effective way to determine the required data.
New data pool
The need to configure a new data pool usually arises when a company already manages data for their sales units and trade units in that data pool and now wants to automatically publish data from SyncForce. The company must have a subscription to the data pool. In this situation, there are two options:
-
The company (SyncForce customer) keeps its subscription to the data pool, and SyncForce sets up the connection to this new data pool.
- The company switches to one of the existing data pools already connected to SyncForce.
In the first scenario, SyncForce needs to configure the connection to the new data pool, and a SyncForce subscription is required. Both involve financial implications.
In the second scenario, the customer switches data pools. The subscription fee for the new data pool may be higher or lower, but no additional SyncForce costs are incurred for connecting to it.
When sales units and trade units need to be published to a new data pool, SyncForce must first configure the data pool. The workload for this is clear and limited.
In many cases, a new data pool also implies a new target market and possibly a new sector. In such cases, the implications described in the previous sections apply.