Product Data for Rugs: Dimensions, Material and Care

A rug is one of the most attribute-sensitive products a home textiles retailer sells. A customer buying online can't feel the pile or lay the rug down in their living room — so they decide on the data alone: the exact dimensions, the shape, what it's made of, how high the pile is, and whether it survives a vacuum cleaner or underfloor heating. Get one of those attributes wrong and you get a return.

Product data for rugs is a precise set of measurement, material and care attributes — plus an image set that almost always arrives separately. This is a focused sub-topic of the broader home textiles product data challenge: where towels and bedding share much of the same logic, rugs push the size-variant and material precision to an extreme.

Which attributes make or break a rug listing?

A sellable rug record is built from a tight cluster of attributes, and each one is a filter or a decision factor for the buyer:

• Dimensions and shape: length x width in cm, plus shape — rectangular, round (by diameter), oval, or runner (by length). This is the number-one filter in any rug shop.
• Pile material: wool, polypropylene, viscose, cotton, jute — the material blend drives both the look and the price bracket, and it has to be exact.
• Pile height: in millimetres — low-pile vs. high-pile / shaggy changes the whole use case (flat-weave under a dining table vs. shaggy in a bedroom).
• Weight and backing: total weight or grams per square metre, plus the backing material — relevant for quality perception and slip resistance.
• Production method: hand-knotted, hand-tufted or machine-woven — a core value and price signal.
• Care instructions: washable, vacuum-safe, suitable for underfloor heating, colourfastness — the attributes that prevent returns.

None of this is optional. A rug listed without pile height or care information simply converts worse and returns more. Doing it by hand across dozens of suppliers is exactly the consolidate-normalize-enrich-publish problem, in a domain that punishes imprecision.

Why do the images always have to be handled separately?

Here's the part that trips up almost every rug retailer: the attribute feed and the images live in two completely different places. The feed is a table — a row per article or per size. The images are large binary files, delivered over FTP, a download link or a ZIP, named by article number, colour or size in a way that rarely maps cleanly to your rows.

And a rug isn't a one-image product. To sell it you need a full top view, a close-up of the pile, and ideally a room scene showing scale. Multiply that by every size and colour variant of a design, and you have a matching problem: which image belongs to the 160x230 in beige versus the 200x290 in grey?

• Filenames rarely match your SKU scheme, so matching is manual by default.
• One design has many variants, each potentially needing its own room scene or colour shot.
• Images update on a different cadence than the data — new photography lands without a data change.

Without proper digital asset management, this becomes an afternoon of renaming files and dragging them into the right variant — per collection, per season.

Do standards cover rug data — and where do they stop?

Rug data does touch a few standards, but it's important to be honest about how far they reach:

In short: standards give you clean identifiers and a rough classification for branded goods, but the depth that actually sells a rug — precise attributes, care, and matched images — is on you. And for the longtail of no-name and own-brand rugs, there's frequently no feed at all.

How does Productbay structure rug data?

The answer is structure plus a proper DAM, run over every supplier at once — which is exactly what Productbay is built for:

• Consolidate & normalize: import every source once — supplier CSV, Excel, feed URL, FTP, API — match by SKU or EAN/GTIN, and normalize the size, shape, material and care attributes into one consistent structure, so variant matrices from different suppliers line up.
• Enrich: AI fills missing attributes from whitelisted sources, writes descriptions, assigns categories and translates via DeepL — always with a review queue before anything publishes.
• DAM plus structure: the built-in digital asset management links each image to the right size and colour variant, so the top view, pile detail and room scene sit on the correct record instead of in a folder you rename by hand.

The result is one clean catalog where a rug's size matrix, its material and care attributes, and its full image set all live on the same record — ready to publish to Shopify, Shopware and marketplaces. Productbay is built for specialist retailers running multi-supplier catalogs, of any size.

Frequently Asked Questions