SKU mapping across marketplaces: keep packs and variants distinct

A marketplace lists “A5 notebook — pack of two”. The ERP holds individual notebooks. An integration reads a sale quantity of three and deducts three notebooks. The import completed, but stock is overstated by three units.

The decision behind SKU mapping is specific: which approved stock item and quantity must this channel line affect? A title match is only one piece of evidence. Pack size, edition, colour, seller account and effective version may change the answer.

Agree what one stock unit means

An internal SKU identifies the item managed in the merchant's system. A channel's seller SKU, listing identifier and variation identifier serve that channel's own model. A GTIN is a standard trade-item identifier; it should not be treated as interchangeable with every internal or channel code.

GS1's full GTIN Management Standard, release 1.1, distinguishes two changes. Section 2.3 covers a change to legally required declared net content on the consumer pack, including a declared count; it requires a new GTIN at that level and existing higher packaging levels. Section 2.8 covers the number of trade items in a case or cases on a predefined pallet, with new identifiers for affected higher packaging levels. A merchant's internal SKU does not replace that identity decision. GS1 standard, sections 2.3 and 2.8.

Before defining a conversion, establish whether the warehouse holds individual units or prepacked sale units. A virtual two-pack assembled from two individual notebooks can deduct two each. A sealed two-pack held as its own stock SKU should normally deduct one pack from that SKU under the merchant's approved model. Converting that pack to individual units and also consuming the pack would count the same stock twice.

This article's worked example uses individual notebooks as the stock unit and virtual packs assembled from them.

Make the mapping explicit

The retailer sells two notebook colours. The approved records distinguish them even where channel codes are similar.

The third row shows why code text is insufficient. Without approved evidence of the blue product, leave the mapping unresolved.

A usable mapping record includes:

• the channel, seller account, listing and variant identifiers;
• the approved internal item and stock unit;
• the conversion factor and whether the item is a virtual pack or stocked pack;
• source evidence such as approved product data, packaging details or a validated supplier record;
• valid-from and, where applicable, valid-to values;
• mapping version, approver and change reason.

Keep barcode data in the record when it helps validate identity. A missing or reused barcode is a review condition, not a reason to invent one.

Follow three pack sales through stock and a return

Assume the red-notebook ledger starts with 80 available individual units and no other holds or commitments.

Three two-packs are sold and dispatched. The fulfilled quantity is three × two = six notebooks, so the remaining on-hand and available stock is 74. A separate sale and dispatch of four single notebooks leaves 70.

The customer then returns one of the original two-packs. Receiving counts two notebooks, but one is damaged.

The return quantity conversion is two, but the availability increase after inspection is only one. Correct SKU mapping identifies what arrived. It does not authorise the disposition.

For a partial or incomplete pack return, record what physically arrived and retain the original commercial claim. If the customer returns one notebook from a two-pack, do not receive two merely because the original listing represented two. Any refund decision is a separate approved action. The stock-availability guide explains how restricted quantities affect new promises.

A pack change must not rewrite an old order

Suppose a future offer contains three notebooks rather than two. For a packaged consumer product, assess the declared-count rule; for a case configuration, assess the case-quantity rule. A virtual offer also needs the channel's listing rules. Record the identity decision before changing the mapping.

Whatever change is approved, retain the resolved stock identity and conversion used for each existing order line. An old return should not look up today's factor and credit three units for a two-unit pack.

Effective dates help, but a timestamp lookup alone can be inadequate when events arrive late or source clocks differ. Persist the order's resolved mapping version and the supporting source line. If historical evidence is missing, route the return for review rather than claiming an exact conversion from an uncertain date.

Correcting a mapping error also needs explicit treatment. Identify the affected orders and stock movements, assess the physical position and record approved corrections. Editing the master table should not silently reprocess completed orders.

Separate plausible suggestions from approved mappings

Fuzzy matching can propose that “A5 Red Notebook 2pk” resembles an existing item. AI may help extract attributes from supplier descriptions or group likely aliases. Use suggestions to reduce the reviewer's search effort.

The approval still needs evidence of edition, variant and quantity. A high similarity score does not establish that a pack contains the same product. Keep the suggested match, the original evidence, any disagreement and the review result.

Where evidence is stable, deterministic checks can catch many consequential errors:

Explain the failed check: “two active factors, 2 and 3, for this listing” gives catalogue operations a decision to resolve.

Test two channels before widening the catalogue

Start with a small set that includes single units, virtual multipacks, closely named variants and a legitimate product change. Choose examples because they expose different mapping risks, not because they are the cleanest rows.

An approved mapping table may be enough when the catalogue and channel relationships are stable. A PIM or integration mapping service can help when several systems need controlled updates, evidence and version history. The service still needs an accountable catalogue owner.

Use sales, cancellations and returns in acceptance testing:

1. Three virtual two-pack sales resolve to six units of the correct notebook.
2. The same code in another account resolves only through that account's approved mapping.
3. A duplicate event creates no additional stock movement.
4. A later three-pack change leaves the original two-pack order history intact.
5. A return with one damaged notebook changes physical and available stock differently.
6. A missing or ambiguous mapping remains visible without a guessed posting.

Record both unresolved mappings and corrections discovered after approval. A high percentage of auto-matched titles is not a useful success measure if pack errors reach fulfilment.

Preserve identity through the whole transaction

A reliable mapping remains understandable when an order is imported, fulfilled, changed and returned. It connects the channel's wording to an approved item and quantity without losing the original evidence.

1. Define the stock unit for the selected products.
2. Review the channel/account keys and pack factors.
3. Store the mapping version used by each order line.
4. Rehearse a pack change and a partial return before widening the rollout.