Colloquially, many know GTIN as a barcode, but technically, GTIN is the number found beneath the barcode symbol itself, and can therefore also be used for other technologies such as 2D barcodes and RFID tags.
The guide below will give you insight into the data format that needs to be in order for you to set up an M2M integration.
All data communication will be done with XML files according to the latest GDSN version. You can always find the latest documentation on the GDSN website (in English) via the following link:
View latest documentation for GS1 GDSN
The GDSN standard is constantly updated, but the intention is always that you should be able to send in the current format even after updating to a new version. In some cases, however, this may not always be possible.
This means that one unified data set must be provided in each file. Thus, all information must be provided each time information is sent to the GDSN network. In principle, it is possible to enrich data on an ongoing basis, but the minimum requirements for the market in question must always be met, as otherwise the file will be rejected.
For documentation of API and FTP for Production Environment, contact GS1 Denmark.
When you exchange data with the GDSN network, regardless of the communication channel you use, for each file you send to GS1 you willTrades Sync, receive a response back telling if data has been accepted or rejected.
Depending on whether you are sending data to a customer using the same platform as you or whether it is a customer using an external platform, the type of response you receive may vary.
However, we are always talking about the same two types of messages.
The first message is a GS1ID that indicates whether the file meets the schema rules, and thus whether the file can be processed by the system. In addition, this answer also indicates whether the general GDSN-rules are being complied with.
When you receive a GS1response that is accepted, you will then receive another message, a Catalogue Item Confirmation (CIC). This file indicates whether your data has been sent to the recipients you expect and whether they have received it, or if they have any objections to missing information. This is used, for example, if you send abroad, where there may be local regulations that you have to comply with.
Data is not automatically synchronized with everyone who uses GDSN. This is handled with the help of signatures. A subscription does not depend on the product being created in the GDSN, just as the product creation does not depend on a subscription.
This means that you can send data to the GDSN without anyone having requested to receive your data in the GDSN. This is important to understand because you may find that responses to products come fairly long after you have originally created the product.
However, this is because data is not sent to a recipient until they request to receive data via a subscription. Below is shown how the signing process works:

Contact us so we can help you get started info@gs1.dk or on tel. 39 27 85 27.
Do you still need help? Reach out to our support team. We are always ready to help.