Running one shop is a rota. Running two is a puzzle. Running three is a second job.
Across the multi-site retailers JMS Dev Lab has worked with, what consistently surprises owners is how disproportionately hard scheduling gets every time another location is added. Going from one shop to two does not double the work — it roughly triples it. Going to three adds another layer that is somehow worse again. The rota itself is fine. What kills owners is the coordination around the rota: the swaps, the sickness cover, the one staff member who works across two shops and ends up double-booked because nobody noticed they were already in at the other one.
If you are running Shopify across more than one location and still trying to schedule staff from a spreadsheet and a WhatsApp group, you already know this. What this article will try to do is name exactly where it breaks, explain why it breaks harder with every additional shop, and walk through a practical setup that makes the whole thing calm again.
If you look at the surface, a second shop seems like a second rota. You build one schedule for Shop A, another for Shop B, share both with the relevant staff, and you are done. In practice, you are not done. Several things are happening that did not exist when you only had one shop.
Shared staff. You almost always have at least one person who can cover both shops. Maybe it is you. Maybe it is a full-time manager who floats. Maybe it is a Saturday worker who does not mind which shop they are at as long as the hours add up. Anyone who can appear on both rotas is a double-booking risk — one you did not have before.
Cross-cover dependencies. When someone calls in sick at Shop A, the first thing you look at is Shop B. Can you pull someone over? Which shop is quieter today? Who is trained to work at both? These questions did not exist when there was only one shop and the only option was "cover it yourself or close".
Differing opening hours. Rarely do two shops have identical opening hours. One might open later on Sundays. One might close for a half day on Wednesdays. The rota has to reflect that each location has its own operating shape, not a template stamped across both.
Different busy periods. Customers do not spread themselves evenly. One shop might be dead on Tuesday mornings while the other is run off its feet. You want staff where the customers are, which means your rotas need to be built from the location-level demand — not from staff availability alone.
Location-specific wage costs. If you are reporting by location in Shopify (which most multi-shop operators are, because you need it for stock and reporting anyway), you also want to know what each shop costs you to staff. A single blended payroll number hides which shop is actually profitable.
Each of those is manageable in isolation. Together, they form the reason Sunday nights are ruined.
When owners talk to me about multi-location scheduling headaches, the same few specific failures come up again and again. It is almost never "my rota is wrong". It is one of these six.
You have two rotas open, one per shop. You put Sarah in at Shop A on Saturday. Two tabs over, you put Sarah in at Shop B on the same Saturday. Nobody notices until Sarah notices, and by then you have already printed and shared both rotas. Nothing in a two-spreadsheet system warns you that one person is listed at two places at the same time.
Staff who work across locations sometimes read the wrong row of the wrong rota. They show up at Shop A on Monday when they were supposed to be at Shop B. Usually this is because the rota does not clearly mark the location on each shift — the document is called "Rota Shop A" and the shifts inside it just say "9 to 5" with no location tag. Fine in a single-shop setup. Dangerous the moment someone is working across multiple shops.
Someone phones in sick at 8am. You now need to: work out who is free, work out who is qualified to cover that role, work out who is closer to the shop, ring them, confirm, update both rotas, tell the rest of the team, and restart your day. This chain takes an hour minimum. In a single-shop operation it takes maybe fifteen minutes because there are fewer variables.
Two staff members quietly agree to swap shifts. They tell each other. Neither tells you. Neither updates the rota. One of them thinks the swap was for this week; the other thinks it was next week. One of the shifts is at the other shop, which nobody else knew about. Somebody does not turn up. You only find out when a customer complains.
New processes — a new returns policy, a new stock-count procedure, a seasonal campaign — need to reach all your staff across all your shops. In a single-shop operation you explain it once in the morning huddle. In a multi-shop operation you have to remember to explain it to every team at every shop, often on different days, and there is no system tracking who has and has not been told. Drift happens fast.
At 4pm you want to know: who is on at each shop right now, and who is on at each shop tomorrow morning. In a spreadsheet system, that is a minimum of two files open on your phone, both of which you hope are the latest version. It should be one screen.
Notice that none of these six is really about building the rota. They are all about what happens after the rota is published. That is the part spreadsheets cannot help with — and the part that eats managerial time across multi-location operations.
We're not anti-spreadsheet. For a one-shop operation with a small stable team, a spreadsheet rota is perfectly adequate. The manual-rota approach works fine at that scale. The trouble is that multi-location is exactly the scale at which it stops working, and the transition happens faster than you expect.
The core problem is that a spreadsheet is a static grid. It holds numbers well. It holds rows and columns well. What it does not hold is state — the state of who has confirmed, who has swapped, who has been notified, which version is current, which shifts are at which shop, and who has been trained on what. A rota has all of that state wrapped around it, and a spreadsheet cannot represent any of it.
WhatsApp patches some of that. It gets the rota in front of people. But it also turns the rota into a moving target, because every subsequent change goes into the same chat, and after two weeks the chat is a mess of screenshots, voice notes, and "lads is anyone around saturday". Nobody can find the current rota. Nobody can prove what the current rota said.
With one shop, you can hold all that in your head. With two, you cannot. With three, you stop even trying and you just hope.
If you are evaluating tools for multi-location scheduling, these are the capabilities that actually matter in practice. Many scheduling apps handle single-shop use cases well but fall over on these specifics.
That last point matters more than you might expect. Most generic scheduling tools — Deputy, When I Work, the various others — are perfectly capable, but they live outside your Shopify account. You have to set up staff twice, locations twice, and accept that the two systems will never quite talk to each other. If you are already committed to Shopify for your multi-shop operation, a Shopify-native tool closes that gap.
StaffHub is built inside your Shopify admin, which means it reads your existing locations and staff from Shopify rather than making you set them up again. That sounds like a small thing until you have had to maintain a parallel staff list in a second tool for a year and noticed how often it drifts out of sync.
A few practical points about how multi-location works in StaffHub:
None of this is magic. It is just the combination of features that a scheduling tool needs to actually be useful across more than one shop. The reason it feels like a step change is that the spreadsheet-plus-WhatsApp approach was never designed to handle any of this — and once you stop trying to make spreadsheets do scheduling work, the weekend back.
If you are moving from a spreadsheet-based multi-shop rota to a proper scheduling tool, here is how I would approach the first fortnight. This is broadly tool-agnostic, though the StaffHub flow fits it closely.
Week 1: Setup and parallel run.
Week 2: Full switch.
Most multi-shop operators find that by the end of week two they are not going back. The Sunday-night rota rebuild drops from two hours to about thirty minutes, and the mid-week scramble when something changes becomes genuinely five-minute work instead of an afternoon gone.
A fair question. The honest answer is that it is worth it when the coordination overhead is actively eating your time — and for multi-location operations, that threshold is lower than for single-shop ones.
If you tick any of these, the move is probably overdue:
If you only have one of these, a lighter fix might be enough — see how to schedule staff in Shopify without spreadsheets for a single-shop angle. If you have three or more of them, a proper tool pays for itself inside a month.
A lot of the literature on multi-location retail operations focuses on stock and sales reporting. Scheduling and staffing tend to get a paragraph in a chapter about "operations". That underweights it. Across the multi-shop Shopify retailers we work with at JMS Dev Lab, the single biggest lever on customer experience is whether you have the right people, trained on the right things, at the right shop, on the right day. None of your stock or marketing decisions matter if the shop is understaffed on the Saturday before Christmas because the rota fell over.
Multi-location scheduling is boring, recurring, thankless work. It is also where most of the small mistakes compound. Getting it onto a proper system is one of the highest-leverage unglamorous decisions you can make as a multi-shop Shopify owner.
StaffHub is built for Shopify, handles multiple locations natively, and is free for up to 5 staff with paid tiers from $12.99 per month. The 14-day trial on paid plans is free. If you run two or three shops on Shopify and your rota is still living in a spreadsheet, there is no cheaper test than trying it for a fortnight and seeing how much of your Sunday comes back.
Install StaffHub on Shopify — 14-Day Free Trial
Want to try a multi-location rota first? The free Multi-Location Rota Template Builder generates a printable weekly rota for 2–5 shops. No signup required.
Related reading: StaffHub vs EasyTeam · StaffHub vs Homebase · Homebase vs EasyTeam vs StaffHub · StaffHub vs manual rotas · Setting up staff training in your Shopify store · EasyTeam alternatives for Shopify staff management.