Product matching in marketplace integration means linking every item in your own system to its exact counterpart on each marketplace. The most reliable method uses the SKU as your internal identity and the barcode (EAN, UPC, GTIN) as the shared key. When matching is right, stock and prices reach the right listing; when it is wrong, the rest of the integration, however good, updates the wrong product. This guide walks through matching step by step.
Why matching is the foundation
An integration carries three things: orders, stock, and prices. All three depend on one question: which product? The line item in an Amazon order maps to which item in your ERP? The unit that just left your warehouse should reduce which listing on eBay or Trendyol? The answer is the matching table.
The symptoms of bad matching are familiar: one size's stock written to another, oversells, returns opened on the wrong item, and a profitability report that no longer means anything. The one to three days spent on matching save hours of corrections every month afterwards. For where matching sits in the overall setup, see the four-step setup guide.
SKU: your internal identity
The SKU is a code your business assigns. You set the rules; what matters is consistency. For a sound SKU scheme:
- Every variant has its own SKU. "Tee-Black-M" and "Tee-Black-L" are different codes.
- A code is assigned once and never changed, even if the product title changes.
- No spaces, accented characters, or special symbols. Some marketplace APIs read them differently.
- Keep the length reasonable; codes over 30 characters may be truncated in marketplace panels.
- Never reuse a SKU for a different product. Duplicate SKUs are the most common matching error.
If your catalog lives in Shopify, WooCommerce, or a Turkish platform such as ikas, Ticimax, T-Soft, or İdeasoft, the SKU is defined there and the integration reads it. If you work from an XML feed, make sure the SKU field is filled for every product.
Barcode: the shared language with marketplaces
A barcode (EAN, GTIN, UPC) is issued by the manufacturer or a barcode authority and is the same worldwide. Marketplaces mostly identify products by barcode; listings with the same barcode are grouped on the same product page. That makes the barcode the bridge between your SKU and the marketplace's product record.
Things to watch with barcodes:
- Each variant needs its own barcode. Putting one barcode on all sizes breaks matching.
- Do not put the SKU in the barcode field. The two fields do different jobs.
- Length and check digit must be valid; marketplaces reject malformed barcodes.
- Barcode requirements and exemption rules differ by marketplace and category; check the current seller agreement.
Step-by-step matching
Matching is the second step of setup and usually takes one to three days. The order is:
- Connect your catalog source. The integration reads products, SKUs, and barcodes from here.
- Pull the current listing set from every marketplace. The SKU and barcode fields on channel listings become visible.
- Run automatic matching. The system compares barcodes first, then SKUs; products where both agree are confirmed matches.
- Review single-key matches. Where only the barcode or only the SKU agrees, find out why the other does not; usually a field is missing on the channel side.
- Link unmatched items by hand. Listings created on the channel without SKU or barcode are linked from a list, and the channel field is corrected afterwards.
- Check variants. The parent may be matched while one size is not; filter the list at variant level.
- Clean up duplicates. Resolve cases where the same barcode appears on two listings; one is closed or merged.
- Set channel ownership. For each product × channel, set the flag that says "is this channel managed by the integration or by an external system?" Channels staying on the old tool during migration are left untouched.
- Spot-check. Pick ten random products and confirm stock and price on every channel equal the source values.
- Enter shadow mode. Once matching is complete, the system reads only, for one to two weeks; when the numbers reconcile, write access is enabled channel by channel. See the shadow mode article.
In Bulutegra these steps run in sequence inside the Integration Panel; auto-matched, single-key, and unmatched products appear in separate lists, and manual linking happens on the same screen.
Variants and size conversion
In apparel and footwear the real unit is the variant. Matching must be done on the color × size combination, not the parent title. Otherwise "Black M" sells out while "Black L" still appears available, or the reverse; the result is oversells and cancellations. The stock side of this is covered in stock synchronization and oversells.
Cross-border channels add a layer: size conversion. For US orders, sizes can be shifted one step up according to the product's own size list; this conversion runs on top of the matching table without altering it. Details are in international size and measurement conversion.
Common mistakes and a checklist
The problems that show up most often, and what to do about them:
- Same barcode on several variants: get a separate barcode for each.
- SKU typed into the barcode field: separate the fields and fix the channel record.
- Spaces or accented characters in the SKU: simplify the code and keep the old one as a note.
- Listing created on the channel outside the integration: it shows as "unmatched"; link it manually.
- Product deleted and recreated: the new listing has a new identity; the old match is orphaned, so update it.
- Wrong ownership flag: if the integration also writes to a channel managed by another tool, values will contradict within hours.
Rule: the matching table is a living document. Update it whenever you launch a product, close a listing, or change a barcode. Check the "unmatched products" count in the panel weekly.
Matching quality is tied to content quality too; for missing color, title, or category findings see product content and quality score.
How this works with Bulutegra
Bulutegra matches products on SKU and barcode together: it reads your catalog source directly, pulls channel listings, and shows auto-matched, single-key, and unmatched products in separate lists. The product × channel ownership flag keeps channels that remain on an external system untouched during migration. When matching is done, shadow mode begins, and once the numbers reconcile, write access is handed over channel by channel. To see it with your own catalog, request a demo.
Frequently asked questions
What is the difference between a SKU and a barcode?
A SKU is the stock code your own business assigns; it only has meaning inside your systems. A barcode (EAN, UPC, or GTIN) is issued by the manufacturer or a barcode authority and is the same everywhere. In integration, the SKU is your internal identity and the barcode is the shared language with the marketplace.
Can I list a product on a marketplace without a barcode?
Some marketplaces and categories require a GTIN, others grant exemptions. Check the marketplace's current seller agreement. Products without barcodes are matched on SKU, but getting a barcode for every product makes matching far easier in the long run.
How are products with variants matched?
Every color and size combination needs its own SKU and its own barcode. Matching is done at variant level, not parent level; otherwise the stock of one size gets written to another.
