Duvets, pillows and toppers live on measurements, fill weights and warmth classes — and they sell as sets. Here's how to model those attributes and the set logic in one system, and where the standards stop.
A customer shopping for a duvet has already narrowed the decision to three numbers before they even read the product description: what size fits their bed, how warm they want it, and what it is filled with. Get any of those attributes wrong or missing, and the product simply doesn't get found — or gets returned. Bedding is one of those categories where the data is the product.
Product data for bedding is built on three structured attributes — size, fill weight and warmth class — plus set logic that binds a duvet to its matching pillows. This is a sub-category of the broader home textiles challenge, and it has a data profile all its own: heavily attribute-driven, variant-rich, and reliant on bundles that no supplier feed delivers cleanly.
Unlike a printed cushion cover, a duvet or pillow sells on measurable specs. The trouble is that every supplier records them differently:
Every one of these is a filter a customer uses. Normalising them into clean, comparable attributes across a dozen suppliers is exactly the manual work that doesn't scale — the same consolidate, normalize and enrich job every multi-supplier retailer faces.
The hero product in bedding is rarely a single item — it's the set: a duvet plus one or two matching pillows, sold as one bundle at a set price. That's where a flat product feed breaks down, because a set is not one row of data, it's several products stitched together:
Modelling this as linked attributes — rather than re-keying every spec into a flat bundle row — is what keeps a growing set catalog maintainable. Change the duvet's warmth class once, and every set that references it stays correct.
Bedding retailers sometimes hope a data standard will fill the gap. Here is the honest picture of what the common ones do and don't deliver:
| Data layer | What the standard delivers | Where it stops |
|---|---|---|
| Identifiers | GTIN/EAN via GS1, GDSN for master data exchange | No attributes, no content, no set logic |
| Classification | ETIM / eCl@ss give a category skeleton | Not built for warmth class or fill weight |
| Attributes | Partial, supplier-dependent in feeds | Size, fill weight, warmth class rarely clean |
| Sales content | Not the job of any standard | Descriptions, benefit copy, SEO text absent |
| Set / bundle | No standard models duvet-plus-pillow sets | Built entirely by the retailer |
In short: there is no content standard for bedding. The identifiers and classifications give you a scaffold, but the measurements, fill logic, set structure and the actual sales copy are all yours to build. That's the gap Productbay is designed to close.
The job is the same three steps every multi-supplier retailer runs — and Productbay is built to run them across the specific attribute logic of bedding:
The set logic is where Productbay earns its keep in bedding: it models sets as linked attributes, so a duvet, its pillow and the bundle stay consistent without double maintenance. For the wider category context, see product data in home textiles. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — from mid-sized shops to large chains.
Sizes, fill weights, warmth classes and duvet-plus-pillow sets — bedding lives on structured attributes no standard fills for you. See how Productbay normalises fillings, models sets as linked attributes and enriches the rest in a 30-minute walkthrough.
Get started