Product matching across supplier and channel records
Unsure whether two records describe the same product? Match identifiers and attributes, handle variants and send uncertain pairs for review before merging.
- Published
- Last updated
Product matching identifies which supplier and sales-channel records describe the same sellable product by checking identifiers, variant attributes and pack quantities. Link confirmed matches to one canonical record, and hold conflicting pairs for review before combining them. A shared photograph can hide a different size or pack.
Before starting, keep an untouched copy of each feed and its source record IDs. Gather the supplier’s item definitions and the manufacturer’s model or pack specifications for any disputed pair. Work on a proposed mapping that you can inspect before changing destination listings.
Define the matching unit
- Decide exactly what one matched record will identify.
A physical item is one individual object, such as a particular bottle on a shelf. Several physical items can share a product identifier because they are examples of the same trade item. Serial numbers, where used, distinguish individual objects.
A variant is a sellable choice within a product family, such as a navy bottle with a 750 mL capacity. A two-pack of that bottle is another sellable unit. The family groups related variants, but it cannot replace the identity of each choice.
GS1’s variant guidance requires a unique Global Trade Item Number (GTIN) for each product variation, including size and colour. Keep family grouping separate from duplicate matching so one family can contain several distinct sellable records.
Correct: two suppliers’ records for the same navy 750 mL single bottle point to one canonical variant. Incorrect: all bottles with the same family name point to one sellable record, even when their capacities differ.
Use similar titles and images to find candidate pairs. Neither establishes a duplicate. Suppliers can reuse a family photograph, omit a pack count from a title or describe different models with similar words.
Compare reliable identifiers
- Check each identifier within the scope in which it was assigned.
Start with a GTIN when both sources provide one. Preserve it as text so leading zeros survive imports. Check its expected length and check digit before comparing it with another record. A correct check digit confirms the calculation, not whether the number belongs to that product.
Use GS1’s validation guidance to investigate the assignment. Verified by GS1 provides information about the assigning company and product information where available. Company information alone does not establish a particular size or pack.
Compare manufacturer part numbers (MPNs) with the manufacturer’s name and exact specification. A shared model family code can cover multiple variants. Keep meaningful suffixes until the manufacturer’s documentation explains them. Supplier references identify records within that supplier’s system, so identical references from unrelated suppliers are not proof of identity.
Check the packaging level too. The GS1 GTIN Management Standard requires a new GTIN when the number of trade items in a case changes. A case identifier and the identifier for its contained single item must stay distinct.
Consider a hypothetical conflict. Two records carry the same GTIN, but one says a single 750 mL bottle and the other says a two-pack. Pause the match. Compare the pack label and manufacturer’s specification with both feeds, then ask the supplier to correct the conflicting field. Accept the pair only after the evidence confirms the same sellable unit.
A different GTIN also needs explanation before records can be combined. Check whether the pair contains different variants, packaging levels or a source error. Preserve both records while the conflict remains unresolved.
Use attributes to resolve ambiguity
- Compare the attributes that define the sellable unit, using a consistent format.
Put brand and model beside size, colour and unit quantity. Add the category’s distinguishing features, such as voltage for an appliance or connector type for a cable. Record missing values as unknown. An empty colour field cannot confirm that two colours agree.
Normalise formatting in separate comparison fields while keeping the originals. For example, 0.75 L and 750 mL express the same capacity. Trim accidental whitespace and standardise recognised unit labels. Use an approved colour mapping only when the supplier’s definitions support it: navy and blue can describe different variants.
Keep capacity per item separate from pack quantity. Two 750 mL bottles contain 1.5 L in total, but they are a different sellable product from one 1.5 L bottle. Comparing total volume alone would conceal that difference.
Apply the same care to model punctuation. Removing a space can resolve a formatting difference, while deleting a suffix can erase a region or technical distinction. For a difficult pair, use the manufacturer’s exact model and pack data to decide which difference matters.
If the title agrees but the specification conflicts, return the pair to review. If both records lack a distinguishing attribute, collect that attribute before approving the match.
Set review and rejection rules
- Assign an outcome with a reason that another person can inspect.
Use separate outcomes for exact, probable, uncertain and non-match pairs. An exact outcome needs validated identity evidence and agreement on the sellable unit. A similarity score can order the review queue, but it cannot explain away a conflicting pack count.
The following matching demonstration is hypothetical. Every pair concerns a fictional bottle family, and the evidence described is assumed for the example.
| Outcome | Evidence across the two records | Decision |
|---|---|---|
| Exact | Same validated GTIN assignment, navy colour, 750 mL capacity and single-item quantity | Approve one canonical variant |
| Probable | Same brand and manufacturer part number, with matching attributes, but one GTIN is missing | Review the manufacturer’s variant specification before linking |
| Uncertain | Same GTIN, with a single item in one feed and a two-pack in the other | Hold until the source conflict is resolved |
| Non-match | Same family and photograph, but confirmed 750 mL and 1 L capacities | Keep separate variants |
Give the reviewer both source IDs, original values and normalised values. Include the identifier lookup result and supporting manufacturer document. State the conflict or missing evidence explicitly, then record who decided the outcome and why.
Keep a confirmed non-match decision so the same pair does not repeatedly enter the queue unchanged. Reopen it when new source evidence changes the reason for rejection. If a queue keeps returning two-packs as probable singles, make pack quantity a required comparison before the next batch.
Link records without losing their source
- Save a reversible mapping, then verify what each destination will receive.
Map each source-system name and source record ID to the canonical variant ID. Retain the original records and their import versions. Record the matching rule used, supporting evidence and approval. Field-level provenance must show which source supplied each chosen value, especially when suppliers disagree.
Keep a history of mapping changes so you can remove an incorrect link and restore the earlier destination assignment. Choose canonical attribute values through a separate approval decision. Matching two records does not make every field in either feed reliable.
Before applying a batch, inspect its proposed variant structure. Confirm that sizes and colours remain selectable and that single items remain separate from multipacks. Check images against the selected variant, then inspect the destination listing’s title, identifier and quantity.
For the hypothetical bottle family, the two confirmed navy 750 mL single-item records must reach one variant. The 1 L bottle and the two-pack must retain separate sellable records. An unresolved pair must remain unmerged.
Finally, open the affected channel listings or their import preview and follow each mapped source ID through to its destination. If an image changes to the wrong colour or a single item inherits a two-pack quantity, stop the batch and correct the mapping. Use the consolidated product for comparisons only after those checks pass and each selected value remains traceable to its source.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.