Skip to content
  • There are no suggestions because the search field is empty.

GS1 Benelux release of 22 August 2026 (GDSN 3.1.36)

SyncForce has processed all relevant changes from the GS1 Benelux release that went into production on 22 August 2026.

This release is built on GDSN standard 3.1.36. The new data model and the full overview of changes were published by GS1 on 15 June 2026.

This article summarises what changed and what it means for you. It covers Benelux FMCG and Benelux DIY.

Most changes are handled inside SyncForce and your mapping, so you do not have to do anything. The points marked Action need a look from your side.


1. Local code lists are now Benelux code lists

The Dutch local code lists have been renamed. The prefix changes from NL_ to BNL_, because the lists now serve the whole Benelux instead of the Netherlands only.

This affects a long list of code lists, among them:

  • BNL_DangerousGoodsHazardousCodeList
  • BNL_SEVESOClassificationCodeList
  • BNL_SafetyRecommendationsCodeList
  • BNL_ADRTunnelRestrictionCodeList
  • BNL_ADRClassificationCodeList
  • BNL_DangerousGoodsPackingGroupCodeList
  • BNL_DangerousHazardousLabelNumberCodeList
  • BNL_HazardStatementsCodeList
  • BNL_SpecialPermitOrExemptionIdentificationCodeList
  • BNL_BatteryMaterialCodeList
  • BNL_PackagingMaterialColourCodeList
  • BNL_PackagingMaterialClassificationCodeReferenceCodeList
  • BNL_NutrientTypeCodeList
  • BNL_IngredientPurposeCodeList
  • BNL_alcoholicBeverageCharacteristicCodeList

The validation rules that point at these lists have been updated as well. The values themselves do not change. You will only notice the new names in validation messages and in the GS1 validation overview.


2. Warnings, usage instructions and storage instructions

GS1 has tightened the use of the attribute Warnings and side effects for medicines or supplements (drugSideEffectsAndWarnings). The name, the example and the obligation of the attribute have changed.

Two things follow from this:

  • From this release, label information for food and drugstore items in this attribute is checked by Data Management Services as part of the data quality programme.
  • A new validation (500.646) blocks the use of this attribute when the product is not a food supplement, a self-care medicine or a health product. A new code list DrugSideEffectsAndWarningsGPCCodeList supports this check.

To stop the attribute being used for the wrong purpose, two other attributes have had their instructions cleaned up:

  • Usage instructions (consumerUsageInstructions): the sentence pointing to the medicine warnings attribute has been removed.
  • Storage instructions (consumerStorageInstructions): the sentence about drugstore items, cosmetics and personal care has been removed.

Action: if you put general warnings or restrictions of use in drugSideEffectsAndWarnings for products that are not supplements or medicines, move that text to the correct attribute.


3. Safety data sheets in the national language

The instruction for SDS file name URL (uniformResourceIdentifier) now says that the safety data sheet must be supplied at least in the national language or languages of the target market.

One old validation has been removed (500.407) and replaced by three new ones that check the SDS language code per target market:

  • 500.633: for the Netherlands, fileLanguageCode must contain at least nl
  • 500.634: for Belgium, at least nl or fr
  • 500.635: for Luxembourg, at least fr or de

Action: check that your safety data sheets are published in the right language per market.


4. Excise duty

Two new validations make sure excise data is delivered correctly and consistently:

  • 500.632: for alcoholic drinks with more than 0,5% alcohol by volume, dutyFeeTaxTypeCode must be filled at least once with one of the excise codes (N304, N305, N401, N402, N501, N502, N601), and dutyFeeTaxCategoryCode must be APPLICABLE in the same iteration.
  • 500.658: for products whose GPC category appears in the new code list NLExciseGPCCodeList, dutyFeeTaxTypeCode must be filled at least once with one of the same excise codes.

Two code lists support this:

  • NLExciseGPCCodeList is new. It holds the GPC bricks for product categories that are subject to excise duty in the Dutch market.
  • BE_ExciseCodeList has been extended with 8 excise codes, based on the official 2026 publication.

Action: if you sell alcoholic drinks or other excise goods, check that the excise type code is filled.


5. Single Use Plastic categories

The Single Use Plastic (SUP) categories in the attribute Single Use Plastic (SUP) category (propertyDescription) have been revised at the request of Verpact, so that they follow the latest legal guidance and sector agreements.

Part of the old code values are migrated to the new values. The remaining old values are removed.

Action: check your existing data mappings for SUP and adjust them to the new structure. This is the change in this release with the largest chance of an impact on your data.


6. Nutrition
  • Nutritional programme ingredient quantity (nutritionalProgramIngredientMeasurement) moves from Optional to Conditionally Mandatory. It is now required when Nutritional programme ingredient type is filled. Validation 500.433 checks this.
  • NL_NutrientTypeCodeList (now BNL_NutrientTypeCodeList) has three new codes.

7. Other attribute changes
  • Net content statement (netContentStatement): information about portions may no longer be put in this attribute.
  • Provenance statement (provenanceStatement): the attribute is meant for primary ingredients and for cases where regulation requires it. Marketing text with a geographic reference does not belong here.
  • Cfp value (cfpValue) and Cfp functional unit (cfpFunctionalUnit) are now repeatable, in line with GDSN.
  • Unique selling point (tradeItemFeatureBenefit): maximum length is documented as 500, following the GDSN schema. This is a documentation correction only.
  • Contact details (communicationValue): the Dutch and French attribute names in the usage note have been corrected.
  • Accreditation logo or quality mark on packaging (packagingMarkedLabelAccreditationCode): the reference to online labels for wine and spirits has been removed, and an incorrect URL in the Dutch and French instruction has been corrected.
  • Hazard type (ADR, BRZO/Seveso) (dangerousGoodsHazardousCode): the instructions have been clarified, and the code lists it uses are now the BNL versions.
  • Maximum lengths have changed for: Nutri-Score product category, growing method code, dosage form, average life, Cfp value, sustainability programme code and sustainability value.

8. Product name for Belgium and Luxembourg

Two validations have been activated in the Dutch data pool:

  • 500.655: the functional product name must be filled in the mandatory languages for target market Belgium.
  • 500.656: the same for target market Luxembourg.

9. Packaging type and packaging material

Several new validations check that the packaging type and the packaging material make sense together:

  • 500.660: for packaging type BO (bottle), JG (jug) or JR (jar) there must be a second packaging instance with a packaging type filled.
  • 500.665: bag-in-box (BBG) may not have GLASS as packaging material.
  • 500.674: brick (BRI) must have COMPOSITE or LAMINATED_CARTON as packaging material.
  • 500.672: cup or tub (CU) may not have GLASS as packaging material.
  • 500.673: cup or tub (CU) may not have PAPER_PAPER as its only packaging material.
  • 500.662: cylinder (CY), when it is not a bottle, may not have GLASS as packaging material.
  • 500.663: cylinder (CY) needs at least two packaging elements.
  • 500.650: Is packaging material recoverable? (isPackagingMaterialRecoverable) must be filled with TRUE or FALSE.

10. Explosives precursors

To support EU regulation 2019/1148 on explosives precursors, two new code lists have been added:

  • EU_ExplosivesPrecursorsRegistrationCode
  • EU_ExplosivesPrecursorsReportingCode

Four new validations (500.639, 500.640, 500.641 and 500.642) check that Regulation type (regulationTypeCode) and Values defined in directive (regulationLevelCodeReference) are filled correctly for registered and reported precursors.


11. Consumer contact information

Validation 500.597 has been reactivated and extended. GPC segment 53000000 (cosmetics) has been added.

The rule checks that contact name, contact address and communication value are filled when the contact type is CXC (consumer support). It is a warning for now, but it may become an error in a later release.


12. Other validation changes
  • 500.654: KAG and KOAG certification numbers must be formatted correctly.
  • 500.657: the wine vintage (vintage), when filled, must be a value between 1900 and 2100.
  • 500.460: the GPC bricks for fresh cut herbs (10008217) and potatoes (10006104) are excluded from this rule.
  • 500.388: brick 10005645 is excluded.
  • VR_DIY_B2B_0049 has been removed because it duplicated VR_DIY_B2B_0048.
  • VR_BASIC_0060 has been removed because it is no longer implemented in My Product Manager.
  • A group of rules (500.375, 500.542, 500.589 and others) has had the target market country code removed from the rule description.
  • A larger group of rules has had its rule description rewritten so that it reflects the real intent of the rule. The rules themselves do not change.

13. Battery related code lists

ElectricalAppliancesGPCCodeList has been slimmed down twice:

  • The GPC for medical devices (10005844) has been removed, because most medical devices do not contain batteries.
  • 61 more GPC codes have been removed, because products in those bricks are not always electrical.

This list is used by VR_FMCGB2B_0163 and VR_FMCGB2B_0164.


14. GDSN 3.1.36 code list changes

The August 2026 GDSN release adds, removes and changes codes in a long list of GDSN code lists, among them:

AdditionalTradeItemIdentificationTypeCode, BatteryTypeCode, ClaimElementCode, DietTypeCode, GrowingMethodCode, HairProductFunctionOrTreatmentCode, MeasurementUnitCode_GDSN, NutrientTypeCode, PackagingMarkedLabelAccreditationCode, PhysicalResourceUsageMeasurementTypeCode, ProductCharacteristicCode, ReferencedFileTypeCode, RegulationTypeCode, ResponsibleAgencyCode, SterilisationTypeCode, SustainabilityProgramCode, TargetedConsumptionByCode, TargetHairTypeCode and TargetSkinTypeCode.


15. Benelux DIY

The DIY data model has its own set of changes:

  • Extra values have been added to improve data quality and to reduce the use of "other". Where possible, the "other" option has been removed.
  • Several attributes move from mandatory to optional, or the GPC brick is unlinked, in places where "other" was often used.
  • The way the EPREL ID is recorded changes. The GDSN attribute is now used for additional product information, and the temporary EPREL ID attribute will disappear in the next release.
  • Definitions and instructions for recording packaging for the Green Score calculation have been adjusted, including the use of values such as Recycled and Bio plastic.
  • The temporary attribute Repairability index has been withdrawn as of 22 August 2026 and is replaced by the international attribute Sustainability value.
  • GPC bricks 10008138, 10005209, 10001097 and 10006781 have been activated, for handheld vacuum cleaners, kitchen storage parts and accessories, luggage, bag and umbrella accessories, and non powered tweezers.

DIY points that need attention

  • Roll length: field 4.470 is replaced by field 4.054. Field 4.470 will be removed in the next release.
  • Energy class (field 4.242): four new validations have been added (520.021, 520.022, 520.024 and 520.025). They cover regulatory information, the energy label file, the EPREL identification type and the EPREL product sheet. All four are warnings today, but they may become errors in a later release.
  • Light source included (field 4.155): validation 520.821 is an error. When field 4.155 is TRUE, field 9.130 (lamp cap type) must be present.
  • Minimum order quantity: validation 520.822 is a warning. When the item is orderable, orderQuantityMinimum should be used.

Questions

If you are not sure whether a change affects your data, contact your SyncForce consultant. We can check your mapping and your current values with you.