Sold by the meter, not by the piece: how width, repeat and roll logic collide with material and opacity attributes — and why the supplier feed never covers both.
A curtain fabric isn't a product in the way a coffee mug is. You don't sell one — you sell 3.5 meters of it, off a roll that's 280 cm wide, from a design whose pattern repeats every 64 cm. Change any of those numbers and the price, the consumption and the way the customer orders all change with it. Decor fabrics live in the home textiles world, but their data behaves unlike almost anything else in the shop.
Product data for decor fabrics is meterage data: sold per running meter, defined by width and pattern repeat, and layered with attribute-rich properties like material and opacity. That combination — a non-standard sales unit plus a rich attribute set, arriving on a thin supplier feed — is exactly what generic setups get wrong.
The moment you sell by the meter, the one-SKU-one-piece assumption breaks. A decor fabric is a single article whose commercial reality is a bundle of meterage attributes:
None of that fits a plain apparel variant matrix or a hardware spec sheet cleanly. Meterage needs its own structured model — and then the properties need somewhere consistent to live.
Weaving mills and fabric wholesalers optimize for ordering, not for selling online. Their export is built around the article number and the price per meter — everything a buyer needs to place an order, and almost nothing a shopper needs to make a decision. A typical incoming feed looks like this:
| Data layer | What the supplier feed delivers | Where it stops |
|---|---|---|
| Ordering basics | Article number, color number, price per meter | No sales unit logic beyond the price |
| Meterage specs | Roll width, sometimes composition | Pattern repeat and minimum cut often missing |
| Properties | Rarely a bare material line | Opacity, weight, fire behavior, care usually absent |
| Sales content | None | Descriptions, use-case, SEO text all missing |
| Media | Maybe one swatch image | Detail, drape and in-situ shots absent |
So the raw record is enough to reorder the roll and nowhere near enough to publish the product. The distance between those two is the manual work every fabric retailer knows — and it multiplies across hundreds of colorways and collections.
The job is the same three steps as everywhere, but tuned to meterage — and that's what Productbay is built for:
Productbay starts where the mill's feed ends: it takes the thin ordering record and turns it into a structured, sellable meterage product. For the wider category context see home textiles, and for the crossover into outdoor and seasonal ranges, garden & decor. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs.
Meterage pricing, roll width, pattern repeat, thin supplier feeds — decor fabrics break most product-data setups. See how Productbay models meterage as an attribute group and enriches the rest with AI in a 30-minute walkthrough.
Get started