Why Cannabis, CBD, and Medical Retailers Layer LineNow on Lightspeed Instead of Migrating
Lightspeed Retail (X-Series) is the right POS for specialty retail. It is not a compliance procurement system. This guide is for the Lightspeed operator running a regulated catalog — cannabis, CBD, hemp, medical, or pharma-adjacent: where the compliance gap is, why migrating to a vertical POS is the wrong fix, and what it looks like to layer LineNow on top. Vendor license tracking with expiry, lot-level COA and transfer manifest capture, FEFO picking, and audit-ready receipt history — without replacing the POS you already run.Lightspeed Retail (X-Series) is the POS of choice for a lot of specialty retailers — strong product depth, solid hardware story, fair pricing, and a roadmap that hasn't slowed down. It's especially common in cannabis, CBD, hemp, licensed beverage retail, and a growing share of medical / pharma-adjacent specialty retail (regulated supplements, OTC controlled categories, pet meds, durable medical equipment) where operators picked it for the catalog depth and multi-location reporting. What Lightspeed isn't — and was never trying to be — is a compliance procurement system. It handles checkout and inventory. It does not handle vendor license tracking, COA storage on a specific lot, transfer manifest capture at receipt, or document-blocked receiving for regulated items.
This guide is for the Lightspeed operator running any kind of regulated catalog — cannabis dispensary, CBD storefront, hemp retailer, medical supply shop, or specialty retailer carrying licensed inventory — who is one audit, one recall, or one expired license away from a bad week, and is tired of stitching that work out of spreadsheets, email folders, and Drive screenshots. It walks through what Lightspeed handles, where the gap is, and what it looks like to layer LineNow on top without replacing the POS you already invested in.
If you're a Lightspeed retailer with regulated SKUs of any kind, this is for you.
What Lightspeed handles well
Lightspeed Retail (X-Series) is genuinely good at:
- Item catalog with variants, modifiers, and pricing
- Multi-location inventory with transfers
- Checkout, returns, exchanges
- Customer profiles and loyalty
- Reporting on sales and inventory
- Hardware (registers, scanners, label printers)
- Standard purchase order entry against your catalog
- Vendor records with contact info
This is the operational core. If you're running a cannabis dispensary, CBD storefront, hemp retail location, medical supply shop, or any specialty retailer with licensed inventory, the POS layer is doing real work — and the integrations into Faire, NuORDER, accounting platforms (Xero, QuickBooks Online), and analytics tools mean you're not boxed in.
Where the compliance gap shows up
The gap appears the moment you try to answer a regulator's question or respond to a vendor recall:
1. Vendor licenses live in inboxes, not the POS
Lightspeed has a vendor record. It doesn't have a vendor license record with number, type, jurisdiction, authority, issue date, and expiration date — let alone a way to request the license from the supplier, track when it was last verified, or surface "lapsing in 30 days" alerts.
So vendor licenses end up living in shared Drives, email threads, and the trusted shoebox of the manager who's been there longest. Two months after that manager leaves, the license file is gone and you're explaining to the auditor why you don't have current paperwork on a supplier you bought $40K from last quarter.
2. COAs are tied to vendors, not lots
A Certificate of Analysis is lot-specific by design. Lab X tests batch 2026-04-22-A and issues a COA for that batch. The next batch from the same supplier — 2026-05-01-B — gets a different COA. Tying the COA to the vendor record (which Lightspeed and most POSes do by default) loses that distinction.
When the state inspector asks "show me the COA for the units of strain Y that you sold on May 15," tying COAs to vendors instead of lots means you can't actually answer. You can show the most recent COA the supplier sent you. That's not the right one.
3. Receiving accepts what you tell it to
Standard POS receiving is "click receive, enter quantities, click save." It doesn't know that this particular item is regulated. It doesn't block the receipt for a missing COA. It doesn't capture the lot or the expiration. That data gets entered later — sometimes — into a spreadsheet, when someone has time.
This is the highest-leverage compliance failure in the stack. Once stock is received without lot, expiry, and document attachment, reconstructing those fields after the fact is mostly impossible.
4. Transfer manifests and wholesale-distribution paperwork are PDF, not data
Cannabis transfers carry a state-mandated manifest. Medical wholesalers issue pedigree / chain-of-custody paperwork. Either way, the PDF lives in an email. The structured data — manifest or pedigree number, transfer/ship date, shipper, receiver, carrier, vehicle ID, order number — is never extracted. The PDF gets uploaded to a Drive folder if anyone remembers. The "is this PO on the manifest" check is "open the PDF and look."
5. FEFO picking is impossible without lot expiry
Lightspeed's inventory model is FIFO on standard goods. For regulated items with short shelf life, the right model is FEFO (first-expiry-first-out) — pull the lot closest to expiration first. Without expiration dates captured on every receipt, FEFO has no data to operate on. So you write off near-expiry stock that newer lots sat in front of, week after week.
6. Audit and recall response means stitching three systems
When inspection time comes, the answer to "produce the chain of custody for lot Z" lives in: the Lightspeed receipt record (no lot detail), the email thread with the COA, the supplier's portal for the license PDF, the Drive folder for the transfer manifest, and the spreadsheet where someone hand-stitched it together last time. That's four systems and a manual stitch. It works once. It doesn't work at scale.
What "layered procurement" actually means
The instinct when you hit the gap is to swap the POS — for a cannabis-vertical POS like Treez, Dutchie, or Cova, or a pharma-vertical system for medical retailers. That works, but the cost is real: a POS migration is months of work, a hardware change, a retrain for every register operator, and a permanent shift in your tooling around POS-adjacent integrations (loyalty, analytics, accounting, marketing).
The alternative is to keep Lightspeed and add the compliance procurement layer alongside it. LineNow does exactly that:
- POS stays Lightspeed. Checkout, hardware, catalog management, customer-facing operations don't change.
- Sales sync into LineNow. Inventory depletes in real time as items are sold; LineNow knows current on-hand without manual sync.
- Procurement, supplier licenses, COAs, transfer manifests, lot tracking, expiration capture live in LineNow. This is where the compliance loop closes.
- Accounting handoff continues to your existing system (QuickBooks, Xero, Business Central). LineNow generates the bills with PO + receipt + line-level cost attached.
- State-mandated reporting keeps running alongside both — Metrc / BioTrack for cannabis, pharmacy-board or wholesaler reporting for medical. LineNow doesn't replace it; it gives you cleaner data to feed into it.
The result is the compliance posture of a vertical POS without the migration cost. For most Lightspeed-running regulated retailers — cannabis, medical, or otherwise — this is the lower-risk path.
What the workflow looks like, end to end
-
In LineNow's item form, mark a regulated SKU as regulated. Pick which documents it requires (COA, transfer manifest, vendor license). A Premium badge appears next to the toggle — the Regulated Items add-on is $50/mo, prorated, auto-enabled on first save and auto-canceled when no items remain regulated.
-
Capture supplier licenses on the line. Enter the details from a document you reviewed, or send the supplier a request — replies are extracted from email, parsed into structured fields, and queued for review.
-
When a delivery arrives, open the receive dialog. Add a row per lot, each with its own quantity and expiration date. Attach the COA with structured fields (COA number, test date, lab name, batch number) parsed out automatically. Attach the transfer manifest or wholesaler pedigree with its own fields (manifest number, transfer date, shipper, receiver, carrier, vehicle ID).
-
Receipt is blocked if any required document is missing. Receive into pending state, request the document from the supplier, and the receipt completes the moment the document is verified.
-
Picking runs FEFO. Near-expiry stock is surfaced before it has to be written off; the lot closest to expiration is pulled next.
-
Audit, recall, or internal review: every lot is tied to its COA, manifest, and supplier license at receipt time. Every verify and reject is timestamped with the manager. One query produces the chain of custody.
How this attracts Lightspeed merchants specifically
Lightspeed is dominant in specialty retail because of catalog depth, hardware, and integrations. Operators on Lightspeed picked it for reasons that haven't gone away. The compliance gap is real, but it isn't a reason to migrate — it's a reason to add a layer.
LineNow's pitch to a Lightspeed-running regulated retailer is exactly this: keep your POS, add the compliance procurement layer, drop the spreadsheet stitch. No migration, no retrain on registers, no risk to a working storefront. The Regulated Items add-on is $50/mo on top of LineNow's base — auto-enabled when you mark an item regulated, auto-canceled when you don't have any anymore. You pay for it the months you need it.
A 60-second decision diagnostic for Lightspeed operators
Three questions:
- Can you produce the COA for any specific lot you've sold in the last six months in one click? No = your compliance archive is open.
- When does your top-three suppliers' license expire? If you can't name the dates without looking, your renewal calendar is open.
- Of your on-hand regulated stock, how much expires in the next 30 days? Don't know = your write-off queue is silent.
If any answer is no, the gap is open. The work you're doing in those gaps is the work a procurement layer eliminates.