Shopify POS Legacy Switch: What to Check Before Replacing Retail POS

A legacy POS rarely fails all at once.

It usually becomes expensive in smaller ways first.

Inventory takes too long to reconcile. Store staff use workarounds that never reach ecommerce. Customer history lives in one system and order behavior lives in another. Reporting depends on exports. Returns between online and retail feel fragile. The old POS still processes sales, but it is no longer helping the business run as one retail operation.

That is the moment to evaluate Shopify POS seriously.

The question is not only, "Can Shopify POS replace our current register?" The better question is, "Can Shopify become the operating base for retail, ecommerce, inventory, customer data, staff workflows, payments, and reporting without creating a worse store experience during the switch?"

Shopify's retail migration guide is useful as a setup reference, and Shopify's POS launch checklist recommends starting preparation at least four weeks before opening day for small to mid-size rollouts. That is the platform checklist. The operating checklist starts earlier.

Start with the symptoms, not the software comparison

Retailers often start with a POS comparison table.

That can help, but it is not the first decision. The first decision is whether the current POS is blocking the business model the brand is trying to run.

Look for symptoms like:

• Online and store inventory disagree often enough that staff stop trusting either system.
• Retail customer history does not support ecommerce marketing, service, or loyalty work.
• Store returns, exchanges, discounts, gift cards, or special orders need too many manual exceptions.
• Multi-location reporting takes too long to produce or cannot answer basic store-level questions.
• Staff permissions are too broad, too narrow, or impossible to manage consistently.
• Hardware, payments, receipts, barcode scanning, or cash tracking create daily store friction.
• Ecommerce and retail teams have different definitions of customer, order, product, and available inventory.

If those symptoms are minor, a cleanup project may be enough. If they are structural, switching POS platforms becomes a business-operating decision, not an IT preference.

Decide what Shopify POS must own

Shopify POS is strongest when retail is meant to connect tightly with Shopify ecommerce.

That does not mean Shopify POS should automatically own every retail rule on day one. Before replacing a legacy POS, define what the new system must own directly and what should stay in an app, ERP, accounting platform, warehouse system, or custom workflow.

The ownership map should cover:

• Product and variant records.
• Inventory by location.
• Customer profiles and consent.
• In-store orders, exchanges, refunds, and returns.
• Discounts, gift cards, store credit, and promotions.
• Staff roles, approvals, attribution, and cash tracking.
• Hardware, payment devices, barcode scanners, receipt printers, and network requirements.
• Reporting for stores, registers, staff, inventory, finance, and ecommerce.

Shopify's POS staff-management documentation says POS access can be controlled by staff member, location, and task. Shopify's permissions reference shows how many retail actions can become role decisions. That matters because a POS migration changes who can do what in the store.

If permissions are copied casually from the old system, the new setup can preserve old operating problems in a cleaner interface.

Check the data before promising the launch date

A POS switch is not ready because the product import worked.

The launch date depends on whether the critical retail data can support real store work. Products, variants, barcodes, prices, tax settings, inventory counts, customer records, order history, gift cards, discounts, and staff records each need a decision.

The most important questions are practical:

• Which historical orders need to be searchable at the register?
• Which returns or exchanges depend on legacy order records?
• Which customer fields should move into Shopify, and which should stay archived?
• Which products are active, discontinued, store-only, online-only, bundled, or special-order?
• Which inventory counts should be trusted before go-live?
• Which data should not be migrated because it would create bad store behavior?

This is where a POS switch differs from a simple setup. A setup asks whether Shopify POS can sell. A migration asks whether the business can keep helping real customers after old records stop being the daily source of truth.

LHG's related Shopify POS migration checklist goes deeper on products, customers, and orders. The readiness point is simple: do not choose the cutover date until the store team knows which records they can trust.

Test the first week, not only the first transaction

The first card payment is not the migration test.

A retail team needs to test the first week of real operations before go-live. That includes normal transactions, but also the messy cases that make store teams lose trust.

Test scenarios such as:

• Sell a simple item, a variant-heavy item, and a discounted item.
• Sell the last unit at one location and check what ecommerce sees.
• Return or exchange an order from the legacy POS window.
• Attach a migrated customer to an in-store purchase.
• Create a new customer and confirm consent handling.
• Scan barcodes under normal store pressure.
• Open, close, and reconcile the register.
• Process manager approvals for refunds, discounts, and exceptions.
• Confirm receipts, payment devices, printers, cash drawers, and barcode scanners behave at each location.
• Review reporting after the test day, not only during the sale.

Shopify's hardware documentation and launch checklist are helpful because POS readiness depends on devices, card readers, peripherals, staff login, subscription tier, and location setup. But the business still has to prove the store rhythm.

A test that only confirms the happy path can miss the problems that appear when the store is busy.

Protect inventory and location trust

Inventory trust is often the reason retailers switch POS systems.

It is also one of the easiest things to damage during the switch.

Before replacing the legacy POS, decide how Shopify locations, inventory states, transfers, count processes, pickup rules, and store availability should work together. A retailer with one store can sometimes correct inventory manually. A retailer with multiple locations, ship-from-store, pickup, transfers, or warehouse stock needs a stricter model.

The team should define:

• Which locations exist in Shopify and which locations should be sellable.
• Which products are stocked, unstocked, incoming, committed, damaged, or unavailable.
• Who can adjust inventory and who can approve corrections.
• How transfers between stores or warehouses are requested, sent, received, and reconciled.
• How ecommerce should treat retail stock during the first launch week.

The goal is not to make every process heavy. The goal is to keep staff from losing trust in Shopify POS before the operating model has had a chance to work.

For adjacent checks, use the LHG guides on POS inventory sync, POS inventory states, and POS inventory transfers.

Know when not to switch yet

Sometimes the right answer is to wait.

If the legacy POS still owns critical custom behavior, unsupported hardware, region-specific payment requirements, store operations that Shopify POS cannot yet support cleanly, or reporting that finance depends on daily, the team should not force a cutover just to modernize the stack.

Waiting does not mean doing nothing. It means turning the gap into a migration plan:

• Document the must-keep retail workflows.
• Identify which gaps Shopify POS can handle natively.
• Decide which gaps need apps, custom work, process changes, or a staged rollout.
• Clean product, customer, inventory, and staff data before migration.
• Run a pilot location if the store network is complex.
• Set a fallback and support plan for the first week.

The wrong POS switch creates two systems of truth: the official one and the one store staff invent to keep serving customers. The right switch removes that split.

Treat the POS decision as unified-commerce work

Replacing a legacy POS is not only a register project.

It touches ecommerce, retail operations, merchandising, inventory, finance, customer support, lifecycle marketing, analytics, and store leadership. If those teams are not aligned before the switch, Shopify POS can go live while the business still runs in pieces.

The decision becomes stronger when the team can answer five questions:

• What is broken in the current POS that a cleanup cannot fix?
• Which retail workflows must Shopify POS own on day one?
• Which data has to be trusted before the first store opens on the new system?
• Which first-week scenarios prove the setup works?
• Which team owns exceptions after launch?

That is the difference between replacing software and moving toward unified commerce.

If your retail POS is holding back inventory trust, staff workflows, customer data, or online-to-store operations, talk to Lake House Group about Shopify POS migration before the cutover date is set.