POS SKU and Barcode Migration

Source record IDs, merchant SKUs, and printed barcodes are different identifiers. Create a crosswalk so the new system can be traced back to the original records.

Read barcode values as text and check leading zeros, punctuation, duplicate values, and multiple barcode types. Test scanning separately from the file import.

• Source record ID → migration crosswalk
• Merchant SKU → agreed stock identifier
• UPC or EAN → text value with leading zeros
• Destination ID → returned record reference

The illustrative code 001234567890 must remain 001234567890. A spreadsheet that turns it into a number can silently change what a scanner expects to find.

• Keep source internal ID, merchant SKU and barcode in separate fields in the mapping file.
• Treat barcode and SKU columns as text, including values that resemble dates or scientific notation.
• List duplicated, blank or reused codes for a retailer decision before loading the file.
• Scan a leading-zero barcode and a size/color variation on the intended device; verify the selected item and label.

Use the migration checklist to assign the decision owner and acceptance evidence. Confirm inclusion in the written scope after a secure sample review.

Current vendor instructions inform this guide; account access and the selected workflow still need confirmation.

• Square item import and export instructions
• Shopify product CSV documentation