In KNX and building automation, the buyer's real question is 'does it work with my installation' — an answer that lives in linked attributes ETIM never carries. Where the standard helps, and where it stops.
In most retail sectors a buyer asks 'what is this product'. In building technology they ask something harder: 'will this work with my installation'. A KNX dimming actuator isn't sold on its own merits — it's sold on whether it runs the right application program, whether it's certified, whether it fits into the bus alongside everything else the electrician has already planned. The device is only half the answer; the other half is its relationship to the rest of the system.
Product data for building technology is data about compatibility: the value is not in the single device but in its verified place inside a KNX system. That shifts the whole data problem. This is a sub-branch of electrical wholesale, but with a twist that pure component trade doesn't have — and it sits right next to consumer smart home, which shares the interoperability logic at a lighter scale.
The familiar multi-supplier pain — no two suppliers deliver alike — is here layered on top of a compatibility problem that flat data can't express:
Maintain this by hand across firmware updates and you fall behind fast. The fix is the same discipline as everywhere — consolidate, normalize, enrich and publish — but here the enrichment has to respect that compatibility is a relationship, not a lone value.
Building technology inherits the connecting grid of the electrical trade: ETIM, the international classification for technical products, usually delivered as BMEcat from manufacturers and wholesalers. ETIM is genuinely strong — it puts a KNX actuator in the right feature group with a defined set of attributes. But it's a classification, and the interoperability layer is a different thing:
| Data layer | What ETIM / feeds deliver | Where it stops |
|---|---|---|
| Article classification | ETIM class puts the device in the right feature group | No modeled relationship between compatible devices |
| Core master data | BMEcat from big manufacturers & wholesalers | Thin for direct suppliers & accessory brands |
| System / interoperability | Partial, brand-dependent | KNX certification, application program, ETS version often missing |
| Compatibility facts | Not the job of a classification | Which gateway fits which actuator lives in PDFs |
| Sales content | Not carried | Descriptions, benefit copy, SEO text absent |
In short: ETIM gives you a clean skeleton and the wholesaler feeds cover the branded core well. What they don't give you is the certified compatibility relationships, the application-program references, or the sales content — and in building automation that layer is the whole purchase decision.
The throughline is a three-step job, run with the compatibility layer treated as first-class data — and that's what Productbay is built for:
Crucially, Productbay starts where ETIM and the feeds end. The classification and the branded core stay as they are; Productbay adds the certified compatibility layer, the application-program references and the sales content no standard provides. For the broader picture see electrical wholesale and the neighboring consumer smart home case. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains.
KNX certification, application programs, bus load, ETS versions — building technology data is only useful when the compatibility relationships are modeled. See how Productbay keeps linked system attributes clean and current in a 30-minute walkthrough.
Get started