Ketenstandaard Bouw en Techniek is the Dutch foundation that manages the data and message standards of the building and installation chain: ETIM in the Netherlands, the DICO message standard, STABU, and the use of GS1 numbers in the sector. It writes the agreements; it does not hold product data itself. That is the job of the 2BA data pool, which runs on these standards.
Many people still search for it under its old name, Ketenstandaard Bouw en Installatie. For a supplier the practical meaning has not changed: classify your products in ETIM, identify your company with a GLN and every orderable unit with a GTIN, send product and article data in DICO or ETIM xChange, and exchange orders and invoices as DICO messages. Technische Unie calls following these standard agreements "an absolute must" in its supplier delivery instructions.
From Bouw en Installatie to Bouw en Techniek
The name changed in September 2019, when STABU and Ketenstandaard Bouw en Installatie merged and continued as Stichting Ketenstandaard Bouw en Techniek (Computable). Before the merger, Ketenstandaard offered two standards: ETIM for classifying technical products and the Sales standard for electronic communication. STABU brought its specification system for building projects.
The Sales standard has since been renamed DICO. File and message names still carry the old label: 2BA's preferred format is listed as DICO (SALES005), and Technische Unie lists DICO-S@les among the formats it accepts. If a wholesaler asks for SALES005 and your software vendor talks about DICO, they mean the same family of messages.
ETIM, DICO, GS1 and STABU: what each standard governs
The Ketenstandaard standards a supplier runs into
| ETIM (Netherlands) | Product classes, technical features, values and units | Classifying every product before it goes to 2BA or a wholesaler |
|---|---|---|
| DICO (formerly SALES) | XML messages for product and article data, conditions, quotes, orders, order confirmations, delivery notes and invoices | The product feed to 2BA and the order-to-invoice flow with wholesalers |
| GS1 identifiers (GLN, GTIN, EANCOM) | Unique numbers for companies, locations and trade items, plus the EDIFACT message convention | A GLN on every file and message, a GTIN on every orderable unit |
| STABU | The specification system that specification writers use for building projects | Mostly indirect: products named in specifications for projects |
ETIM is managed internationally by ETIM International and in the Netherlands by Ketenstandaard, which submits Dutch change requests to ETIM International. Our ETIM guide covers the model itself; this post is about the agreements around it.
Ketenstandaard links the standards commercially too. An ETIM participation includes free use of the DICO article and product message and, if you want one, a single GLN (Ketenstandaard). For a manufacturer starting from zero, that is the shortest route to the identifiers and message rights a first 2BA delivery needs.
The four groups of DICO messages
DICO is a set of agreements for electronic exchange between manufacturers, wholesalers, construction, maintenance and installation companies and housing associations. Ketenstandaard sorts the messages into four groups (DICO facts):
- Data messages: product information, article data, conditions (agreed prices and discounts) and product and article relationships.
- Transaction messages: quotes, orders, order confirmations, delivery notes and invoices.
- Maintenance messages: planning, maintenance orders, status updates and fault reports.
- Rental messages: off-hire notices and their confirmations.
The messages travel over MessageService, a web service that sets up a secure connection between two parties, so nobody has to empty a mailbox or poll an FTP folder. For a manufacturer selling through installation wholesalers, the data messages and the transaction messages are the two that matter.
The DICO message chain between a supplier, 2BA and a wholesaler
Product or article: the distinction DICO and ETIM xChange share
Ketenstandaard draws a hard line between product data and article data (Ketenstandaard). Product data describes what something is and holds for every unit of it: name, ETIM class, technical features such as length, diameter and material, brand and a general description. Article data describes one sellable form of that product: article number, barcode (GTIN), price agreements and volume discounts, packaging form and quantity, stock and supplier details.
Its own example is a box of nails. The nail is the product: galvanized steel, a given length and diameter, for joining timber. A bag of 100, a box of 1,000 and a loose quantity are separate articles, each with its own article number, GTIN and price. One product, several articles. A supplier file that repeats the full technical description on every packaging line, or that puts the bag of 100 and the box of 1,000 under one GTIN, breaks this model and fails at the wholesaler.
The split also matches how often data changes. Price per 100 or per 1,000, volume discounts and stock information belong to the article and change far more often than the length or material of the product. Kept apart, a price update touches only the article data, and the ETIM features on the product stay as they were.
The ArtikelProductBericht: ETIM xChange with Dutch extensions
ETIM International launched ETIM xChange in February 2024 as the successor to BMEcat for exchanging product and article data, in a single JSON message. Many of its structures were taken from DICO. Ketenstandaard then folded ETIM xChange into DICO: the ArtikelProductBericht (ItemProductMessage) uses ETIM xChange as its base and adds Dutch extensions:
- Dutch standards and regulations: dedicated fields for norms and guidelines that apply in the Netherlands.
- Packaging information: packaging units with several packaging layers.
- Features beyond ETIM: unclassified features, or features from another classification, can travel along.
- Certificates: a fuller structure for certificates that Dutch buyers often require.
For a supplier this narrows the choice. A system that writes ETIM xChange covers the international base; the Dutch extensions are what DICO adds on top. Technische Unie asks its suppliers to export to 2BA in ETIM xChange because it carries the complete dataset 2BA supports, including sustainability features. Our 2BA product data guide compares the fields each format can carry.
How Ketenstandaard, ETIM International and 2BA divide the work
The three are easy to confuse because they appear on the same documents:
- ETIM International owns the classification model and the ETIM xChange format and publishes the official releases.
- Ketenstandaard Bouw en Techniek manages ETIM in the Netherlands, submits Dutch change requests and owns DICO.
- 2BA runs the data pool where suppliers publish ETIM-classified data and wholesalers and installers pick it up. It follows the standards; it does not write them.
- The wholesalers decide which of the allowed options they want from their suppliers, as Technische Unie does with ETIM xChange to 2BA and EDI for orders.
The split shows in ETIM 11.0, which Ketenstandaard's news of 6 November 2026 expects on 1 December 2026. ETIM International handled 2,390 change tickets for it, 466 of them submitted by ETIM Nederland, and new classes include hybrid heating systems (EC005025), building-integrated solar panels (EC005118) and AC load balancers (EC005009) (Ketenstandaard). Existing classes change too, so Ketenstandaard advises suppliers to check which of their classes are affected and agree the switch with their data manager, software vendor and customers.
What Technische Unie's supplier rules show in practice
Technische Unie's delivery instructions turn the standards into concrete demands. A supplier that is not yet a Ketenstandaard participant has to join first. New trading relationships only start once all four transaction messages run electronically: purchase order, order confirmation, delivery note and invoice, in DICO XML or the GS1 EANCOM EDIFACT convention for the installation sector. Existing suppliers get a transition period in which PDF is still accepted.
- Order confirmation within 24 hours for every purchase order, one confirmation per order, with a status code per order line (accepted, accepted with changes, not accepted, delivery date unknown).
- Same EAN and unit throughout: the confirmation, delivery note and invoice use exactly the EAN and order unit from the purchase order.
- Electronic delivery note before 06:00 on the day of delivery, one per shipment, with the delivery note number matching the paper copy.
- One invoice per delivery note, preferably as an EDI message.
- No substitutes: articles that are not on the purchase order are refused on arrival; if an item is no longer available, the supplier contacts stock management instead of shipping an alternative.
- Clean delivery notes: partial deliveries are allowed, but one delivery note never covers several purchase orders, its number stays unique for at least a year, and a multi-part article is listed with the EAN of the complete set.
Every one of these depends on clean article data. A confirmation cannot repeat the right EAN if the item master holds one GTIN for two packaging forms, and a delivery note cannot match order units that were never defined.
Six questions for your software vendor before the first DICO message
Most suppliers do not write DICO or EANCOM themselves; their ERP, EDI or PIM software does. Before you give a wholesaler a go-live date, get clear answers to these:
- Which messages and versions does it write? Technische Unie accepts order confirmations and delivery notes in EDIFACT D96A, INSBOU003 or INS008. Ask for each of the four transaction messages separately, not for "DICO support" in general.
- Does it keep products and articles apart? You need a product code that several article numbers can point to, or every packaging form ends up as its own product.
- Can it confirm per order line? Technische Unie expects a status code on every line: accepted, accepted with changes, not accepted or delivery date unknown. Technische Unie does not support a status code at header level only.
- Which delivery note level does it support? Level 1 lists quantities per article; level 4 shows which articles sit on which pallet or parcel. Technische Unie supports both and is working towards SSCC labels, which lead to level 4.
- How are messages transported? Ketenstandaard's MessageService web service, or another route the wholesaler accepts.
- Which ETIM release does the product export reference, and what happens to your classifications when you switch to ETIM 11.0?
Written answers to these six save a test round or two with each wholesaler's EDI contact. The checklist below covers the rest of the preparation.
Ketenstandaard readiness for a new supplier in the Dutch installation chain
Keeping the product side ready for DICO and 2BA
WISEPIM does not send DICO or EDI messages, has no 2BA connection and does not write ETIM xChange. Orders, confirmations and invoices stay in your ERP or EDI software. What WISEPIM handles is the product side those messages depend on.
- ETIM 10.0 classification in the optional Classification module, assigned per product family so every product in the family inherits the class. Product classification covers Mapping review, which suggests links from your own attributes to ETIM features for a person to approve.
- Feature completion with Auto-fill with AI, which fills only missing or invalid features and re-validates each value, and an ETIM Conformance score per product.
- BMEcat 2005 (ETIM) export and import in Feed Hub. The import reads a supplier's BMEcat file and fills empty fields from its ETIM features, which helps a wholesaler receiving files from manufacturers abroad.
WISEPIM has no packaging-level fields, so a product with several packaging forms needs one record per orderable article or stays in the ERP on the article side, and the product and article split described above still has to be agreed with whoever builds your DICO or xChange export. For wholesalers taking in supplier files, our page on PIM for wholesalers shows how classified supplier data feeds webshops and catalogs, and the ETIM classification walkthrough takes one supplier file through the steps.

