Publication of the new GS1 Benelux datamodel DIY, garden & pet (February 2026)
The new version of the GS1 Benelux data model for the DIY, garden & pet sector (3.1.34) has been published. It will go live on 21 February 2026. Retailers will receive data according to the new data model from then on. Suppliers should therefore ensure that any changes have been implemented by then.
Most common error messages and solutions
Error message
The attribute 'Tax type code' must at least be filled once and no more than once with one of these values: 'BTW' or 'VAT' and the attribute 'Tax category code' must be filled at least once with one of these values: 'HIGH', 'LOW', 'ZERO' or 'EXEMPT' in the same iteration.
What?
Please complete the taks information per target market seperately with the code BTW/VAT/TVA in combination with the code that refers to the correct VAT %. To indicate a VAT of 21% you should use for
- Begium the code STANDARD
- The Netherlands the code HIGH
How?
Option 1 - Bulkaction
(Only if no other taxes like excises, ecotrel, … are used)
- Go to 'My products
- Set filter as ‘Discontinued' = 'No'.
If you have different taxes based on GPC codes, this can be an extra filter. - Select all and choose ‘edit in bulk’
- After the view with the selected items, you get in a new screen with 2 selections
- Set the question ‘Release product after bulk action’ to ‘Yes’.
- Choose for ‘Update attributes', open ‘Taxes’ and select ‘Tax information per target market’.
- Complete the tab and confirm. This will overwrite the existing information.
Optie 2 - Excel
- Correct the information in 1 productsheet, save and release.
- Go back to ‘My Products’.
- Set filter as ‘Discontinued' = 'No'.
- Select all, choose ‘Export’ and follow the steps.
- Search in the Excel for ‘Taks informartion par target market’, filter on 1 target market and check/update the tax category code (528 = HIGH, 056 = STANDARD). Do this for all target markets in that column and the other columns with that name.
- Save your Excel and upload it through ‘My actions’.
Error message
If 'pallet type code' is filled out, 'packaging type code' is also mandatory
What?
If you fill in the field “Code type pallet”, you must also fill in the field “Code type packaging” with the code “PX” (pallet). The pallet is then considered a type of packaging in that section of the Packaging Information.
Attention regarding the field ‘Pallet type code’
This field is mandatory when you enter pallet information in your item sheet. Only fill it in either in the pallet’s own sheet or in the sheet of the product placed on the pallet if you are not creating a separate pallet sheet.
Concretely: In a hierarchy with a base unit and a case that also contains pallet information, you only fill it in on the sheet of the case.
For the case, you will then have two ‘Packaging Information’ sections:
One for the item placed on the pallet
One for the case itself
Below is how you should complete the relevant fields for a case that is placed on a pallet.
| Section 1 = case | Section 2 = pallet |
Packaging type code | BX (box) | PX (pallet) |
Packaging level | 2 | 3 |
Pallet type code |
| 11 (80x120 europallet) |
How?
From the simulation report, we identified several scenarios that triggered the error. Because of this, a single unambiguous instruction is not possible, but we would like to share a few tips with you.
Use the bulk action if you:
Attention: bulk actions will overwrite your data, not add data.Do not provide packaging details in your product sheet
Need to re‑enter the data per packaging type. Example: base units are bottles (which do not contain pallet information) and all outer packaging are cases (which do contain non‑GTIN pallet information)
Only have pallets and the two fields were filled in, but in separate sections. In that case, you can re‑enter them in a single section using the bulk action.
Working via Excel is possible to:
Remove the column ‘pallet type code’ from all items that are not the highest level of a hierarchy (e.g., base unit, inner pack, …)
Once one sheet (e.g., the case) is correctly completed, copy this change to the other sheets of the same category
If you need advice or have doubts, email support@gs1belu.org so we can review your specific cases together and resolve them with you.
Error message
(GDSN-575) Invalid value for consumer unit flag. A trade item with GTIN 14 is always a non-consumer unit.
What?
GTIN 14’s are used to identify logistic units, which aren’t scanned at a point of sales and are by instance not consumer units.
How?
Scenario 1: I assigned a GTIN14 to my case, display, pallet, … and marked it as a consumer unit.
- Go to ‘My Actions’, click ‘Start bulk action’, and choose ‘Export products’.
- Add the GTINs from the error report to the export menu and start the export.
- In the Excel file, search for ‘Is it a consumer unit?’ and change ‘TRUE’ to ‘FALSE’ in that column.
- Save your Excel file and upload it in MPM via ‘My actions’
Scenario 2: I assigned a GTIN‑14 to my inner packs for Colruyt.
Colruyt is aware of this and will provide GTIN‑13s for inner packs in the future. Follow the steps described in Scenario 1 to mark the items as non‑consumer units
Other scenario? Contact our support team: support@gs1belu.org.
Error message
The field Batteries required indicator shall be filled out with 'true' because the field 'Number of batteries required' is used.
How?
Attention: the relevant field will only be available after the release!
- Look up one item sheet in the interface and update the data. Save and release it.
- Go to ‘My Actions’, click ‘Start bulk action’, and choose ‘Export products’.
- Add the GTINs from the error report to the export menu and start the export.
- In the Excel file, search for 4.297 and enter the value ‘TRUE’ in that column.
- Save your Excel file and upload it in MPM via ‘My actions’.
Error message
As off the Start availability date time, at least one product image shall be present for new and changed consumer units, where the fields File name and Uniform resource identifier are used and Referenced file type code equals PRODUCT_IMAGE or MOBILE_READY_HERO_IMAGE.
What?
In addition to the stricter requirements in the FMCG sector regarding product images (November 2025), submitting a hero image as a packshot will also be accepted.
More info
How?
You can add a product image in two ways:
- Upload the image directly in the web interface via My Product Manager.
- Add the image URL directly in the product sheet (or via Excel).
Technical specifications for image URLs:
- The URL must be publicly accessible (no login required).
- The URL must point directly to the image, not to a webpage containing the image.
- The URL must support a HEAD call.
- The URL must include a content length so the system can validate the file size upon download.
- The DAM system must be able to process the request within a reasonable time, without time-out.
- If the DAM returns an error message (e.g. HTTP 429: too many requests), a validation error will be raised.
Key changes:
- Changes to validations for phased data submission to make this way of working easier to use.
- Addition of a validation warning that information related to ECOCHEQUES must be completed for the Belgian target market.
- The annually changing codes for INTRASTAT and Bebat/Stibat have been updated to the most recent version.
- Validation to prevent entering a VAT code too frequently.
- Activation of GPC bricks for party clothing and related accessories, biscuit dowels and whistling kettles.
- Harmonisation with retailers’ systems of various GPC bricks for sledgehammers, hammers, chisels, gouges, spanners, pliers, clamps and saws.
Expired attributes
From 21 February, certain attributes will be discontinued. For several of these discontinued attributes, replacement attributes are available and can be found in the published data model.
The discontinued attributes include:
- The merging of GPC bricks for doors, so that separate pick lists for interior and exterior doors are no longer needed.
- Where possible, we align with attributes that are now available internationally.
More information
The new data model (incl. change datamodel with all changes) and the overview of the validation rules can be found on our website in Dutch, French and English. In the data model itself, all the changes vs version 3.1.33 have a yellow background.
Questions? Contact us via diy@gs1belu.org or call +32 2 229 18 88.
