Your supplier file says a product is new, but you can already see it in Shopify under a different barcode. Before importing it again, check all the identifiers attached to the exact variant, then confirm the size and packaging agree. Barcode matching should give you a reviewed destination for each supplier row before it changes stock or creates a listing.
Why I separate a supplier offer from a Shopify variant
In BC Supply Ops for BeautyCorner.gr, I built around a 70,000+ product store and 7 suppliers. Three suppliers were automated; four supplied spreadsheets. Matching had to account for testers, refills, variants, and duplicate supplier rows.
The import engine normalized supplier feeds and matched barcodes against the live store without writing to Shopify. That produced a reviewable new-arrival plan. Each publishing run had a limit and could resume after interruption, skipping duplicate barcodes and already-published items instead of creating them again.
There is another useful decision in that project: supplier routing could change the SKU while leaving the barcode, images, and selling price in place. That is why I recommend keeping a supplier's offer separate from the store variant it supplies. Changing where you buy an item should not make it look like a new product.
The checklist below is how I recommend applying that approach to a new importer. It narrows the broader multi-supplier Shopify operations workflow to one question: when is an identity match trustworthy enough to use?
What should you normalize before comparing barcodes?
Start by asking what the supplier's identifier column contains. A Global Trade Item Number (GTIN) is a standardized product identifier, while a supplier's internal code may mean something only within that supplier's catalog. Shopify's multiple-barcode guidance distinguishes typed identifiers such as UPC and GTIN from Custom codes. Do not assume every value labeled “barcode” is a GS1 identifier.
For declared GTINs, use the same preparation rules on both supplier data and the store snapshot:
- Keep the raw value and source row before changing anything.
- Read the identifier as text and preserve leading zeros.
- Trim surrounding whitespace, but flag embedded punctuation or unexpected characters for review.
- Require the declared GTIN to contain digits and have an accepted length: 8, 12, 13, or 14 digits.
- Validate its check digit, then create a separate comparison key padded with leading zeros to 14 digits.
GS1 explains the uniform 14-digit representation of GTINs. Add those zeros only to the comparison key. Keep the original value so you can trace a mismatch without rewriting Shopify's saved barcodes.
Use the GS1 US check digit calculator to check sample values while defining the import rules. A correct check digit verifies composition, not that the supplier attached the identifier to the right item. Keep the product review even when the arithmetic passes.
If a spreadsheet arrives with a shortened number or scientific notation, request the original identifier as text. Don't guess missing digits, recalculate a failing check digit, or strip characters until a match appears. Keep custom codes in a separate supplier-specific mapping unless their shared meaning has been verified.
How many variants does each identifier actually match?
First check whether your importer can see every barcode your team relies on. Shopify documents the full set in the product CSV's Variant Barcodes column; its first barcode is still used where a channel expects a single value. An older export or connector that reads only that first value needs a coverage check before you trust its “not found” results.
Choose a variant with an additional barcode and trace that code from Shopify into the matching report. If it disappears, resolve the missing data before approving new products. Keep this check read-only: don't reorder or replace the store's barcodes to accommodate an incomplete importer.
Build a lookup from each verified identifier to the distinct Shopify variant IDs it reaches. Several codes leading to one variant are additional ways to identify it, often called aliases. One code leading to different variants is an unresolved conflict.
Here is a hypothetical review for a fragrance catalog. The labels below stand for verified identifiers, not real GTINs or an upload file.
| Identifier being reviewed | Destinations in the complete store snapshot | Decision |
|---|---|---|
| Manufacturer GTIN and Supplier A's verified custom code | Both lead to the same Retail 50 ml variant | One destination; confirm the item details before accepting |
| Manufacturer GTIN | Leads to Retail 50 ml and Tester 50 ml variants | Two destinations; hold and investigate the conflicting assignment |
| Supplier B's custom code | No verified mapping, although Supplier A uses the same text | Hold; identical local codes don't prove identical products |
For the second row, give the reviewer both variant links and the supplier's packaging evidence. Resolve which assignment is correct, record the decision, then rerun matching. Don't delete a listing or choose the first result just to clear the duplicate flag.
Which rows can move forward?
Record the catalog snapshot's scope and completion time. If the export or API read is incomplete, block the matching plan: an absent variant is not evidence that a supplier product is new.
Classify each supplier row before considering stock, price, or publication actions.
| Result | Evidence to inspect | Proposed action |
|---|---|---|
| Missing or invalid GTIN | Raw value, declared type, validation failure | Hold for corrected supplier data or a verified manual mapping |
| Valid key, no destination | Complete snapshot, alternate identifiers, product details | Review as a possible new item; do not create automatically |
| One distinct destination | Variant ID, options, packaging, source row | Accept identity only after details agree |
| Several destination variants | Every matching variant and its options | Hold; resolve the catalog conflict before choosing a target |
| Repeated supplier rows | Supplier references, costs, quantities, packaging | Resolve the offer relationship before applying any update |
| Matching code, conflicting item | Supplier evidence beside the store variant | Hold even if there is only one destination |
Keep the candidate IDs beside the decision so another operator can retrace it.
What if the barcode matches but the packaging differs?
Compare the supplier's description and packaging evidence with the exact sellable variant. For fragrance, that means checking size, concentration, tester status, refill status, and pack quantity wherever they distinguish the offer. Similar names can help you investigate, but aren't enough to approve a match.
Even when a tester row finds only one destination, hold it if that listing describes the retail presentation. Ask the supplier to confirm the item; a unique match can still be wrong.
Apply the same rule when a supplier quotes a case but the storefront sells individual units. Do not silently convert quantities or costs inside barcode matching. Require an explicit, reviewed unit mapping before that offer can supply the variant.
A repeated code across suppliers may represent offers for the same item. Repeated rows within one supplier could also carry conflicting quantities or packaging. Retain supplier identity and row references, then resolve those offers separately rather than summing stock simply because their codes match.
What evidence belongs in the matching report?
For each accepted or held row, retain the supplier, source file, row reference, raw identifier, normalized key, candidate variant IDs, and decision reason. Add the checked item details and the reviewer for any manual resolution. These are proposed importer fields, not required Shopify fields.
For a possible new item, require evidence that the catalog read completed and existing listings were checked using the verified identifiers available. Then send the row through the normal creation review. A barcode miss should not bypass the image readiness and publication queue.
Tie each approval to its source row, mapping rules, and destination variant. If any of those change, rebuild the match decision before using it. Resolve conflicting aliases in the mapping report rather than hiding them behind a previously saved approval.
Before enabling writes, check these cases with saved files:
- Equivalent valid GTIN representations resolve to the same comparison key.
- A bad check digit remains held rather than being repaired automatically.
- A custom supplier code never enters the global GTIN lookup.
- A verified additional barcode reaches the same variant as its primary identifier.
- Multiple destination variants remain held, regardless of their ordering.
- A packaging conflict blocks an otherwise unique match.
- An incomplete catalog snapshot cannot produce approved new-product candidates.
A successful identity check does not establish that a feed's quantities are current or complete. Keep the separate supplier feed acceptance checks before inventory changes.
Where to start
Take one supplier file and a complete store variant snapshot, then produce the decision table with writes disabled. Review unresolved identifiers and packaging conflicts before changing any normalization rules. Keep a copy of each resolution so the next run can explain why it targets that variant. Once matching is settled, the product import approval checklist covers the rest of the review before a supplier file goes live.
If your current importer cannot show the raw identifier, competing matches, and chosen destination, I can help scope that review through my Shopify supplier integration service. Share a sanitized feed and a few unresolved rows through the supplier automation enquiry form, or book a call.