New EAN/GTIN Validation

Update October 1:

The schedule for the update has been postponed, and the requirements are being re-evaluated. The change will not be implemented as previously announced. We will share a new date along with technical instructions as soon as possible. We apologize for any additional work this may cause.

This change is based on requests from our users to display EAN/GTIN on invoices, combined with GDPR requirements. The goal is to ensure that historical documents/records are not affected when articles are updated. Therefore, we are planning support for the automatic storage of EAN/GTIN, including validation to prevent personal data or invalid characters from being sent in e-invoices.

Original information (published June 25):

In September, we will be updating how the system handles item numbers. EAN/GTIN will then be included on all quotes, orders, and invoices in accordance with official GS1 standards.

Since this change impacts existing integrations and workflows, we are sharing this information in advance so you have sufficient time to prepare.

What rules will apply?

Going forward, we will only allow EAN/GTINs that are correct according to official GS1 validation rules. To accommodate the different types of codes available, we will support lengths of 8, 12, 13, or 14 digits.
Read more about EAN/GTIN on GS1:s website:

• Different types of GTIN

• UPC-A and UPC-E

The new validation will change how items and documents are handled in the system:

• Saving or updating an item with an incorrect EAN will not be permitted.

• An item with an incorrect EAN/GTIN cannot be added as a component of a package- or structure item.

• An item with an incorrect EAN/GTIN cannot be added to a quote, order, or invoice.

Please note: The exact validation rules and how documents are affected are currently under review. The details previously published in this post are being revised, and final guidelines will be published alongside the updated schedule.