Shopify POS looks simple from the outside. Tap, pay, done. But for any retailer running multiple retail locations, a POS rollout touches almost every part of the business, from how stock moves between stores to how finance reconciles payouts at month end.
That's the part that tends to get underestimated. Shopify POS is a genuinely powerful piece of software, but can be deceptively complex. Getting it to behave the way a multi-location retailer needs it to behave takes proper planning, not just switching it on.
We saw this first hand when we worked alongside Frog Stack on OKA's 15-location Shopify POS rollout, connecting the shop floor to NetSuite and unifying trade pricing, gift cards, inventory and reporting across a unified eCommerce setup. That project is a good reference point for the decisions below, because almost every one of them came up somewhere in the build.
Here are the 10 decisions worth working through before you start configuring a Shopify POS rollout.
1. How orders, payments, refunds and exchanges will actually work
Shopify natively handles complex in-store scenarios: endless aisle, cross-channel returns, exchanges, split payments. The question isn't whether Shopify POS can do it. It's whether the data behind each of those transactions, the sold-from-location, the sales rep, the payment method, reaches your reporting and finance teams in a form they can actually reconcile. Get this wrong and finance ends up chasing payouts that don't match what happened on the shop floor.
2. Where the single source of truth for stock sits
Multi-location retailers need to decide early whether an ERP is the master system, with Shopify POS acting as a downstream node, or whether Shopify POS itself is the stock master that everything else is audited against.
This decision shapes how transfers, replenishment, stock takes and adjustments are configured, and it needs to be agreed before go-live, not discovered after it.
3. How customer records, trade status and loyalty carry across channels
A loyal customer walking into store should not be a stranger to your system. Trade pricing if you're running B2B, order history, loyalty status and purchase activity all need to follow the customer, regardless of where they last shopped.
On the OKA rollout, this meant migrating historical data from legacy systems into Shopify so store teams had a genuinely richer view of every customer from day one, not a blank slate.
4. How gift cards and promotions behave across every channel
Gift cards issued online need to be redeemable in store and vice versa, with one clear view of balances and redemptions. Promotions need guardrails too, particularly around trade pricing or exclusions, so store staff aren't left applying discounts manually or guessing what applies to who.
If you're trading across multiple currencies or territories, gift cards also come with compliance considerations that are easy to overlook. Some US states require balances under a certain amount to be redeemable for cash rather than only spent in further purchases. In certain countries, putting an expiry date on a gift card is against the law entirely. These rules need to be factored into how gift cards are configured per market, not applied as a single global setting.
5. What your ERP, finance and fulfilment integrations need to deliver
This is usually where the real complexity lives. Shopify POS is a lightweight, digital-first system, not a monolithic enterprise EPOS, so translating in-store scenarios into the data structures your ERP expects rarely happens automatically.
Integration needs to be treated as a core workstream of the project, not a technical afterthought bolted on at the end.
6. Your hardware and payment setup, store by store
A pop-up might online need an iPad or two, whereas a flagship store is more likely to need a full counter setup with a scanner, printer and cash drawer.
Getting hardware right also means thinking about staff efficiency day to day. Shopify has made this considerably easier recently: as long as one device in a location is already signed in, staff can approve a new device sign-in from it in seconds, rather than typing credentials into every till individually. Worth factoring into how you plan device rollout across multiple stores.
7. How staff permissions and workflows are structured
Who can see certain activity, override what and process what varies enormously across a retail estate, especially once you're supporting trade customers, multiple locations and different levels of seniority.
It's also worth building your workflows around some of the newer POS Pro capabilities. Cart sharing on Shopify now lets staff build a cart on one device and hand it off to be completed at another till entirely, useful for busy floors with multiple registers or a mix of mobile and fixed devices. And POS Pro's multi-location pickup means a member of staff at one store can create a pickup order for a customer to collect at a different location, all from a single device.
A small but genuinely useful detail worth building into your workflow: a saved cart converts into a draft order, and that draft order can be given a proper name rather than left as a generic reference.
From a training perspective, that's a simple habit that makes a real difference when multiple staff are juggling multiple in-progress carts across a shop floor.
8. How training, testing and rollout sequencing will be handled
Even the best-configured setup falls flat if store teams aren't confident using it. Training needs to be built into the project properly, covering core tasks like checkout and returns as well as more advanced flows like trade pricing or multi-location pickup.
Multi-location retailers also need to decide between a phased rollout, testing and refining store by store, or a full launch across every location at once. For bigger retail rollouts, a phased approach usually reduces risk considerably.
9. What support looks like after go-live
Go-live is not the finish line. Once Shopify POS is live, most retailers uncover new opportunities to refine workflows, reporting and customer journeys as real usage data starts coming in.
Planning for that ongoing relationship, rather than treating launch as the end of the project, tends to separate the retailers who get lasting value from Shopify POS from those who just get a new till.
10. What "done" actually looks like for your business
Finally, it's worth being honest about what success means before you start. Is it fewer disconnected systems? Faster checkout? A single customer view across channels? Better reporting for trading decisions?
Shopify POS can support all of these, but only if the project is scoped against the outcome you actually need, rather than treated as a like-for-like till replacement.
Why this matters more for multi-location retailers
Every one of these decisions gets harder as the number of locations grows. Data mapping, staff permissions, hardware variation and integration complexity all compound. That's exactly the scale of challenge we worked through on OKA's Shopify POS rollout across 15 UK locations, unifying retail and eCommerce onto one platform connected to NetSuite, with trade pricing, gift cards, customer data and inventory visibility all working from the same foundation.
If you're weighing up Shopify POS for your own retail rollout, our Shopify POS support services cover everything from feasibility and discovery through to rollout, training and support after launch.
And if you'd like a broader look at what Shopify POS can do before you get into the detail, our free ebook, Retail, Reimagined, walks through the platform, the hardware, the value case and further insight from our OKA rollout.
Join us in Birmingham
We're running Retail, Reimagined. as part of our Q4 eCommerce event series. Proudly sponsored by Shopify, we'll be running practical presentations on bringing in-store and eCommerce together, a merchant pane with retailers sharing insights and we'll giving hands-on demonstrations of new Shopify POS hardware and retail technology.
If you'd rather talk these decisions through in person, come along to the POS Roadshow in Birmingham on 9th September, where we'll be covering unified retail, rollout planning and lessons from projects like OKA.
