Supplier SKUs in Shopify: match supplier codes to your SKUs
Your supplier's invoice says PW-00412. Your Shopify product says LEAD-RED-M. They're the same dog lead, and you know that, but your spreadsheet doesn't, and neither does any import or app you point at the invoice. Multiply that by a few hundred lines and a dozen suppliers, and matching codes becomes the slowest part of every delivery, every price update and every reorder.
This guide sets up the matching once, so it gets lighter with every delivery instead of starting from scratch: where to keep the supplier's code in Shopify, how to clean codes so they actually match, and a lookup that tells you which lines matched and which need a look. There's a free code map template further down that does the lookup for you.
The short version
- Keep one code map: supplier, the supplier's code, your SKU, and how many units their code means.
- Store the supplier's code in Shopify where it helps: a variant metafield for catalogue numbers, an extra barcode for barcodes the supplier prints on the item.
- Keep codes as text, and clean them the same way on both sides (spaces, capitals, dashes) before you compare.
- Match on supplier + code, never the code alone.
- Every delivery: look up each line, fix only the ones that didn't match, and add them to the map so they match next time.
Why supplier codes don't match your SKUs
Almost every mismatch is one of these. Knowing which one you have tells you the fix:
| What you see | Example | Fix |
|---|---|---|
| The supplier has its own numbering | Invoice PW-00412, Shopify LEAD-RED-M | Map it once in the code map |
| Leading zeros lost | 00412 became 412 | Keep codes as text (see below) |
| Long numbers mangled | 5012345678901 shows as 5.01235E+12 | Import the column as text |
| Spaces, capitals, dashes | pw 00412 vs PW-00412 | Clean both sides the same way |
| Supplier prefix or suffix | ACME-1001 vs your 1001 | One rule per supplier |
| One code is a case, not a unit | CANDLE-06 is a case of 6 candles | Pack size in the map |
| Sizes written differently | Supplier 38, your variant M | A size map per supplier |
| The same code from two suppliers | Both send code 1001 | Match on supplier + code |
| The supplier changed its code | Last season PW-412, now PW-00412 | Keep both rows, note the date |
Where to keep the supplier's code in Shopify
Shopify has no "supplier SKU" field on the product. There are four places a code can live, and each is good for something different:
| Where | Good for | Watch out for |
|---|---|---|
| Your own SKU | Shops with one supplier per product, who are happy to use the supplier's numbering as their own | Breaks when you add a second supplier or the supplier renumbers |
| Variant metafield | The supplier's catalogue number. Shown on the variant page, editable in bulk, and apps can read it | Not in the product CSV: fill it in the bulk editor |
| Extra barcode | A barcode the supplier prints on the item or case, so you can scan it when stock arrives | Keep your own barcode first, because channels read the first one |
| Supplier SKU on a purchase order | A reminder on each line of Shopify's own POs | Lives on the PO, not the product; can't be bulk edited or imported |
A variant metafield for the supplier's code
For most shops this is the right home for a catalogue number. Set it up once:
- In the admin, go to Settings › Custom data › Variants and add a definition.
- Name it Supplier SKU, and choose Single line text as the type. Text matters: a number type would strip leading zeros. Shopify's own Stocky transition guide suggests one definition per supplier detail, with a namespace and key like
supplier.supplier_sku, and that's a sensible name to copy. - If one variant comes from two regular suppliers, add a second definition (say
supplier.supplier_sku_2) rather than squeezing both codes into one field. With more than two, keep them in your code map instead.
To fill it for many variants at once, use the bulk editor: in Products, tick the products and click Bulk edit, then add the metafield as a column. Each row is a variant. One thing that catches people out: Shopify's help states that variant metafields aren't supported for product CSV import/export. Product metafields are, but a supplier code belongs on the variant, because each size or colour has its own. So it's the bulk editor or an import app, not the product CSV.
Extra barcodes for the supplier's printed barcode
This one is new. Since September 2026 a Shopify variant can hold up to 20 barcodes instead of one, and Shopify POS finds the variant by any of them. If a supplier's box carries an EAN that isn't yours, add it as a second barcode and it scans straight to the right product.
- Keep your own barcode first. The first barcode is the one Shopify says channels, labels and apps that expect a single barcode keep using. Add supplier barcodes after it.
- Pick the type. Barcodes can be marked UPC, EAN, ISBN, GTIN or ASIN, and Shopify checks the format so a mistyped digit is caught. Codes that follow no standard can be added as Custom. There's also NS-PID, for the manufacturer's own model or part number, which is used on customs declarations for EU shipments (see shipping to the EU below).
- They do import. Unlike variant metafields, barcodes are in the product CSV: the Barcodes column takes several values separated by a semicolon, with an optional type before a colon:
Check the column header in a fresh export first: Shopify's CSV guide says a file can't have both the old Barcode column and the new Barcodes column.
EAN:5012345678900;EAN:5098765432109
Use barcodes for codes that are physically printed on stock. A catalogue number that only appears on invoices belongs in the metafield: it's not something anyone will ever scan. The one exception is the manufacturer's own model or part number if you ship to EU customers from outside the EU, below.
Shipping to EU customers from outside the EU
Since 1 November 2026, EU customs requires product identifiers for every item in a parcel sent to a customer in the EU from outside the EU and worth €150 or less. Shopify's help says a parcel without them can be held or rejected at customs, and you might pay return-to-origin fees. There are three identifiers per item, and Shopify takes all three from your product data:
| Identifier | What it is | Where Shopify takes it from | What you need to do |
|---|---|---|---|
| Merchant (M-PID) | Your own identifier for the item | The variant's ID | Nothing |
| Standardized (S-PID) | A GTIN, EAN, UPC or ISBN | A barcode saved with that type. A Custom barcode is accepted too if it's a valid GTIN of 8, 12, 13 or 14 digits | Add the barcode printed on the packaging, with its type. If the product has none, declare that instead (below) |
| Manufacturer's (NS-PID) | The manufacturer's model number, part number or style code | A barcode with the NS-PID type. Without one, Shopify uses the standardized barcode, then any other barcode, then the SKU, then the variant ID | Optional: a variant with a GTIN or a SKU already meets it |
What that means in practice:
- The standardized barcode is the one that stops labels. When you buy a label in the Shopify admin for an EU parcel worth €150 or less, the label can't be bought while any item has no standardized barcode and no declaration. You can fix it on the label page with Edit customs declaration, and what you enter there for a product is saved back to that product.
- The supplier's printed barcode is often the answer. If you resell a branded product, the EAN or UPC on its packaging is the standardized identifier. Add it as an extra barcode with type EAN or UPC, after your own barcode, exactly as described above.
- Declare "none" only when it's true. For a product with no GTIN, EAN, UPC or ISBN, such as a handmade item or an own-brand product you never registered, open the product (or each variant), and in the Shipping section click More details and turn on No EU standardized identifier. With it turned on, no standardized identifier is sent for that item even if one is saved, so don't use it as a shortcut.
- Check in-house barcodes. Because a Custom barcode that's a valid 8, 12, 13 or 14-digit GTIN is accepted as the standardized identifier, a numeric in-house code of that length could be sent to customs as one. If your shelf labels use made-up numbers, check what yours look like.
- A supplier's code isn't always the manufacturer's code. When you buy straight from the maker, its catalogue number is the manufacturer's code, and you can add it as an NS-PID barcode. A wholesaler's or distributor's own catalogue number isn't: the manufacturer's model or part number is usually printed on the packaging or the spec sheet. Keep the wholesaler's code in your metafield for matching invoices either way.
- Some goods are exempt, decided by HS code. Shopify lists unprocessed agricultural and perishable goods in HS chapters 01 to 15, certain handmade and artisanal goods, and antiques, collectibles, works of art, stamps and coins. You can't mark a product exempt yourself: Shopify applies it from the variant's HS code, so check your HS codes are right.
- Doing it in bulk. Shopify says the bulk editor takes both the barcodes and the declaration. Barcodes also import through the product CSV's Barcodes column; to get the NS-PID type written correctly, set it on one variant in the admin, export that product, and copy the format from the file.
- Labels bought outside Shopify. Shopify adds the identifiers to labels bought in the admin, including Managed Markets. If you buy labels in a shipping app, with your own carrier account or through a 3PL, ask them how they get the identifiers. Shopify's help only says to make sure they reach your carrier through the method you use today.
The Supplier SKU on Shopify's purchase orders
Each line of a purchase order in the admin (Products › Purchase orders) shows a Product SKU and a Supplier SKU. It's useful on the PO you send, but it isn't a master record: the code is stored on the purchase order, Shopify's help doesn't document the field, and merchants have reported that there's no way to see or edit these codes in bulk. Treat it as a copy of what's in your metafield or code map, not the place you keep it.
Keep codes as text, and clean them the same way
Most "no match" results aren't really different codes. They're the same code damaged on the way in.
Stop the spreadsheet changing codes. Excel and Google Sheets treat anything that looks like a number as a number. That drops leading zeros (00412 becomes 412), shows long codes in scientific notation, and in Excel keeps only 15 significant digits, so the 16th digit of a long code silently becomes a 0. When you open a supplier's CSV:
- In Excel, use Data › From Text/CSV instead of double-clicking the file, choose Transform Data, and set the code column to Text before loading.
- In Google Sheets, select the code column and choose Format › Number › Plain text before pasting codes in.
- Never type codes into a column formatted as a number. If you must type one, start it with an apostrophe:
'00412.
Clean both sides the same way. Suppliers are inconsistent about spaces, capitals and dashes, sometimes within one invoice. Before comparing, put every code through the same small clean-up: trim spaces, make it upper case, and remove inner spaces and dashes. In a spreadsheet:
=UPPER(SUBSTITUTE(SUBSTITUTE(TRIM(B2)," ",""),"-",""))
That turns pw 00412, PW-00412 and Pw-00412 into the same PW00412. Two rules make it safe:
- Clean both columns, the invoice's and your map's, or nothing will match.
- Don't strip leading zeros "to be safe".
00412and412may be two different products for that supplier.
Prefixes and suffixes are a rule per supplier, not a guess. If one supplier always writes ACME- in front of a number you store without it, strip exactly that text for that supplier only:
=IF(A2="Acme", SUBSTITUTE(B2,"ACME-",""), B2)
A pattern you can write down like this needs no AI and no fuzzy matching. Fuzzy matching ("this looks about right") is exactly how a lead in size M ends up received as size L.
Match on supplier and code, never the code alone
Two suppliers can both have a product 1001. If your lookup uses the code alone, one of them will match the other's item, and nothing will look wrong. Build the match key from both: the supplier name, a separator, and the cleaned code.
Match key: =A2&"|"&UPPER(SUBSTITUTE(SUBSTITUTE(TRIM(B2)," ",""),"-","")) Your SKU: =XLOOKUP(F2, 'Code map'!G:G, 'Code map'!C:C, "NOT FOUND")
Here A is the supplier, B the supplier's code, F the match key on the invoice sheet, and the code map holds the same key in column G. XLOOKUP works in Excel 2021 and Microsoft 365 and in Google Sheets. In older Excel, use =IFERROR(INDEX('Code map'!C:C, MATCH(F2,'Code map'!G:G,0)),"NOT FOUND"), which is what the free template uses so it works everywhere.
Cases, packs and sizes
Matching the code is half the job. The other half is knowing what the code means in your units.
- Pack size. Put a pack size against every supplier code in the map: 1 if the supplier sells singles, 6 for a case of 6. Then units received = quantity on the invoice × pack size, and cost per unit = invoice price ÷ pack size. An invoice line of 2 cases of
CANDLE-06at £27.00 a case is 12 candles at £4.50 each, and £4.50 is the number that belongs in Shopify's cost per item. Our guide to checking supplier invoices shows why this is where most short deliveries hide. - Sizes. When a supplier sends sizes in its own system (
38where you sayM,Mediumwhere you sayM), keep a small size map for that supplier: their size, your size. Build it the first time their file comes in. After that, each order only needs a look at sizes the map hasn't seen. Shopify treats every spelling of a size as a different option value, so in a product CSV import an unmappedMediumnext to yourMbecomes a second variant instead of an error, and stock and sales end up split across the two.
The routine for each delivery
- Paste the invoice lines into the check sheet: supplier, code, description, quantity, price.
- Every line either finds your SKU or says NOT FOUND. On a supplier you've done before, most lines match.
- For each NOT FOUND line, find the product once by its description, and add a row to the code map: supplier, their code, your SKU, pack size. Next delivery, it matches.
- Matched lines now have your SKU, units and cost per unit. Use them to receive the stock in Shopify and to spot any line whose cost moved, which our guide on updating prices when supplier costs rise picks up from.
The first invoice from a new supplier is slow. The fifth is mostly checking the two or three new lines. That's the point of keeping a map rather than matching from memory each time.
When a supplier changes its codes, add a row for the new code and keep the old one with a note ("replaced by PW-00412 from Nov 2026"). Old invoices and credit notes will still quote the old code, and you'll still want them to match.
Free supplier code map template
Download the free supplier code map (Excel). It has three sheets: a Code map (supplier, their code, your SKU, product, pack size), a Size map, and a Check a delivery sheet. Paste an invoice into the check sheet and it cleans each code, looks up your SKU by supplier and code, works out units and cost per unit from the pack size, and counts matched and NOT FOUND lines. Code columns are already set to text, so leading zeros survive. A worked example is filled in. It opens in Excel, Google Sheets and Numbers.
Questions merchants ask
Does Shopify have a supplier SKU field?
Not on the product. Shopify's own purchase orders show a Supplier SKU next to the product SKU on each line, but it lives on the purchase order, so you can't filter, import or bulk edit by it. For a code that stays with the product, use a variant metafield, or an extra barcode if the supplier prints it on the item.
Can I import variant metafields with the product CSV?
No. Shopify's help says variant metafields aren't supported for product CSV import or export. Use the bulk editor with the metafield added as a column, or an import app.
Can a variant have more than one barcode?
Yes, up to 20 since September 2026, and POS finds the variant by any of them. Keep your own barcode first.
Should the supplier's code go in the barcode field?
Not as the first barcode. A barcode the supplier prints on the stock makes a good extra barcode. A catalogue number nobody will scan belongs in a metafield or your code map. The exception is the manufacturer's own model or part number when you ship to EU customers from outside the EU: add it as an extra barcode with the NS-PID type.
Do I need a barcode on every product to ship to EU customers?
If you ship from outside the EU and buy labels in Shopify, each item in a parcel worth €150 or less needs a standardized barcode (GTIN, EAN, UPC or ISBN) saved with its type, or the No EU standardized identifier declaration turned on, or the label can't be bought. Exempt goods are worked out from the HS code. The manufacturer's code is optional, because Shopify falls back to the barcode or SKU.
I'm moving off Stocky. Where do supplier codes go?
Shopify's own transition guide points to variant metafields for supplier-specific SKUs and case packs, which is the setup above, and notes that staff convert case packs into units by hand. Suppliers can't be exported from Stocky, so copy their details while you still have access: our guide on exporting your Stocky data has a free template for it.
Quick checklist
- One code map: supplier, supplier code, your SKU, pack size.
- Supplier catalogue numbers in a variant metafield (Single line text).
- Supplier-printed barcodes added as extra barcodes, after your own, with their type.
- Shipping to the EU from outside it: every variant has a standardized barcode with its type, or the No EU standardized identifier declaration, and a correct HS code.
- Supplier files opened with the code column as text.
- Codes cleaned the same way on both sides before comparing.
- Lookups on supplier + code, never code alone.
- A size map for any supplier that uses its own sizes.
- Every NOT FOUND line added to the map, so it matches next time.