Barcode identity preflight
Purchase Order Barcode Import Matcher
Shopify's native purchase order import matches rows by SKU — but supplier files often only carry barcodes. Check every row's match identity before the import silently skips it.
Browser-side scan
Drop a purchase order CSV with barcodes
No CSV selected
Use this purchase order barcode matcher when supplier CSVs identify items by barcode, UPC, EAN, or GTIN instead of your Shopify SKUs, especially while replacing Stocky's barcode-based receiving. The preflight reads your PO import CSV locally, classifies each row's match identity — SKU plus barcode, SKU only, barcode only, or none — validates barcode formats against common GTIN lengths, and finds duplicate barcodes that would make matching ambiguous. Rows that can only match by barcode are flagged so you can map the Shopify SKU before the native import drops them. The export is a review worksheet; nothing is written to Shopify.
Import blockers
Common causes this scan checks
- Supplier purchase order files carry the manufacturer barcode but not your Shopify SKU.
- Stocky supported barcode-based matching that Shopify's native PO import does not.
- Duplicate barcodes across variants make barcode matching ambiguous.
- Hand-typed barcodes lose digits or gain spaces, so they no longer look like a valid GTIN.
Workflow
How to use the cleaned CSV
- Upload the purchase order CSV with SKU and barcode columns.
- Review rows flagged barcode-only, duplicate, or with suspicious barcode formats.
- Fill the Shopify SKU on rows that would otherwise rely on barcode matching.
- Export the worksheet and run the native Shopify PO import with confident row identity.
Auto-fix policy
What the export can safely change
- Detects SKU, barcode, UPC, EAN, GTIN, supplier SKU, quantity, cost, and location columns.
- Classifies each row's match identity and flags rows with no usable identifier.
- Validates barcode digits against GTIN-8, -12, -13, and -14 lengths after stripping spaces and dashes.
- Finds duplicate barcodes and exports a reconciliation worksheet for manual review.
CSV example
CSV example: purchase order barcode matching preflight
The preflight confirms the first row can match by SKU and barcode, while the second row carries only an EAN — so the worksheet says to map the Shopify SKU before the native purchase order import silently skips that line.
SKU,Barcode,Title,Quantity,Cost MUG-1,123456789012,Coffee Mug,10,4.20 ,4006381333931,Travel Mug,6,5.10
SKU,Barcode,Supplier SKU,Title,Quantity,Cost,Location,Match identity,Barcode format,Review note MUG-1,123456789012,,Coffee Mug,10,4.20,,SKU + barcode,GTIN length,Ready for import review ,4006381333931,,Travel Mug,6,5.10,,Barcode only,GTIN length,Map the Shopify SKU; native PO import matches by SKU
FAQ
Shopify CSV questions
Does Shopify's PO import match by barcode?
Shopify's native purchase order import matches rows by SKU. This preflight shows which rows only have a barcode so you can map SKUs before importing.
What barcode formats are checked?
Digits-only values of 8, 12, 13, or 14 characters after removing spaces and dashes. Anything else is flagged as non-numeric or an unusual length for manual confirmation.
Can it look up my Shopify catalog to fill missing SKUs?
No. The MVP audits the file you upload. Pair it with a product export in your spreadsheet when you need to backfill SKUs from barcodes.
Is the purchase order data uploaded anywhere?
No. The CSV is parsed locally in your browser and nothing is stored or transmitted.
Feedback
How is this tool working for you?
Found a bug, a false alarm, or a missing check? Tell me — a human reads every note.