Quick Rule Summary · Updated November 2026

Lightspeed R-Series appends color and size into each child row’s Description while keeping the parent title in Matrix Description: always derive Shopify’s shared URL handle from Matrix Description (or X-Series handle), prefer Custom SKU over 12-digit System ID, keep leading zeroes on UPC/EAN barcodes, and review negative Qty On Hand rows before import.

01 / INTERACTIVE LIGHTSPEED-TO-SHOPIFY CONVERTERGroup R-Series matrices, map X-Series options & guard leading-zero UPCs.

Click any Lightspeed Retail scenario below—or open the live field drawer to test your own matrix attributes and barcodes—and download a clean UTF-8 Shopify CSV:

Source Rows Inside Lightspeed Retail Export (.csv)
Edit or test your own Lightspeed Matrix / UPC fields (live converter)

02 / THE 4 LIGHTSPEED RETAIL CSV TRAPSWhy specialty bike, apparel & boutique exports break raw Shopify imports.

  1. R-Series Description vs. Matrix Description split: On matrix items, Lightspeed R-Series writes “Trail Shell Jacket Alpine M” in Description and “Trail Shell Jacket” in Matrix Description. If you generate handles from Description, Shopify creates 8 standalone products instead of 1 jacket with 8 variants!
  2. System ID vs. Custom SKU vs. Manufact. SKU: Lightspeed assigns a 12-digit internal System ID to every row even when your barcode labels use Custom SKU. Populate Shopify’s Variant SKU from Custom SKU first, falling back to Manufact. SKU or System ID only when blank.
  3. Dropped leading zeroes on 12-digit UPC barcodes: Opening a Lightspeed export in Excel strips the leading 0 from North American UPC-A codes (turning 045912008812 into 11-digit 45912008812), causing every handheld scanner in Shopify POS to fail on opening day!
  4. Negative Qty On Hand & Supply Price leakage: Retail layaways and special orders often leave QOH = -2 or -4 in Lightspeed (check headers & structure), and mapping Default Cost / supply_price into the wrong price column exposes wholesale cost on your storefront (verify retail prices).

03 / HEADER DICTIONARYLightspeed R-Series & X-Series (Vend) to Shopify column reference.

Mapping Lightspeed Retail R-Series and X-Series (Vend) columns to canonical Shopify product CSV headers
Lightspeed R-Series / X-SeriesShopify CSV headerRequired transformation
Matrix Description (R) / handle (X)URL handle (Handle)Slugify Matrix Description when non-empty (else Description) so all matrix variants share one handle.
Matrix Description / nameTitleEmit on Row 1 of each handle; leave blank on child variant rows 2..N.
Brand / brand_nameVendorCopy manufacturer or brand label cleanly.
Category / product_categoryTypeMap top or leaf retail category.
Matrix Attribute Set + Attribute 1..3Option1..3 name & valueSplit set name (Color/Size → Color, Size); use Title / Default Title for non-matrix items.
Custom SKU (fallback System ID)Variant SKUPrefer human-readable Custom SKU; keep System ID in tags or metafields if needed for audit history.
UPC / EANVariant BarcodeKeep exact 12/13-digit string with leading zeroes intact (never save through unformatted Excel!).
Default Price / retail_price + Default CostVariant Price + Cost per itemFormat plain 2-decimal retail price; map wholesale cost strictly to Cost per item.

04 / SAFE MIGRATION STEPSMigrate Lightspeed Retail to Shopify & Shopify POS in 4 steps.

  1. Export Both Single & Matrix Items Together: In R-Series (Inventory → Item Search → Export) or X-Series (Catalog → Products → Export List), include active matrix attributes, UPC, Default Cost, and per-shop QOH.
  2. Group Matrix Children by Matrix Description: Sort rows so all children of one matrix sit contiguously under a single shared Handle with Title only on the first row.
  3. Preflight Barcodes, Prices & Negative QOH in Row & Record: Open the file inside our browser-local CSV workspace (zero server upload) to verify leading-zero UPCs and retail vs. cost columns before import.
  4. Scan-Test 5 Physical Barcodes in Shopify POS: Import a small 5-product pilot batch and scan physical hangtags with your barcode scanner before running your full catalog cutover.

Common questions.

How do I stop Lightspeed R-Series Matrix items from importing as separate products in Shopify?

Generate Shopify’s URL handle from Lightspeed’s Matrix Description column rather than the item-level Description column (which includes each variant’s color and size), split Matrix Attribute Set (e.g., Color/Size) into Option1 Name and Option2 Name, and leave Title blank on rows 2..N of each matrix.

Should I map Lightspeed System ID or Custom SKU to Shopify Variant SKU?

Map Custom SKU (or Manufact. SKU) whenever populated so your existing warehouse bins and printed hangtags stay recognizable. Fall back to Lightspeed’s 12-digit System ID only on rows where Custom SKU is empty.

How do I keep Excel from deleting the leading zero on Lightspeed UPC barcodes?

Never double-click a Lightspeed CSV to open and re-save it in Excel—Excel treats 045912008812 as an integer and strips the leading zero. Inspect, map, and export your UTF-8 CSV directly inside Row & Record’s browser workspace so every 12- and 13-digit barcode stays plain text.

What should I do with negative Qty On Hand (-2, -5) rows from Lightspeed?

Lightspeed records negative QOH when floor staff sell unreceived special orders or uncounted stock. Decide before cutover whether to zero out negative QOH to 0 for accurate physical shelf counts or preserve negative values while fulfilling open layaways.

05 / RETAIL POS & STORE MIGRATION HUBMoving from another POS or e-commerce platform?

Ready to preflight your Lightspeed-to-Shopify CSV?

Verify matrix handles, leading-zero UPC barcodes, and retail prices locally in your browser.

Open CSV Preflight Workspace ↗

Verified November 2026 against Lightspeed Retail R-Series & X-Series (Vend) item export schemas and Shopify’s Product & POS CSV specification.

Shopify POS & store migration documentationShopify product CSV column referenceRow & Record Chrome Extension ↗