The Multi-Location Ops Pack

1. The 4-week rotation pattern

Most multi-location rotas fail on fairness. The same staff get weekends, the same staff get late shifts, and resentment builds quietly until somebody quits. This 4-week pattern rotates fairness for a 6-staff, 2-location setup so every staff member sees an even share of weekends, late shifts, and cross-location coverage.

The rules

• 6 staff total, 3 anchored to Shop A and 3 anchored to Shop B as their primary location.
• Each staff member works 5 days/week, has 2 days off.
• Each cycle is 4 weeks long, then repeats. After 4 weeks every staff member has had: one weekend off, one full week of late-shift-free, one week at the other shop.
• Three shift types: Early (07–13), Mid (11–17), Late (13–19). One Cross-shift means the staff member works at the other location that day.

The pattern (Shop A, weeks 1–4)

Shop B uses the same pattern with staff B1/B2/B3, offset by 2 weeks — so when Shop A staff are on a "cross-B" week, Shop B staff are on a "cross-A" week. The two shops are reciprocally covered.

What this gives each staff member after one full cycle

• One full weekend off (Sat + Sun) once per 4 weeks.
• Two weekend days off (one Sat, one Sun, on different weekends) every other week.
• One week with no late shifts per 4 weeks.
• One week at the other shop — either to learn a different customer base, or to give a colleague a different rotation.

How to adapt the pattern

• For 4 staff per shop: add a fourth row per week with the same shift-rotation logic, just one offset deeper into the cycle.
• For a single shop: drop the Cross-B column — everyone stays at the home shop. Fairness logic still works.
• For a 5-day-a-week operation: remove Sat+Sun columns entirely; the shift rotation compresses into the 5 weekdays without changing the fairness math.
• For staff who can't do certain shifts (school pickup, second job, etc.): pin that staff member's "Off" slots to the constrained day, then rotate the remaining staff through the open shifts.

2. The cross-location swap process

Staff want to swap shifts across locations because their commute or college timetable favours the other shop. Most managers reject these because they create coverage chaos — or approve them ad-hoc and lose track of who's actually working where. The 5-step process below makes swaps safe and traceable.

The 5 steps

What goes wrong if you skip steps

• Skip step 3 (manager sign-off): staff member B turns up at Shop A and doesn't know how to operate the back-office return-with-fitting workflow. Customer ends up frustrated. Manager at Shop A has to drop their own work to coach.
• Skip step 4 (written confirmation): the swap was a verbal agreement; one staff member misremembers the date; both turn up; one doesn't. Coverage doubled at one shop, missing at the other.
• Skip step 5 (rota update + pattern record): over months you don't notice that one staff member has done 80% of the swap-acceptances and is working twice as many cross-location shifts as anyone else. Burnout follows.

Manager rules of thumb

• Approve by default. Reject only when the qualifications gate isn't met or when one staff member is being asked to bear a disproportionate share. The cost of friction on the manager's side is a slow erosion of staff goodwill.
• Don't allow same-day swaps. Minimum 24 hours' notice. Same-day swaps too often mean the original staff member just doesn't show up.
• Cap any one staff member at 2 cross-location shifts per week. Beyond that, you're rebuilding the rota, not swapping shifts.

3. The 60-day "second shop opening" checklist

What to set up before the second shop opens, sorted by how badly things break if you skip them. The retailers who handle multi-location transitions smoothly do most of this before opening day, not after.

4. Why these three together

The three pieces of this Pack — rotation pattern, swap process, opening checklist — aren't independent.

The rotation pattern produces a fair baseline rota, which means the swap process is for genuine preferences (a college shift, a family commitment), not for fixing an unfair pattern. If the baseline rota is unfair, the swap process becomes the way staff route around the unfairness — and the manager spends all week adjudicating swaps instead of running the shops.

The opening checklist sets up the conditions under which the rotation pattern and swap process can actually function. Without a written training checklist, "qualified to work the other shop" is a judgement call the manager has to make personally. With one, it's a yes/no based on the competency-check completion record.

Across the multi-location Shopify retailers our software supports at JMS Dev Lab, the pattern is consistent: the retailers who treat multi-location as a systems-design problem during the planning phase spend the first 6 months of two-shop operation enjoying the new shop. The retailers who treat it as "we'll figure it out as we go" spend the first 6 months firefighting and lose at least one good staff member before the system catches up.

This Pack is what we see working. Every retailer's specifics differ — staff numbers, opening hours, payroll cadence, country of operation — but the underlying patterns travel.