Product Data for Table Linen: Formats and Color Worlds

Dimensions, shapes and color names decide whether a tablecloth is findable. Why format and color attributes are the real work in table linen — and how attribute mapping turns four spellings into one clean filter.

Jakob Feinböck, ProductbayJuly 4, 20267 min read
☝️Key takeaways
  • Table linen data is dominated by format and color attributes: dimensions, shapes, weave, material blend and shade names — the whole sales logic runs on filters.
  • The pain is inconsistent naming: 130x220 vs. 1,30 x 2,20 m, rund vs. rectangular, anthrazit vs. stone — every spelling variant breaks a filter and hides a product.
  • Standards like GDSN, ETIM, eCl@ss carry identifiers and the branded core, but rarely the deep dimension/shape/color detail — and nothing for the no-name longtail.
  • Productbay maps every supplier's raw fields onto one target attribute schema and keeps size/color variants together under one product.

A tablecloth is not a complicated product. It has a size, a shape, a material and a color — and that is almost the entire story. Which is exactly why table linen is deceptively hard to keep clean as data: when four attributes carry the whole sales logic, every inconsistency in how those four are written lands directly on the customer, who filters by size and color and either finds the product or does not.

Product data for table linen is a format-and-color problem: dimensions, shapes, weave, material blend and shade names — and no shared standard for how any of them are written. This is a sub-branch of the broader home textiles challenge, and it shares the DNA of every multi-supplier catalog: the same product, spelled four different ways by four different brands.

Which format and color attributes actually drive table linen?

Table linen is filter-driven merchandise. A shopper almost never searches by article name — they search by the table they need to cover and the palette of the room. That means a small set of attributes has to be structured perfectly:

  • Dimensions: width x length in centimetres, plus diameter for round cloths. The single most-used filter and the single most-inconsistent field.
  • Shape: rectangular, oval, round, square — a short controlled list, but suppliers spell it in two languages and three synonyms.
  • Color: the emotional buying attribute, and the messiest. Hundreds of shade names collapse into a handful of color families a filter can actually use.
  • Material & weave: cotton, linen, polyester blends, Damast, coated/wipeable, plus care attributes like stain-resistant or machine-washable.
  • Range role: tablecloth, runner, napkin, placemat — often the same design sold across all four, which the data should link, not scatter.

Get these five right and the shop navigates itself. Get them wrong and every faceted filter leaks products into the void.

Why does inconsistent naming break the catalog?

The problem is not that suppliers withhold the data — it is that they each encode it differently, and a filter only groups values that are written identically. The same tablecloth from four vendors arrives like this:

AttributeHow suppliers write itWhy it breaks
Dimensions130x220 cm · 130 x 220 · 1,30 x 2,20 m · width + length in two columnsFour strings, zero matches — no size filter groups them
Shapeeckig · rechteckig · rectangular · square (for eckig)One shape splinters into four filter buckets
Coloranthrazit · anthracite · dark grey · stoneOne tone appears as four colors; the color facet is unusable
Material100% Baumwolle · Cotton · BW · Baumwoll-MischgewebeSame fabric, no clean material grouping
Careabwaschbar · wipeable · beschichtet · PVC-freiBuying-relevant feature buried in free text

None of this is exotic. It is the everyday reality of buying table linen from a dozen suppliers, and it is why the catalog quietly degrades: filters that should narrow 400 products to 12 instead return 0, because the twelve are spelled twelve different ways.

Do the data standards cover it — and where do they stop?

There is no dedicated classification that models table linen the way TecDoc models car parts. General standards help at the edges: GTIN/EAN gives you clean identifiers, GDSN and classifications like ETIM or eCl@ss carry structured base attributes for the branded core, and content databases like ICEcat can enrich known articles. But table linen leans heavily on soft, descriptive attributes — exact format, shape, weave, material blend and above all color naming — that these standards either leave to free text or do not carry in depth. And for the no-name and own-brand longtail, which is a large share of a linen assortment, there is usually no classified record at all. So even a standards-literate retailer still faces the core job by hand: normalizing dimensions and mapping color names.

How does Productbay solve the attribute mapping?

The throughline is a three-step job, and for table linen the middle step — mapping — is where the value sits. That is 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.
  • Map & normalize: point each supplier's raw fields at one target attribute schema. AI parses dimensions out of mixed strings into a clean width/length in centimetres, matches shade names against your master color list and controlled color families, normalizes shape and material, writes descriptions and translates via DeepL — always with a review queue before anything publishes.
  • Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp), and feed exports for Amazon, OTTO and Kaufland — with size and color kept together as variants of one product, not scattered SKUs.

The result is a catalog where the size filter actually groups, the color facet actually works, and one tablecloth design carries its whole format-and-color range under a single article. For the wider picture across curtains, bed linen and towels, see the home textiles overview. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs — and the same consolidate, normalize, enrich, publish logic applies whether you sell a hundred tablecloths or ten thousand.

Frequently Asked Questions

Let's look at your product data process

Tablecloths, runners and napkins across dozens of formats and hundreds of shade names — and no two suppliers write them the same way. See how Productbay maps them onto one clean attribute set in a 30-minute walkthrough.

Get started