Skip to main content

2BA Product Data: What Suppliers Must Deliver to the Dutch Data Pool

How to deliver product data to 2BA: product vs trade item records, mandatory fields, price units, file formats and what Technische Unie expects.

Diego Nijboer

2BA Product Data: What Suppliers Must Deliver to the Dutch Data Pool

2BA is the Dutch data pool for the installation and technical trade. Manufacturers, importers and agents publish their product and trade item data there once, classified in ETIM, and wholesalers and installers subscribe to it instead of collecting a spreadsheet from every supplier. If you sell to Dutch installation wholesalers, 2BA is the route your article data is expected to take.

Delivering takes four things: a GLN for your company, a 2BA account, an export in a format 2BA reads (DICO SALES005, ETIM xChange or BMEcat 2005 with ETIM), and data that covers the fields your buyers mark as mandatory. The wholesalers are explicit about it. Technische Unie writes in its supplier delivery instructions that it exchanges product data exclusively through 2BA and expects updates at least once a week.

Who publishes to 2BA and who reads the data

The manufacturer is the source. An importer or agent can be appointed to deliver on a manufacturer's behalf: the product records then go in under the manufacturer's GLN and brand, the trade item records under the importer's own GLN, and the right is temporary and only granted in consultation with 2BA. Wholesalers cannot supply product data at all, apart from OEM or own-brand products (2BA, step 3 of the manufacturer roadmap).

What wholesalers do add is their own trade information on top of your product: their own gross prices, packaging units and GTINs. On the other side of the pool, installers search the data from their own software through 2BA's Unifeed search engine. The order of Unifeed results depends partly on data richness: whether a product has an ETIM class, filled feature values, a product image, and whether the supplier is current with its agreed delivery frequency (2BA Data Label).

How supplier data moves through 2BA

Loading diagram
The supplier approves each delivery after reading the processing report; wholesalers and installers only receive what was published.

Every delivery runs through automatic checks, some of them against the data already in the pool. You then get a statistics tab that compares the delivery with what 2BA holds and a checks tab with the result per check. Only after you have accepted both does the approve button become active; you approve or reject the data, and approved data shows up in Unifeed the next day (2BA, publishing a file). Treat that report as the acceptance test for your first upload.

Product record and trade item record: the split 2BA is built on

2BA keeps two linked records. The product record says what the thing is: product code, product GTIN, brand, series and type, descriptions, ETIM class and features, and attachments. The trade item record says how it is ordered: order number, trade item GTIN, packaging code, minimum order quantity, order multiple, gross price, price units and logistic data. One product can have several trade items, and a wholesaler can link its own trade items to your product.

The split catches a common supplier habit: a cable sold per metre, per 100 m roll and per 500 m reel entered as three products with copied specifications. In 2BA that is one product with three trade items, each with its own GTIN and article code. Technische Unie makes the same point with a lamp sold singly and in a box of twelve: both units need their own EAN, and the order confirmation, packing slip and invoice must use the unit on the purchase order.

Two product fields deserve a decision before the first file. Series and type are used for filtering on wholesaler webshops; if a product line has none, 2BA lets you send the value RNV_NA instead of an empty field. And products that go out of production stay in the pool with status code 130, because wholesalers may still sell their stock and installers still look up manuals and successors.

Reading 2BA's own cable reel example

Price units cause more broken files than any other field group, because the unit you price in is often not the unit you sell in. 2BA documents this as the unit triangle and publishes worked examples. In one of them, a cable without plug comes on a 500 m reel and is priced per 1,000 m:

2BA's demo trade item: a 500 m cable reel priced per 1,000 m

Packaging codeRL (reel)The orderable unit is one reel
Gross priceEUR 1,000List price for the price quantity below
Number of price units per price1,000 mThe gross price covers 1,000 m
Quantity of use units500 mOne reel holds 500 m
Price to order unit factor500Sets the price of one order unit: EUR 1,000 / 1,000 × 500 = EUR 500
Minimum order quantity1At least one reel
Order multiple1Whole reels only
Price of one use unitEUR 1Per metre
Price of one order unitEUR 500Per reel
Showing 9 of 9 rows
Values from 2BA's own unit triangle example: the gross price field says EUR 1,000, yet one reel costs EUR 500.

If your ERP export carries only "price 1000, unit m", a wholesaler's system has to guess whether that is per metre, per reel or per 1,000 m. All three numbers (price quantity, use units per order unit and the conversion factor) have to travel together. Our unit of measure article covers how to store sales, content and price units so they export consistently.

The fields Dutch wholesalers mark as mandatory

2BA's Data Requirements Overview 2025 (version 3.0.0) lists every field per target group: Dutch installers, Dutch wholesalers, Belgian wholesalers and the maritime sector. Mandatory fields block the data from going live. Essential fields are needed for primary processes and have to follow within three to four months. Below that come strongly desired and nice to have.

What Dutch and Belgian wholesalers require in 2BA's Data Requirements 2025

GLN supplierTrade itemMandatoryMandatory
Trade item ID (order number)Trade itemMandatoryMandatory
Trade item GTINTrade itemEssentialMandatory
Short descriptionBothMandatoryMandatory
Description in DutchBothMandatoryMandatory
Description in FrenchBothNice to haveMandatory
Minimum order quantityTrade itemMandatoryMandatory
Order multipleTrade itemMandatoryMandatory
Gross priceTrade itemMandatoryMandatory
Allowance (discount) groupTrade itemMandatoryMandatory
Packing type codeTrade itemMandatoryMandatory
Minimum delivery timeTrade itemEssentialMandatory
BrandProductMandatoryMandatory
Model (series)ProductMandatoryStrongly desired
Product GTINProductEssentialMandatory
ETIM product classProductMandatoryMandatory
Filled ETIM featuresProductEssentialEssential
Product picture (low resolution)AttachmentMandatoryMandatory
Showing 18 of 18 rows
A selection from version 3.0.0 of the overview: GTIN and delivery time are essential for Dutch wholesalers but already mandatory for Belgian ones.

Three things stand out. The allowance group (kortingsgroep, the discount group a wholesaler's net price is calculated from) is mandatory, and it is the field supplier spreadsheets forget most, because it lives in the commercial agreement rather than in the product master. The [GTIN](https://wisepim.com/guides/gtin-vs-upc-vs-ean) is only essential for Dutch wholesalers in 2BA's matrix, but Technische Unie requires an EAN for all communication with it. And the overview lists a reason no value field, so an ETIM feature you cannot fill can say why instead of staying blank. Our ETIM classification walkthrough shows how to keep not applicable apart from not yet known.

For the ETIM side, 2BA's base version is the most recent static release ETIM International has published, and in November 2026 that was ETIM 10. Data recipients choose between the base version and ETIM Dynamic, which includes newly approved classes (2BA and ETIM). ETIM International has planned ETIM 11.0 for 1 December 2026, so check which release your buyers download before you classify a new range. Our ETIM guide explains classes, features, values and units if your team is new to the model.

DICO, ETIM xChange or BMEcat: choosing a delivery format

The requirements overview names three current exchange formats. DICO (SALES005) is the Dutch XML standard from Ketenstandaard Bouw en Techniek and 2BA's preferred format. ETIM xChange is ETIM International's JSON format. BMEcat 2005 with the ETIM guideline 5.0 is the XML catalog format ETIM International recommended before it released xChange; our BMEcat guide walks through its structure.

Which one you use depends mostly on what your software exports, but the formats do not carry the same fields. In 2BA's overview, ETIM xChange is the only one with a place for the WEEE category, the customisable product flag and the packaging recyclable and reusable flags. DICO has no place for warranty periods, the SCIP number or keywords. BMEcat 2005 5.0 lacks alternative use units and the packaging stackable flag. If a buyer marks one of those fields as needed, the format decides whether you can deliver it.

This is why Technische Unie asks its suppliers to export to 2BA in ETIM xChange. 2BA converts between formats internally, but according to Technische Unie only a complete dataset, including sustainability features, converts properly.

What Technische Unie asks of suppliers

Technische Unie publishes its rules in a document called Aanleverinstructies Purchase to Pay. On product data, it asks for the following:

  • Product data before the first order. At minimum the trade data (description, price, EAN and order unit) plus legally required documents such as a safety data sheet or a conformity certificate where they apply. ETIM features, images and other digital assets are processed too.
  • 2BA first. Technische Unie subscribes to your data in 2BA. Its Excel template is only for suppliers with a separate agreement with their product manager, needs every mandatory field filled, and its format must not be changed.
  • Six weeks of lead time. Most changes need to be in at least six weeks before the first order moment, so updates must be published to 2BA at least weekly.
  • One EAN per sellable or tradable unit, used identically in every order message, and every packaging form of a product declared.
  • Range changes agreed with the product manager. Changes to the stocked range are still agreed with the product manager, even after they are published in 2BA.

Prices follow a quarterly calendar. Technische Unie gives its customers a fixed price per quarter, so price changes only take effect on 1 January, 1 April, 1 July or 1 October. The supplier announces a change by email three months ahead, sends discount group changes eight weeks before and the article file with the new price list six weeks before. For a 1 January change, those dates are 1 October, 6 November and 20 November; changes delivered late move to the next quarter.

Five reasons a 2BA delivery comes back weak

  1. Packaging forms entered as products. The 100 m roll and the 500 m reel become separate products with copied specifications, so features drift apart and the links between trade items and product break.
  2. The price basis gets lost. The export carries a price but not the price quantity or conversion factor, and the wholesaler's system reads EUR 1,000 per metre.
  3. A class without features. The product has an ETIM class but most features are empty, which leaves it hard to find in filters and ranks it lower in Unifeed.
  4. Commercial fields missing. Discount group, minimum delivery time and packing type code sit in contracts or in the head of a sales manager, not in the item master.
  5. Updates arrive in batches. A supplier that publishes once a quarter misses Technische Unie's six-week window for every change in between.
Blocking rules stop products without a valid GTIN or a main image before they reach an export.

Most of these are not 2BA problems. They start in an ERP that was built to invoice, not to describe products, and they surface when the data has to be classified and complete for the first time.

Classifying and completing article data before it reaches 2BA

WISEPIM has no 2BA connection and does not publish to the pool for you. Where it helps is the step before: turning an ERP article export into ETIM-classified, complete product data that your 2BA software or account can deliver.

An ERP export mapped column by column; the saved import profile is reused for the next delivery and flags changed columns.
  • Import the ERP export as CSV or Excel with a saved import profile, so the next delivery reuses the mapping and the app flags columns that changed.
  • Classify in ETIM 10.0, the release 2BA used as its base version in November 2026, with the optional Classification module. Classes are adopted per product family and the products inherit them; Mapping review suggests links from your own attributes to ETIM features, and a person approves each one.
  • Fill and check features. Auto-fill with AI fills only missing or invalid features and re-validates every value; the ETIM Conformance score shows how many class features are valid per product.
  • Block incomplete products with Quality Guard rules, for example no export without a valid GTIN.
  • Export BMEcat 2005 (ETIM) from Feed Hub, one of the formats 2BA lists. Products whose family has no ETIM class are left out. WISEPIM does not write DICO or ETIM xChange, and the export has no GLN or discount group fields, so check the file against 2BA's BMEcat mapping and the processing report before the first live upload.

If you want a second pair of eyes first, our free data readiness check is a person reviewing one supplier file with you on a call, including which ETIM classes and fields are missing.

Diego Nijboer

CTO and Co-Founder at WISEPIM, building AI-powered solutions that transform product data management for e-commerce businesses. Over 10 years of experience solving complex technical challenges in e-commerce and PIM systems.

Frequently asked questions

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

No. According to 2BA, wholesalers cannot supply product data, except for OEM or own-brand products. They add their own trade information to the manufacturer's product. A manufacturer can appoint an importer or agent to deliver on its behalf; the product data then goes in under the manufacturer's GLN, and the right is temporary and arranged with 2BA.

2BA's base version is the most recent static release published by ETIM International; in November 2026 that was ETIM 10. 2BA also follows ETIM Dynamic, which includes classes and features approved since that release, and data recipients choose which of the two they download. ETIM International has planned ETIM 11.0 for 1 December 2026, so check the base version on 2BA's ETIM page before you classify a new range.

They stay in the pool. 2BA asks suppliers to keep the product data available and mark the product with status code 130, because wholesalers may still sell remaining stock and installers still need manuals, certificates and the successor product. Removing the record breaks those lookups, so change the status and add a successor reference instead.

Only by exception. Its delivery instructions say all product master data should come through 2BA. A supplier that has a separate agreement with its Technische Unie product manager can use the TU Excel template, with every mandatory field filled and the template format unchanged, sent to the purchasing support team for the product group. The six-week lead time applies to the template route as well.

It is 2BA's measure of how complete a supplier's product and trade data is for each target group, such as Dutch wholesalers or installers. It was developed with wholesalers and end users and shows which data components fall short. Classified products with filled features and images also rank higher in 2BA's Unifeed search results.

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7