Product Data for Kitchens: Configuration and Appliance Integration

Two logics in one catalog: the combinatorial configuration of the furniture and the deep technical attributes of built-in appliances — where ETIM helps, and where it stops.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Kitchens are the most configurable furniture category: fronts, carcasses, handles and worktops combine into thousands of sellable variants.
  • On top sits appliance integration — built-in ovens, hobs, dishwashers and fridges bring their own deep technical attributes and PDF datasheets.
  • ETIM covers appliance attributes well, but models neither the configuration logic nor the sales content of the furniture side.
  • Productbay holds configuration and appliance data in one catalog with linked attributes, and uses AI enrichment where the standard stops.

No furniture category configures like a kitchen. A single kitchen front exists in a dozen decors, several widths and both a handled and a handleless version — and every one of those combinations is a sellable variant with its own price, image and dimensions. Then, on top of the furniture, sit the built-in appliances: an oven, a hob, a dishwasher, a fridge, each carrying a two-page technical datasheet. Two data logics — combinatorial furniture and attribute-rich appliances — meet in the same catalog.

Product data for kitchens are split between two logics: the configuration logic of the furniture and the attribute logic of built-in appliances. That split is what makes kitchens the hardest furniture segment to maintain. This is a sub-branch of the broader furniture retail challenge, and it borrows heavily from consumer electronics on the appliance side.

What makes product data for kitchens so difficult?

Every multi-brand retailer knows the base problem — no two suppliers deliver alike. Kitchens amplify it because you are maintaining a configuration, not a flat article list:

  • Combinatorial variants: fronts, carcasses, handles, worktops and decors combine into thousands of sellable configurations, each with its own price and dimensions.
  • Appliance integration: built-in ovens, hobs, dishwashers, extractors and fridges bring deep technical attributes — energy class, dimensions, connection values — often delivered as PDF datasheets.
  • Fit dependencies: an appliance only fits certain carcass widths, a hob needs a matching worktop cutout — the two logics are not independent, they constrain each other.
  • Constant range updates: decors, appliance model years and price lists rotate, so the catalog is never static — new SKUs and EAN/GTIN keys land regularly.

Do this by hand across a full kitchen assortment and it doesn't scale. The fix is the same as everywhere: consolidate, normalize, enrich and publish — but here you have to keep two coupled data worlds consistent.

Which standard covers kitchen appliances — and where does it stop?

The appliance side does have a connecting grid: ETIM, the technical classification with defined attribute groups. ETIM carries built-in appliances reasonably well — energy class, dimensions, connection values are all modelled. But ETIM was built for electrical and technical trades, not for furniture, so it only solves one half of a kitchen:

Data layerWhat ETIM deliversWhere it stops
Appliance attributesEnergy class, dimensions, connection values for built-in appliancesNothing for the furniture side
Configuration logicNot modelledFronts, carcasses, decors, worktops uncovered
Fit dependenciesNot modelledAppliance-to-carcass links absent
Sales contentNot the job of a classificationDescriptions, SEO text, benefit copy absent
Images / mediaNot coveredFront decors and appliance imagery missing

In short: ETIM cleans up the appliance attributes and gives you a classification skeleton on that side. What it does not touch is the configuration logic of the furniture, the fit dependencies between the two, or the sales content. That is the gap.

How does Productbay help kitchen retailers?

The throughline is a three-step job, run for both data worlds and kept linked — and that's exactly what Productbay is built for:

  • Consolidate: import every source once — supplier CSV, Excel, feed URL, FTP, API — and match by SKU or EAN/GTIN so existing products update and new ones are created. Furniture configuration data and appliance datasheets land in one catalog.
  • Link and enrich: AI reads appliance specs out of PDF datasheets, writes descriptions, assigns categories, fills missing attributes from whitelisted sources and translates via DeepL — and appliance attributes stay linked to the furniture variant they belong to, always with a review queue before publishing.
  • Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp), and feed exports for Amazon, OTTO and Kaufland — each with per-channel transformations.

Crucially, Productbay picks up where ETIM ends. If a standard already carries your appliance attributes, great — Productbay complements it, models the configuration logic the classification never touched, keeps appliance and furniture data consistent, and adds the sales content no standard provides. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains.

Frequently Asked Questions

Let's look at your product data process

Configuration matrices and appliance datasheets, fronts and energy classes — kitchens pack it all into one catalog. See how Productbay consolidates, links and publishes both data worlds in a 30-minute walkthrough.

Get started