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

GS1 Benelux release of 14 November 2026 (GDSN 3.1.37)

SyncForce has processed all relevant changes from the GS1 Benelux release that goes into production on 14 November 2026.

This release is built on GDSN standard 3.1.37. GS1 published the new data model and the full overview of changes on 7 September 2026. This article summarises what changes and what it means for you.

The release covers Benelux FMCG. There are no separate DIY changes this time, but many of the new validations also apply to DIY Sales Units.

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.

Almost all new validations are warnings for now. They do not block your publication, but they do show up in GS1 Data Source. Fix them early, so your data is ready when GS1 makes them stricter.

1. Commercial warranty

GS1 adds new attributes to show that a product comes with a commercial warranty:

  • Warranty type (warrantyType): use the code GARAN when the product has a commercial warranty. The values come from the new code list BNL_WarrantyTypeCodeList.
  • Warranty duration (warrantyDuration) and Warranty duration unit (warrantyDuration/@measurementUnitCode): the period for which the warranty is valid.
  • Referenced file type code (referencedFileTypeCode): use WARRANTY_INFORMATION for the warranty document.
  • Uniform resource identifier (uniformResourceIdentifier): the link to the PDF with the warranty information.

Two new validations check this:

  • 500.686: when Warranty type is GARAN, the warranty duration and its unit must be filled.
  • 500.687: when Warranty type is GARAN, there must be a file with type WARRANTY_INFORMATION and a link to it.

SyncForce has added the Warranty type attribute and the mapping.

Action: if your products come with a commercial warranty, fill Warranty type, the warranty duration and unit, and add the warranty document as a digital asset with the role that maps to WARRANTY_INFORMATION.

2. Date on packaging

The attribute Trade item date on packaging type code (tradeItemDateOnPackagingTypeCode) may now only have one of these values: BEST_BEFORE_DATE, EXPIRATION_DATE or NO_DATE_MARKED.

  • 500.531 (changed): checks that only these three values are used.
  • 500.676 (new): checks that one of these values is filled when Minimum trade item lifespan from time of arrival (minimumTradeItemLifespanFromTimeOfArrival) is filled.

Action: if you fill the minimum lifespan from time of arrival, check that the date on packaging type is filled with one of the three values.

3. Packaging type and packaging material

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

  • 500.659: Aerosol (AE), Barrel (BA) and Bag-in-Box (BBG) need at least 2 packaging materials.
  • 500.668: Bag (BG) with aluminium (METAL_ALUMINUM, ALUMINUM_OXIDE or METAL_ALUMINUM_METALLIZED) needs at least 1 other packaging element.
  • 500.664 and 500.675: Can (CNG) may only have packaging materials from the GS1 code lists for cans (Benelux_500664PackagingMaterialTypeCodeListSegment and Benelux_500675PackagingMaterialTypeCodeListSegment).
  • 500.671: Carton (CT) may not have GLASS as packaging material.
  • 500.661: Envelope (EN) may not have GLASS as its only packaging material.
  • 500.670: Jar (JR) may not have only paper materials (PAPER_CORRUGATED, PAPER_KRAFT, PAPER_KRAFT_WET_STRENGTH, PAPER_MOLDED_PULP, PAPER_OTHER, PAPER_PAPER, PAPER_PAPERBOARD or PAPER_RAYON). The code list Benelux_500670PackagingMaterialTypeCodeListSegment supports this rule.
  • 500.685: Packaging level must be 1 or higher.

Action: check the packaging type and packaging materials of your Sales Units against these rules.

4. Product image

Validations 500.267 and VR_FMCGB2C_0385 are merged into one rule. From the Start availability date time (startAvailabilityDateTime), every new or changed consumer unit needs at least one product image: a file with type PRODUCT_IMAGE, a file name and a link.

Action: check that every consumer unit you publish has a product image linked.

5. Regulation type: CE marking and biocides

The instructions for Regulation type (regulationTypeCode) are clarified:

  • For products with a CE marking on the product, the packaging or the documentation, use the value CE.
  • For biocidal products, use BIOCIDE_REGULATION. For products treated with biocides, use TREATED_WITH_BIOCIDE_REGULATION.

A new validation checks the CE marking:

  • 500.688: when Third party accreditation symbol on product package code (packagingMarkedLabelAccreditationCode) is CONFORMITE_EUROPEENNE, at least one Regulation type must be CE.

In the usage notes of Regulation compliance indicator (isTradeItemRegulationCompliant), the sentence about biocides has been removed.

Action: if your products show the CE logo, check that Regulation type CE is filled.

6. Recycled content: PCR and PIR

GS1 now has separate codes for recycled content in Packaging raw material code (PackagingRawMaterialCode):

  • RECYCLED now means post-consumer recycled content (PCR) only.
  • The new code PRE_CONSUMER_RECYCLED_CONTENT is for post-industrial recycled content (PIR).

SyncForce already records PCR and PIR separately, so only the mapping changes. SyncForce now sends PIR as PRE_CONSUMER_RECYCLED_CONTENT. You do not have to do anything.

More about the difference: What is the difference between PIR and PCR recycled content, and how does SyncForce map this to GS1?

7. Protected origin labels

In the code list PackagingMarkedLabelAccreditationCode, the code names for protected designation of origin and protected geographical indication have changed. The new names make clear which codes are for the EU and which are for Switzerland.

SyncForce has updated the mapping. You do not have to do anything.

8. Other attribute changes

These changes are about definitions and instructions only. Your data does not change.

  • Preparation type code (preparationTypeCode) and Preparation instructions (preparationInstructions): definitions aligned with the global data model.
  • Usage instructions (consumerUsageInstructions): the Dutch condition now includes "When it is indicated on the label", in line with the other languages.
  • Servings per product precision code (numberOfServingsPerPackageMeasurementPrecisionCode), Regulation type code, Regulation compliance indicator and Target skin type (targetSkinTypeCode): definitions aligned with the global definitions.
  • Usage during pregnancy code (usageDuringPregnancyCode) and Usage during breastfeeding code (usageDuringBreastFeedingCode): instructions clarified.

9. Other validation changes

Several local validations are removed or simplified, because global GDSN validations now cover them:

  • 500.068 / VR_DIY_B2B_0027: removed (covered by global validation 1025).
  • VR_FMCGB2C_0101: rule description simplified (covered by global validation 1440).
  • 500.275 / VR_BASIC_0040: target markets NL, BE and LU removed (covered by global validation 1989).
  • VR_FMCGB2B_0508 and VR_TAXES_0018: removed (covered by global validation 2107).

Two DIY validations change:

  • 500.620 / VR_DIY_B2B_0074: changes from a warning to an error.
  • 500.589 / VR_DIY_B2B_0057: REPAIRABILITY_INDEX must be filled in exactly one instance of Sustainability programme code (sustainabilityProgramCode). This is an error.

10. Benelux code lists

  • French translations have been added to: CatchAreaCode_GDSN, BNL_NutrientTypeCodeList, NutritionalProgramIngredientTypeCodes, PackagingFeatureCodes, PackagingMaterialTypeCode, PreparationTypeCodes and AdditionalTradeItemClassificationCodeListCode.
  • BNL_NutrientTypeCodeList: the code values are aligned with the GDSN names.
  • BNL_WarrantyTypeCodeList: new, see section 1.
  • ElectricalAppliancesGPCCodeList: brick 10002208 removed, bricks 10008514, 10008516 and 10008518 added, and the names of brick 10005397 updated.

11. GDSN 3.1.37 code list changes

The November 2026 GDSN release adds and changes codes in many GDSN code lists. Some examples:

  • RegulationTypeCode: new codes for the Ecodesign for Sustainable Products Regulation (ECODESIGN_REGULATION) and for tyre labelling (TYRE_LABELLING_REGULATION).
  • ReferencedFileTypeCode: 8 new file types, for example Environmental Product Declaration (EPD) and Nordic Swan Ecolabel declaration (SVANEN_DECLARATION).
  • PackagingMarkedLabelAccreditationCode: 6 new certification labels.
  • SpecialItemCode: new codes for products that are not eligible for eco-cheques or employee meal vouchers.
  • TradeItemDateOnPackagingTypeCode: 2 codes changed.
  • CountryCode: 31 codes added.

Other code lists with changes: AdditionalTradeItemIdentificationTypeCode, AllowedUsageCode, CfpBoundariesCode, CfpMethodologyCode, ConsumerSalesConditionTypeCode, ContactTypeCode, FeatureCode, GrowingMethodCode, PreparationTypeCode, ProductCharacteristicCode, ReferencedTradeItemTypeCode, SkinProductFunctionOrTreatmentCode, SterilisationTypeCode, TargetSkinTypeCode, TaxCategoryCode and TradeItemTemperatureConditionTypeCode.

12. GPC

GS1 Global updates the GPC codes. You find all English and Dutch GPC codes in the GPC browser: https://gpc-browser.gs1.org/

More information 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.