Product Data for Sleep & Beds: Dimensions, Firmness, Systems

Dimensions, firmness (H1–H5) and core systems are the attributes that sell a mattress — but suppliers deliver them in five different formats. Making them mandatory and comparable is the whole job.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Beds & mattresses are a technical-precision category: dimensions, firmness grades (H1–H5) and core systems are the attributes shoppers filter and compare on.
  • The pain isn't missing data — it's inconsistent delivery: one supplier writes 140x200, another „Doppelbett“; firmness comes as text, number or code; no binding standard ties it together.
  • General classifications (eCl@ss, ETIM) group the article but don't enforce your mandatory attributes or normalize the units for you.
  • Productbay turns dimensions, firmness and core system into mandatory attribute groups, normalizes them into one scale, and uses AI to fill them from Excel and PDF datasheets.

A mattress is a deceptively simple product to sell and a hard one to describe. Nobody buys it for the brand story — they buy it for a firmness that matches how they sleep, a size that fits their frame, and a core system they can compare against the one next to it. Every one of those is a precise, filterable attribute. And in a multi-supplier catalog, every one of them arrives in a different format.

Product data for beds and mattresses is a matter of technical precision: dimensions, firmness grades and core systems have to be mandatory, normalized attributes — or the category simply doesn't work as a filterable shop. This is a focused sub-branch of the broader furniture retail challenge: furniture in general is variant- and dimension-heavy, but the sleep category pushes attribute precision the furthest.

What makes product data for beds and mattresses so hard?

The problem isn't that the data is missing — it's that the same attribute arrives in incompatible shapes from every supplier:

  • Dimensions, five ways: one supplier writes „140x200“, another „Doppelbett“, a third splits width, length and height into three centimeter columns, a fourth gives a size name only. To build a size filter you need clean numeric width, length and height in one unit.
  • Firmness with no binding norm: the H1–H5 scale is a manufacturer convention, not a certified standard. One brand's H3 is another's H2 — and it may arrive as text („medium“), a number, or a code.
  • Core systems as free text: cold foam, pocket spring, latex, gel, bonell — described in prose, spelled differently per supplier, rarely in a clean enum you can filter on.
  • Certifications buried in datasheets: OEKO-TEX and similar marks that shoppers actively look for often sit in a PDF, not a structured field.

Do this by hand and it doesn't scale — and half-filled records reach the shop. The fix is the same discipline as everywhere: consolidate, normalize, enrich and publish — but here the normalization step carries almost all the weight.

Which standard applies — and where does it stop?

You might expect a classification like eCl@ss or ETIM to solve this. They help — they give the article a group and a shared vocabulary — but they were built to classify, not to enforce your mandatory attributes or to normalize supplier units for you. Here's the honest split:

Data layerWhat eCl@ss / ETIM deliverWhere it stops
Article groupingClassifies „mattress“ or „bed frame“ into a classDoesn't enforce which attributes are mandatory in your shop
DimensionsDefines attribute slots for width/length/heightDoesn't normalize „140x200“ vs. „Doppelbett“ for you
Firmness gradeNo binding H1–H5 norm existsText vs. number vs. code stays inconsistent
Core systemPartial value listsFree-text supplier wording rarely maps cleanly
Sales contentNot the job of a classificationDescriptions, SEO text, benefit copy absent

In short: a classification gives you a skeleton and a shared language, but it doesn't do the two things that actually hurt in this category — making your key attributes mandatory, and normalizing five delivery formats into one comparable scale. That's the gap.

How does Productbay help with beds and mattresses?

The throughline is turning loose supplier data into mandatory, normalized attribute groups — 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.
  • Attribute groups with required fields: define dimensions (width, length, height as numeric fields), firmness grade, core system, weight capacity and certifications as a mandatory group — so a record can't reach the shop half-filled.
  • Enrich: AI reads dimensions, firmness and core system out of titles and PDF datasheets, normalizes „140x200“ and „Doppelbett“ into one numeric structure, maps firmness onto one scale, writes descriptions and translates via DeepL — 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.

Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains. For the wider category picture, see the furniture retail overview.

Frequently Asked Questions

Let's look at your product data process

Dimensions, firmness grades, core systems — the sleep category runs on precise, mandatory attributes that suppliers deliver inconsistently. See how Productbay normalizes them into one structure and fills them from Excel and PDF in a 30-minute walkthrough.

Get started