Ecommerce Catalog Management: SKU Mapping, Attribute Templates and Change Control Across Marketplaces

Most catalog problems on marketplaces are not copywriting problems. They are structural ones: the same product carries three different SKUs across Amazon, Walmart and Shopify, a weight was updated in one place and not the others, or a variation family was rebuilt and orphaned half its reviews. Ecommerce catalog management is the work of keeping that structure correct as the catalog grows and changes.

This article covers the three pieces that hold a multi-channel catalog together: SKU mapping, attribute templates and change control.

What catalog management covers, and what it doesn't

It helps to separate catalog management from the content work around it:

Content gets the attention, but a catalog with broken structure will undermine good content. We covered the content side in building listing content that works on every channel. This piece is about the layer underneath it.

SKU mapping: one product, one identity

Every channel has its own identifiers. Amazon uses ASINs and seller SKUs, Walmart uses item IDs, Shopify uses variant IDs, and your warehouse uses its own item codes. The catalog needs one master SKU for each sellable unit and a mapping table that connects it to every channel's identifier.

A workable mapping table has, at minimum:

• Master SKU, the one your team and your 3PL use
• Channel identifier for each marketplace and storefront
• Barcode (UPC or GTIN) and whether the channel requires it
• Pack quantity, so a 2-pack listing deducts two units from inventory, not one
• Status per channel: live, suppressed, ended

The pack quantity column is where many oversells start. If a bundle listing maps to the base SKU without a multiplier, every bundle sold leaves the inventory count wrong.

Attribute templates: describe it once, export it everywhere

Each marketplace asks for attributes in its own format, but most of the underlying facts are the same: dimensions, weight, material, color, size, age range, compliance details. Keep those facts in one master record per SKU, then map them to each channel's fields.

Attributes worth controlling centrally:

• Physical data: item and package dimensions and weights, measured rather than estimated
• Variation attributes: size and color values written the same way everywhere
• Compliance data: battery, hazmat, age-grading and country of origin
• Category and item type, which decide which other fields a channel requires

Measured physical data matters beyond the listing. The same dimensions and weights feed shipping rates, fulfillment fees on marketplaces that charge by size tier, and your warehouse's carton selection. When the catalog and the warehouse disagree about how big a product is, the order still ships, but someone pays for the difference.

Variation structure is its own discipline. If you sell sizes and colors, the parent-child setup decides how a shopper browses and where reviews accumulate; see structuring Amazon listings for size and color for how that works on Amazon specifically.

Change control: who can edit what, and how you know it happened

Catalogs drift because edits happen in many places. A merchandiser fixes a title in Seller Central, someone updates a weight in Shopify, and a bulk upload overwrites both a month later. Change control stops that drift:

1. Edit the master record first, then push to channels. Direct edits on a channel should be the exception and logged.
2. Keep a change log with the SKU, field, old value, new value, who changed it and why.
3. Restrict structural changes. Changing a variation family, a category or a barcode can break listings or detach reviews; these should need a second person's sign-off.
4. Watch for channel-side overwrites. Marketplaces sometimes change listing data from other contributors or their own systems. A periodic comparison between your master record and the live listing catches it.
5. Version bulk uploads. Keep the file you uploaded so a bad upload can be reversed field by field.

A monthly catalog health routine

• Compare master attributes against live listings on each channel
• Review suppressed or inactive listings and their stated reasons
• Check new SKUs for missing compliance or physical data
• Confirm every bundle and multipack maps to the right component quantities
• Reconcile the master SKU list with the warehouse item list

When to hand it off

Catalog work tends to be done in spare minutes by whoever is closest, which is exactly how drift begins. If your team is selling on three or more channels and nobody owns the master record, that is usually the point where it needs a dedicated owner, in-house or outsourced.

IDCEA's ecommerce management services include listing and catalog management across Amazon, Walmart, eBay and Shopify, alongside order and customer-service operations. When fulfillment also runs through IDCEA, the catalog and the warehouse work from the same item data.