The phone rings at 8.03am. One of your team is sick. Under normal circumstances, you would sort it in ten minutes: check who is free, ring them, update the rota, carry on with your morning. When you run more than one Shopify shop, that ten-minute problem becomes an hour-long problem — and that hour comes out of the time you had planned to spend doing something useful.
Across the multi-site retailers JMS Dev Lab works with, sickness calls are a weekly occurrence. For the first few years of multi-shop operation, each one feels like a crisis — because each one forces the owner to work through the same tangle of questions: who can cover, are they trained for that shop, does taking them leave their usual shop short, can they get there in time? Without a system, every call gets improvised from scratch.
It does not have to be that way. The solution is not complicated — it is just a system, built once, that you run the same way every time. This article walks you through it.
In a single-shop operation, a sickness absence means: find someone free, ask them to cover, update the rota. The decision tree has two branches — yes they can, no they cannot.
In a multi-location operation, the same call branches into four separate problems at once:
Location eligibility. The obvious pool of cover people — the rest of your team — may not all be able to work at the affected shop. Someone trained for Shop A's processes and POS setup cannot automatically cover Shop B. Before you can confirm cover, you need to know who is actually eligible.
Cross-location availability. The person you want to call in might already be scheduled at your other shop. Pulling them to cover Shop A might leave Shop B short. You now have two rotas to check, not one, before you can safely say yes to anyone.
Travel and timing. If the cover person works at a different location, they may need travel time you have not accounted for. A 9am opening needs cover who can arrive by 8.45am. If they live on the other side of the city and usually work the afternoon shift at Shop B, the logistics may not work even if the person is willing.
The cascade risk. The scariest version of a multi-location absence is when fixing it at Shop A breaks Shop B. You move someone from Shop B to cover Shop A. Now Shop B is thin. A second sickness call later in the day and Shop B is the emergency. You solved the first problem by creating the conditions for a second one.
None of these problems are hard to solve in isolation. The difficulty is that they all arrive at once, at 8am, and you need to resolve them in the right order before the shop opens.
When a sickness call comes in for one of your multi-location shops, you need to make four decisions in sequence. Getting them in the wrong order wastes time and sometimes creates new problems.
Before you start ringing round, ask whether the shift actually needs cover. A quiet Tuesday afternoon might run fine with one fewer person. A Saturday opening shift in your busiest shop almost certainly cannot. The answer determines how urgently you need to act and how far you can reach — asking someone to extend a shift is much easier than asking someone to come in on their day off.
The easiest cover is someone already at the affected shop who is on a shorter shift, a later start, or a day where they could extend. Check the affected shop's rota before you look anywhere else. This person does not need to travel, is definitely trained for that shop, and taking them does not affect your other locations.
If nobody at the affected shop can cover, look at cross-trained staff at your other locations. Before you ring anyone, confirm:
Only ring someone when all four pass. Ringing first and checking eligibility second means you are making promises you may have to retract, which is worse for morale than a short wait.
As soon as someone agrees to cover, update the rota for the affected shop and — if they have been moved from another location — update that shop's rota too. Do not leave one updated and the other behind. By lunchtime, whoever manages each shop will be looking at the rota on their phone, and you want both to reflect reality.
The worst time to figure out who your cross-location cover options are is at 8am on a Tuesday when someone just called in sick. The best time is on a calm Thursday afternoon when nothing is on fire.
Take twenty minutes to build what I call a cover list. It is a simple document — one page — with three columns:
When a sick call comes in, you open the cover list, filter by the affected shop, and work down in order of least disruption. This takes two minutes instead of fifteen.
Update the list whenever someone completes training at a new location, or whenever someone's availability changes. A stale cover list is worse than no list, because it sends you chasing people who cannot actually help.
The most common failure in multi-location absence cover is not getting the cover wrong — it is failing to tell both shops what is happening.
You ring round, find cover, confirm it with the cover person. You update the rota. But the manager at the affected shop does not know who is coming in, when they will arrive, or which role they are covering. The cover person arrives, nobody is expecting them, there is a confused ten minutes at the start of what was already a difficult morning. Or worse: the cover person turns up at the wrong shop entirely, because they were told "Shop A" but remembered it as the address of Shop B.
When cover is confirmed, send a message to three people: the cover person (confirms the details), the manager at the affected shop (they know who is coming and when), and anyone at the departing shop who needs to know their colleague will not be in (so they can prepare).
The message does not need to be long. It needs to be specific about location, time, and role. Specifics prevent the confusion that wastes the first hour of a short-staffed shift.
Sometimes cover is not available. Nobody eligible is free. Moving someone from another shop would break that shop. You cannot open on full staff.
Running short is the right call when the alternative is creating a bigger problem elsewhere. A shop at 80% staffing is usually manageable. Two shops at 50% because you tried to solve one problem by robbing the other is not.
When you decide to run short, do three things: tell the affected shop manager so they can plan the shift accordingly, adjust expectations (slower service, some tasks deferred), and document it. If the same shop is regularly running short, the pattern will show up in your records and you can address the underlying rota gap rather than firefighting the symptoms.
Every step in this process depends on information: who is trained for which shop, who is free, who is already scheduled, who has already covered extra shifts this month. In a spreadsheet-based setup, gathering that information during a sick call takes ten to fifteen minutes of cross-referencing tabs and ringing people to ask if they are free.
A scheduling tool that holds your full roster — trained locations, current schedule, availability — compresses that ten minutes to about ninety seconds. You open the app, filter by the affected location, and your eligible free staff are in front of you. You can confirm cover and update the rota from the same screen, so both shops see the change at the same time.
StaffHub is built for this specifically. Because it runs inside Shopify, it already knows which staff are assigned to which locations. When you need absence cover, the app shows you who is eligible and available for the affected shop — it does not surface people who are already working elsewhere that day or who have not been assigned to that location. The collision checks happen before you ring, not after.
That speed matters less for the rare big emergency and more for the steady frequency of smaller absences that make up the real texture of running a retail operation. If you are spending twenty minutes per absence call and you have three or four absences a week across your locations, that is more than an hour a week spent on logistics that should take fifteen minutes total.
If you run two or more Shopify shops and currently manage absences from a spreadsheet and WhatsApp group, the first sick call you handle through a proper tool will show you immediately how much time the old method was costing. StaffHub is free for up to 5 staff, paid tiers start at $12.99 per month with a free 14-day trial, and the setup takes less than an afternoon — much less time than the first absence call you save.
Install StaffHub on Shopify — 14-Day Free Trial
Managing the wider scheduling picture? The free Multi-Location Rota Template Builder generates a printable weekly rota for up to 5 shops. No signup required.
Start with the same-location team first — the easiest cover is someone already at that shop who can extend their shift or come in early. If that fails, look at cross-location staff: people trained for both shops who are free that day. A scheduling tool that shows real-time availability across all locations makes this search take two minutes instead of fifteen.
Not necessarily every person, but you want at least two or three per shift pattern who can cover across shops. Think of it as a bench: your first-choice cover is within the same shop, your second choice is a cross-trained floater. Training two or three flexible people per shift type is the minimum to avoid a shop going unstaffed.
Four things: is the cover person trained for that shop's processes, are they free for the relevant hours, would taking them leave their usual shop short, and does travel time allow them to arrive on time? If all four pass, approve. If any one fails, look at the next option.
Keep a log of who has covered extra shifts in the past 30 days. When you need cover, check that log before you ring. Most small retail teams have one person who is always willing — which is great until that person burns out. A rotation, even informal, distributes the goodwill more fairly.
For an emergency same-day call, you cannot give more notice than you have. But you can reduce the friction: keep the ask short, confirm the hours, confirm the location clearly, and confirm the pay rate before they agree. For a planned shortfall you can see coming, try to give 48 hours minimum.
Related reading: Multi-location staff scheduling for Shopify: the practical guide · How to handle cross-store shift swaps · Setting up staff training in your Shopify store · StaffHub vs manual rotas · Free vs paid scheduling tools for Shopify multi-location.