Identifiers, attributes, and keeping one catalog true across every channel.

Product data fails late, because a wrong attribute breaks nothing until a retailer rejects an item setup or a marketplace suppresses a listing. Identifiers, syndication, and what each channel demands.

16 questions answered

• What is a PIM?→

  A product information management system is the single place product data is authored and maintained — names, descriptions, attributes, images, dimensions, identifiers, and channel-specific variants. Each sales channel and trading partner reads from it, so a correction is made once and propagates, instead of being repeated in five places.

• Do I need a PIM or is a spreadsheet enough?→

  A spreadsheet holds up while one person maintains one catalog for one or two channels. It stops working when several people edit it, when channels need different attribute sets, or when a retailer requires its own format. The signal is not SKU count — it is how many places the same fact is stored.

• What is a GTIN and how do I get one?→

  A Global Trade Item Number is the standard identifier for a sellable product, administered by GS1. You obtain a company prefix from your national GS1 organisation and assign numbers from it to your own products. Retailers and marketplaces require legitimate GS1-issued numbers, and resold or borrowed codes get rejected.

• What is the difference between a GTIN and a UPC?→

  GTIN is the umbrella identifier; UPC is one form of it. A UPC-A is the twelve-digit barcode used in North America, and as a GTIN it is expressed as a thirteen or fourteen-digit number with leading zeros. EAN-13 is the European equivalent. They are the same identifier space in different lengths.

• Do cases need their own GTIN?→

  Yes. A case is a separate tradable unit from the item inside it, so it gets its own GTIN — usually a GTIN-14 built from the item’s number with an indicator digit for the packaging level. A retailer ordering by the case scans the case identifier, not the unit one.

• Do I need a separate GTIN for every variant?→

  Yes. Every variant a customer can choose between — each size, color, flavour, or pack count — is a distinct tradable item and needs its own GTIN. Reusing one number across variants makes them indistinguishable at the till and in the retailer’s system.

• What is a SKU and how should I structure SKU codes?→

  A SKU is your internal identifier for a distinct sellable item, at the level you count and sell it. Structure the code so it is readable and stable: a short product root plus variant segments for color and size, in a fixed order and fixed width. Keep out anything that can change, such as price, season, or supplier.

• What is SKU rationalization?→

  SKU rationalization is deliberately cutting the assortment to the items that earn their place. It weighs each SKU on contribution margin, velocity, the working capital it consumes, and whether it holds a retail listing, then discontinues the tail. The aim is fewer items each supported properly.

• What is product data syndication?→

  Syndication is publishing your product data out to every channel and partner in the format each one requires — a marketplace feed, a retailer’s item-setup template, a distributor’s catalog, your own storefront. The source record is one; the outputs are many and each has its own required fields and vocabulary.

• What is item setup?→

  Item setup is the process of getting your products into a retailer’s system before they can be ordered. The retailer supplies a template — often hundreds of fields covering identifiers, dimensions, weights, packaging hierarchy, compliance data, and imagery — and every required field must validate before the item is live.

• What product attributes do retailers require?→

  Beyond name and description: GTINs at every packaging level, case pack and inner pack, unit and case dimensions and weights, pallet configuration, country of origin, HS or tariff codes, shelf life where relevant, hazardous-materials flags, and imagery to a stated specification. Categories add their own — ingredients, allergens, or fabric composition.

• What is a data contract?→

  A data contract is an explicit agreement about the shape of data passing between systems or teams: which fields exist, what types and value ranges they take, which are mandatory, and who is accountable when one changes. It turns an implicit assumption into something that can be validated and versioned.

• Why do my product listings differ across channels?→

  Because each channel was populated separately and has drifted since. A description edited on the webstore, a title rewritten for a marketplace’s character limit, and an image updated in one place create three versions of one product. Without a source record they diverge further with every edit.

• What is digital asset management?→

  Digital asset management is the system holding product imagery, video, and documents with the metadata that says what each asset is, which product it belongs to, and where it may be used. It handles versioning and renditions, so each channel gets the format and dimensions it requires from one master file.

• What is a single source of truth for product data?→

  One authoritative record per fact, with every other system reading from it rather than holding its own copy. For product data that means one place where a description, a dimension, or a GTIN is authored, and channels rendering from it. Where two systems can both edit the same field, there is no source of truth.

• How do I manage product data for retailers that each want a different format?→

  Hold one internal record with every fact at full fidelity, then treat each retailer’s template as an output mapping from it. Adding a retailer becomes a new mapping rather than a new copy of the catalog, and a corrected dimension updates every partner on the next publish.

Browse every commerce operations answer, or look a term up in the glossary.