Should we run Lightspeed and Shopify POS side by side while building out the new ecommerce store, or migrate everything in one cutover?
Short answer
A Lightspeed and Shopify parallel run is safe for catalog and inventory, never for registers, because two registers on one stock pool produce two counts. Lightspeed's Shopify integration names Lightspeed Retail (X-Series) "the system of record", so updates made in Shopify "may be overwritten" (Lightspeed X-Series support, October 2026). Registers move in one cutover per store.
- System of record in a parallel run
- Lightspeed Retail (X-Series)Per Lightspeed's setup guide: updates made in Shopify may be overwritten, and sales made in Shopify are recorded in Lightspeed by default (October 2026).Source: Lightspeed X-Series support (Setting up the Shopify integration)
- What the integration does not carry
- Loyalty, gift cards, store creditLightspeed also lists price books and promotions as incompatible with Shopify, and says Retail POS sales history can't be transferred to Shopify (October 2026).Source: Lightspeed X-Series support (About the Shopify integration)
- Lightspeed plans with the integration
- X-Series Core, Plus, Pro, Standard, Advanced, EnterprisePer Lightspeed's setup guide. On R-Series, Lightspeed's help center points to Mortar by Accumula, a third-party connector from $39 a month per location (October 2026).Sources: Lightspeed X-Series support (Setting up the Shopify integration); Lightspeed R-Series support (The Accumula Shopify app is now Mortar by Accumula); Accumula Labs (Mortar by Accumula on the Shopify App Store)
- Shopify locations for synced outlets
- 10 on Basic to Advanced, 200 on PlusLightspeed maps inventory outlet by outlet and asks for the same number of Shopify locations, so syncing more than 10 stores meets the plan limit (October 2026).Sources: Lightspeed X-Series support (Managing multi-location inventory with the Shopify integration); Shopify Help Center (Setting up and managing locations)
Deploi’s call
Parallel the data, never the register. The useful parallel period keeps Lightspeed as the system of record and Shopify as a channel, which is precisely the arrangement Lightspeed's own integration enforces. Once a second register starts writing to the same stock, you are not de-risking. You are manufacturing a reconciliation project.
CustomizeRun Lightspeed and Shopify side by side while
- The online store must launch before any register moves, with Lightspeed Retail as the system of record.
- Your Lightspeed plan includes the integration, which Lightspeed lists on Core, Plus, Pro, Standard, Advanced and Enterprise (Lightspeed, October 2026).
- Loyalty, gift cards and store credit can wait for cutover, because the integration does not carry them (Lightspeed, October 2026).
- The parallel has a written end date, the rule our record on keeping store and online stock in step sets for any bridge to a legacy system.
BuyMove every register in one cutover when
- You run a single location.
- Two or three stores share one stockroom.
- The Lightspeed contract ends on a hard date.
Basis: Build or Buy POS-Ecom Coherence on Shopify?, our Build vs. Buy decision record, scored WAIT.
What does Lightspeed's own Shopify integration allow during a parallel run?
Lightspeed's Shopify integration allows a parallel run in one shape only: Lightspeed Retail, the point of sale (POS) system, stays the system of record and Shopify becomes its online sales channel. Lightspeed's setup guide says "Retail POS should be treated as the system of record" and "Updates made in Shopify may be overwritten or cause syncing issues" (Lightspeed, October 2026). The integration shares "product, inventory, customer, and sales information between both systems." By default, "your sales in Shopify are automatically recorded in Retail POS." So Shopify runs downstream of Lightspeed, not as a peer. That suits building the online store while the registers stay put, which is the overlap the full Lightspeed cutover plan is sequenced around.
Check two things before you count on it. Lightspeed lists the integration on its Core and Plus plans and on its Pro, Standard, Advanced and Enterprise plans (Lightspeed), and its app on the Shopify App Store is built for X-Series (Shopify App Store, October 2026). On R-Series, Lightspeed's help center points merchants to a third-party connector, Mortar by Accumula (Lightspeed), whose listing names both series (Shopify App Store, October 2026).
What does the integration leave out of a parallel run?
Lightspeed's integration leaves out the balances customers carry and anything that exists only in Shopify. Lightspeed lists loyalty, gift cards and store credit among the Lightspeed Retail point of sale (POS) features that "aren't compatible with Shopify" (Lightspeed, October 2026). So gift card balances and loyalty balances move at cutover, not during the parallel. Three more limits shape the plan:
- Once integrated, "you won’t be able to sell products exclusively on Shopify." A Shopify product missing from Lightspeed "will be automatically created in Retail POS" (Lightspeed, October 2026).
- Shared products need matching stock-keeping units (SKUs) and handles, and images attached to Shopify products don't sync back to Lightspeed (Lightspeed).
- Inventory maps outlet by outlet, and Lightspeed asks for "the same corresponding number of locations in Shopify" (Lightspeed, October 2026). Shopify allows 10 locations on Basic, Grow and Advanced and 200 on Plus (Shopify Help Center, October 2026), which means syncing more than 10 stores meets the plan limit before any register moves.
Which ways of running both systems keep the stock count true?
The catalog-and-inventory parallel and the split-store parallel keep the stock count true, because each keeps one system of record per shelf. A same-store dual register does not.
| Shape | What runs where | Verdict |
|---|---|---|
| Catalog and inventory parallel | Lightspeed is the system of record; Shopify sells online through the integration; every register stays on Lightspeed | Do this. It is what the integration is built for |
| Split-store parallel | Store A on Shopify's point of sale, stores B to E on Lightspeed, stock not pooled between them | Tolerable and time-boxed. Promise customers no stock transfers between the two estates |
| Same-store dual register | Both systems selling the same stock in the same room | Never. No reconciliation design survives it |
The dual register fails because an inventory decrement is a claim on a physical object, not a message. Two systems that both own one shelf will each believe they sold the last unit. Neither number is wrong inside its own system, so nobody can adjudicate. The only fix is a full physical count, the cost the parallel run was meant to avoid. In a split-store parallel, test what Lightspeed records when the pilot store sells, because Lightspeed's integration records sales made in Shopify in Lightspeed by default (Lightspeed, October 2026).
How long can a Lightspeed and Shopify parallel period last?
A catalog-and-inventory parallel can last as long as the ecommerce build needs, because Lightspeed stays the one system of record and its integration enforces that. A split-store parallel is bounded by month-end, not by weeks. Every close during a split estate is a close where someone reconciles two sets of books by hand. One close is a manageable inconvenience. Three is a hiring decision.
Our working rule: a split-store parallel crosses at most one month-end close, and its end date goes into the plan before it starts. Our record on point of sale (POS) and ecommerce coherence asks the same of any bridge to a legacy POS: write "the bridge's retirement date into the project brief before scoping" (checked October 2026).
When is a single Lightspeed cutover the right call?
A single cutover is the right call when there is no second estate worth running, because a split estate costs a manual reconciliation at every month-end close:
- A single location. There is no split-store option and no reason to invent one.
- Two or three locations sharing one stockroom. The reconciliation cost of a split estate exceeds the risk of one weekend.
- A Lightspeed contract that ends on a hard date. Design to the date rather than pretending it is soft.
Either way, our record on Shopify point of sale (POS) against Lightspeed Retail schedules the switch for a slow week (checked October 2026).
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- The standard migration advice is "run both for a while to be safe." That advice is imported from systems where the data is a record of something that already happened. Inventory is not a record. It is a reservation against a physical object, and reservations do not tolerate two owners.
- What we refuse to scope
- A same-store dual-register period. It is chosen because it feels reversible, and it is the least reversible option on the list, because after a week nobody can say which system holds the true count and the only route back is a physical inventory. We will scope a catalog-and-inventory parallel or a time-boxed split-store parallel, and we will say no to the third.
- What this page adds
- that Lightspeed publishes its own Shopify integration for X-Series, which makes Retail POS the system of record, blocks Shopify-only products and leaves loyalty, gift cards and store credit behind, and therefore defines what a legitimate parallel period looks like before you design one.
Decision records behind this answer
When this answer changes
- Lightspeed changes its Shopify integration's system-of-record rule, or lets products sell only on Shopify.
- Lightspeed adds loyalty, gift cards or store credit to what its Shopify integration supports.
- Lightspeed moves the integration to other plans, or publishes an integration of its own for R-Series.
- Shopify changes the 10-location limit on Basic, Grow and Advanced, or the 200 on Plus.
- Deploi's POS and ecommerce coherence record changes its verdict on bridges to a legacy POS.
Related questions
This follows from How do I migrate from Lightspeed Retail (POS) to Shopify without disrupting in-store sales during the transition?
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Lightspeed X-Series support, Setting up the Shopify integration
- Lightspeed X-Series support, About the Shopify integration
- Lightspeed X-Series support, Managing multi-location inventory with the Shopify integration
- Lightspeed, Lightspeed Retail POS X-Series on the Shopify App Store
- Lightspeed R-Series support, The Accumula Shopify app is now Mortar by Accumula
- Accumula Labs, Mortar by Accumula on the Shopify App Store
- Shopify Help Center, Setting up and managing locations
- Deploi Build vs. Buy, Build or Buy POS-Ecom Coherence on Shopify?
- Deploi Build vs. Buy, Shopify POS vs. Lightspeed Retail: Which POS Fits a Shopify Store?