Marketplace Attribute Requirements and Category Mapping

Category and attribute mapping means placing a product from your own catalog onto the correct branch of a marketplace's category tree, then filling that branch's required fields with values the marketplace actually accepts. Every channel has its own tree and its own field list; the same item lands under "Home Textiles" on one marketplace and "Bedroom" on another. Get it wrong and the listing either never goes live or goes live invisible, missing from every filter a buyer uses. This guide covers how to build that mapping across channels and how to keep it current.

Why every channel's tree is different

Marketplaces organize products as a tree: top category, subcategories, and leaf categories at the end. Listings attach only to leaves; you cannot publish to a branch. Depth and naming vary widely between channels. What you call a running shoe may be "Shoes > Women > Sneakers" on one marketplace and "Sport > Running > Women's Running Shoes" on the next.

The leaf you pick decides three things at once:

• Which attributes are required. Each leaf carries its own field list.
• Which filters your product appears in. When a buyer narrows to "material: cotton", any listing with that field empty drops out of the results.
• How fees are calculated. Commission rates are tied to category; check the current rate in the channel's seller agreement. For how the deduction lines add up per order, see the commission and fees guide.

Because of those three, choosing a category is a commercial decision rather than a labeling chore. The wrong leaf makes a product both harder to find and more expensive to sell than you planned.

Required attributes: the real reason listings fail

Attributes are the questions a leaf category asks about your product: brand, color, material, country of origin, warranty, gender, age group, pack size. They come in three kinds:

1. Required fields. Leave one empty and the listing is rejected or stuck in review.
2. Variation-defining fields. Color and size, typically — they decide which options group under one parent listing.
3. Optional fields. Not mandatory, but they are what put you inside filtered searches.

The most common mistake is treating a field as free text. Most attributes demand a value from the marketplace's own closed list. If your system says "anthracite" and the channel's list only offers "Grey" or "Charcoal", sending "anthracite" achieves exactly what sending nothing achieves. For the full set of rejection and delisting causes, see why listings get taken down.

Setting the mapping up, step by step

Map at product-group level, never product by product. A mapping built once then serves every new item that enters the group.

1. Simplify your own category structure. Merge internal categories that do the same work. The fewer branches on your side, the smaller the mapping table.
2. Pick one target leaf per internal category, per channel. Keep the whole table in one place so "where does this product go" has a single answer.
3. Pull the target leaf's field list. Mark separately which fields are required, which come from closed lists, and which define variations.
4. Connect your fields to the channel's fields. Your "fabric" may be their "material". This link is built once.
5. Write a value dictionary. List how your values translate: "anthracite → Grey", "EU 40 → US 7". The dictionary takes the most effort and pays back the most.
6. Test with a small batch. List five to ten products, watch the approval process, note every warning.
7. Go bulk once approvals are clean. The preparation is covered in the bulk listing guide.

This order keeps corrections down to a handful of listings instead of hundreds.

Five mapping mistakes that cost time

• Choosing the widest branch. "I wasn't sure, so I put it in the parent category" is the expensive decision. The product misses its filters and competes against unrelated items. Always take the narrowest leaf.
• Sending your own values raw. A closed-list field given a value you invented behaves like an empty field.
• Leaving brand as free text. Brand is usually selected from a registered list. A spelling difference alone can hold a listing in review, and two spellings split your products across two brand pages.
• Leaving origin, warranty, and pack size until listing day. These are frequently required and slow to obtain. Ask the supplier at purchase time, not at launch time.
• Keeping the mapping in one person's head. If the table lives in someone's notes, nothing new gets listed while they are away. Who owns which step is worth writing down; see team roles in multichannel selling.

Variation attributes are their own problem

When variation-defining fields are mapped wrongly, the listing publishes but publishes badly. The classic outcome: every size of one t-shirt goes live as a separate listing. Buyers cannot switch size, reviews scatter across listings, sales history splits, and search ranking falls with it.

The fix is to group all variants under one parent and give every combination its own SKU and barcode. For building the color and size matrix, see variant management; for separating the roles of SKU and barcode, see the product matching guide.

Cross-border sellers have one extra job: size values must be converted, not copied. A Turkish size cannot be written into a US size field. Bulutegra performs that conversion against the product's own size list, so each market sees the size it understands.

Mapping is not a one-time task

Category trees and field lists change. When a channel adds a new required attribute, older listings that lack it can slip out of view without an error reaching you. The symptom is familiar: a steady seller's orders stop, stock and price are correct, but the listing cannot be found.

Three habits catch it early:

• Re-pull the target leaf's field list before you take on a new product group.
• Review delisted items weekly; a missing attribute is usually the cause.
• Read the per-channel "missing field" report regularly. Product content and quality score is a good place to start on why this affects sales.

Category mapping gets harder as you add channels, not as you add products. A missing field that is a nuisance on one marketplace becomes five separate corrections across five.

How this works with Bulutegra

In Bulutegra the catalog lives in one place, and category and attribute mapping is configured once per channel so new products inherit it. The Integration Panel's quality tab lists missing color, title, and category findings and lets you fix them in one click, with the correction flowing to the connected channels. Content Studio prepares descriptions and multilingual copy, and the ownership flag records, per product and channel, which system is managing that listing. During setup, shadow mode reads for one to two weeks without writing, so you can confirm the mapping is right before granting write access.

To see how your own category and attribute mapping would be built, request a demo.