Matching products across marketplaces is the identity problem underneath every multichannel operation: your store’s “Leather Wallet - Brown”, Amazon’s ASIN, and eBay’s item number must be recognized as the same shelf item before any tool can sync a single unit of stock. Matching is invisible when done right, and the root cause of the loudest disasters, wrong counts, cross-linked products, mass duplicates, when done carelessly.
The identifiers, ranked by trustworthiness
SKU, your own identifier. The only key you fully control and can enforce on every channel. One product, one canonical SKU, everywhere, variants get child SKUs. Every reliable matching system joins on this.
GTIN family (UPC/EAN/ISBN). Global identifiers, excellent when your products genuinely have them: they let marketplaces recognize catalog products (Amazon matching your offer to an existing ASIN). Limits: handmade and custom goods lack them, and multi-pack/bundle ambiguity is a classic wrong-match source.
Marketplace-native IDs (ASIN, eBay item ID, Etsy listing ID). Authoritative within their platform, meaningless across platforms, the mapping between them and your SKU is precisely what matching must build.
Titles. Not identifiers. Titles are marketing text that legitimately differs per channel, and every matcher that joins on title similarity eventually cross-links two similar products, syncing the wrong count to the wrong listing until a customer discovers it for you.
The behavior that separates safe tools from disasters
The community’s sync horror stories, thousands of duplicates created during onboarding, variations wiped, unrelated products cross-linked, trace to one design choice: what the tool does when it is not sure. Two policies exist:
Guess-and-proceed: match on fuzzy signals, auto-create anything unmatched, keep moving. Fast to demo, catastrophic at scale, the duplicate cleanup alone can take longer than the onboarding saved.
Match-or-surface: pair confidently on SKU (and GTIN where present), and put every uncertain case in a review queue for a human decision. Slower by one afternoon; safe forever. This is Unifystock’s behavior: existing listings pair to your catalog by SKU, and unmatched or ambiguous items surface instead of becoming silent new products.
Variations: where matching earns its pay
Parent-child products are the matching stress test. The rules that keep them sane:
- Child SKUs are the unit of matching, stock truth lives per variant, so Size M / Blue must map as itself, never as its parent.
- Attribute order is not identity: “Blue, M” and “M, Blue” must resolve to the same child, which is what per-variant SKUs guarantee and attribute-string matching does not.
- Platform variation models differ (Amazon variation families, eBay variations, Etsy’s attribute system); the SKU is the invariant that survives all of them.
A practical matching audit before you connect anything
- Export every channel’s listings with SKUs. Blank SKU rate tells you how much prep you owe.
- Fix identity in the source of truth first: canonical SKUs in your store, child SKUs per variant, naming that self-describes.
- Copy SKUs to marketplace listings where they are missing, tedious once, load-bearing forever.
- Connect and review the surfaced exceptions. The queue after a clean prep is minutes, not days.
Common questions
Can matching work if my SKUs differ per channel?
Mappings can bridge legacy mismatches, but every alias is future confusion. Converge on canonical SKUs during onboarding; the afternoon it costs repays itself permanently.
What happens if two of my listings match the same product?
That is a duplicate, and matching just found it for you, the cleanup playbook: keep the listing with history, zero and end the copy.
Do I need GTINs for matching to work?
No, SKU joins do the work. GTINs add value where marketplaces require them or where catalog-level matching (ASIN) applies, but handmade and custom sellers sync perfectly well without them.
How does matching interact with sync speed?
Matching is the map; sync speed is the traffic on it. A perfect map with slow traffic still oversells; fast traffic on a wrong map oversells the wrong product faster. You need both.
Identity first, then speed
Unifystock pairs your channels by SKU, surfaces every uncertain case, and then keeps the matched map honest in real time, from $49/month with unlimited orders. See pricing.