How do serialized or lot-tracked inventory items (common in Lightspeed retail categories like jewelry or bikes) migrate to Shopify's inventory model?
Lightspeed exports serial numbers and Shopify has no field to receive them. X-Series exports a CSV of serialized products with serial numbers, SKUs, outlets and sale dates (Lightspeed, September 2026). Shopify treats a serial as an attribute of a sold order, not of a unit in stock, which reverses the workflow a jeweler or bike shop runs.
This page is about serial numbers, one number per physical unit. Lot and batch tracking, where one number covers many units, is the sibling page on this thread.
What Lightspeed actually gives you, both series
Both Lightspeed Retail products treat a serial number as an inventory-side object, and that is the crux of the problem.
R-Series: tick the Serialized box on an item, then serials are entered on the Serial #s tab or "as part of receiving the purchase order." At the till, "use the Scan or type a serial number dropdown to scan, type, or select an existing serial number." The Inventory > Serial Numbers page "lists all products and their serial numbers" and can be printed or exported to CSV. The system tracks each unit's history through receipt, sale, repair and refund, linked to the customer where there is one (per Lightspeed R-Series support, September 2026).
X-Series: cashiers "will be prompted to enter the serial number to confirm it's available to sell," serials can be added later for unfulfilled sales, and "you can export a CSV list of all serialized products. This file includes serial numbers, product names, SKUs, associated outlets, and sale dates" (per Lightspeed X-Series support, September 2026).
Read the R-Series wording again: "confirm it's available to sell." The serial is stock. It is received, it is held, it is sold. That is how a bike shop knows which frame is on the floor and which one went out last Tuesday.
Why the Shopify equivalent is not an equivalent
Shopify has no serial field on an inventory item, and the app market has largely solved a different problem. Serializer, the most-reviewed dedicated serial app we checked, rates 4.9 across 6 reviews and prices at $9 per month plus $0.25 per tracked item after 50, or $19 per month unlimited. It lets you "add serial numbers, warranty or any custom item details" to items in completed orders or the POS cart, and search orders by serial (per Shopify App Store, September 2026).
That is a serial at the point of sale, attached to an order. It is genuinely useful for warranty lookup, which is what most jewelers and bike shops need the serial for afterwards. It is not an inventory unit, so it cannot tell a salesperson which of the four identical frames in the back is the one with the number the customer is asking about, and it cannot be received against a purchase order.
The direction of the data reverses. In Lightspeed, the serial arrives with the stock and leaves with the sale. In Shopify plus a serial app, the serial is created at the sale. Everything before the sale is outside the system.
The migration decision, in the order it has to be made
- Separate the two uses. Warranty and after-sales lookup is one use. Knowing which physical unit is where is another. Most retailers assume they need both and on inspection need the first.
- If you only need lookup: export the Lightspeed serial CSV with its sale dates and customer links, archive it, and adopt an order-level serial app going forward. You will have a discontinuity at the cutover date, and you should document it rather than hide it, because the first warranty claim that lands on the wrong side of that line is a customer-service conversation either way.
- If you need the stock-side behaviour: Shopify is not the system of record for that inventory. It goes to an ERP or a WMS, and Shopify holds a quantity. This is the same conclusion the lot-tracking page reaches by a different route.
- A third route, for narrow catalogs: make each serialized unit its own variant or its own product. Viable for genuinely one-of-a-kind goods, which is a real pattern in fine jewelry and used bikes. Not viable for a hundred identical frames, because you inherit a hundred SKUs and a catalog nobody can merchandise.
Where to put the exported history
The Lightspeed serial CSV is the only complete record you will ever have of which unit went to which customer before the cutover. Treat it accordingly: archived with a named owner, indexed by serial, and searchable by whoever answers warranty calls. Product or order metafields can surface the last-known serial where staff work, but the archive is the record.
When NOT to rebuild serial tracking on Shopify
- When the manufacturer already holds it. Many bike and appliance brands register serials themselves. Duplicating that is work you do not owe anyone.
- When the serial is only ever read from a physical object. If staff read the number off the item in their hand, you need a lookup table, not an inventory dimension.
- When the catalog is large and the units are identical. Variant-per-unit collapses at scale, and it collapses in merchandising rather than in inventory, where it is harder to unwind.
- During the cutover week. Serials are the last thing to move, because the discontinuity date should be one clean date you can tell staff.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Serial tracking is the capability most often assumed to migrate and least often needed in the form it migrated from. We split the requirement into stock identity and warranty lookup on every one of these projects, because the second is cheap on Shopify and the first is an ERP conversation.
- What we tell clients to check first: Ask the person who actually uses serials, not the person who configured them. In our experience of this pattern the answer is almost always "a customer calls with a number and I need to know when we sold it and to whom," which the exported CSV plus an order-level app satisfies completely.
- Where we disagree: The obvious advice is variant-per-unit, because it works in a demo. It works for genuinely unique goods and it fails silently for everything else, by turning a merchandisable catalog into a ledger. We would rather lose serial-level stock visibility in Shopify than lose the collection page.
- What this page adds: that both Lightspeed Retail series export serials to CSV with sale dates, that the Shopify app market attaches serials at the order rather than at the unit, and that the practical migration is an archive plus a lookup, not a field mapping.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.