Rolling out LS Central to 50+ stores is a programme, not a project. Here's the wave-based phase plan we use to take chains from pilot to full coverage in 4–9 months.
Why retail rollouts fail without a wave plan
The most common cause of multi-store rollout failures isn't software — it's trying to go live everywhere at once. A 50-store chain that goes live in one weekend hits the same problem 50 times. A 50-store chain that goes live in waves of 3, 5, 8, 12, 22 fixes the problems on the way.
Here's the wave plan we use for chains of 20+ stores.
Phase 1 — Pilot store (4–6 weeks)
Pick the right pilot. Criteria: high transaction volume, representative format, willing manager, fast IT. Set up: BC tenant, LS Central, payment gateway, ZATCA / UAE FTA, integration to head-office HR / finance.
Go-live the pilot. Monitor for 10–14 days. Document every issue and fix. The next 49 stores will encounter the same issues — you're paying for the answers now.
Phase 2 — Master data harmonisation (parallel with pilot)
While the pilot is live, the head office team harmonises master data across all 49 remaining stores:
- Item master: deduplicate, standardise units of measure, item categories
- Customer master: clean duplicates, format phone numbers
- Vendor master: same
- GL: chart of accounts standardised, posting groups consistent
- Pricing: hierarchy of group/store/customer pricing finalised
Phase 3 — Wave 1: 3 stores (week 7–9)
Pick 3 stores that are geographically clustered for support efficiency. Target a 3-day-per-store go-live. Hyper-care SLA: on-site for 3 days, then on-call.
Issue rate per store drops by 40% compared to pilot. Documented playbook keeps growing.
Phase 4 — Wave 2: 5 stores (week 10–12)
Larger batch. Same hyper-care SLA. Train wave-2 store managers using wave-1 store managers as references.
Phase 5 — Wave 3: 8 stores (week 13–16)
Now you have rhythm. Issue rate per store at half of pilot. Add a remote-only hyper-care option for stores already comfortable.
Phase 6 — Wave 4-5: remaining 33 stores in two batches (week 17–22)
By now your team is processing 8–15 stores per week with minimal issue rate. Final batches go live with remote-only support except in the highest-volume locations.
Week 23+ — Hand to NovaCare
Switch from project mode to managed support via NovaCare AMC. Monthly release management, quarterly business reviews, ongoing optimisation.
Frequently asked questions
How long does a 50-store rollout actually take?
20–24 weeks from kick-off to all 50 live in our experience. Faster is possible but quality drops; slower wastes opportunity cost.
Should we go live during peak season?
Never. Freeze any go-lives 6 weeks before peak season; resume 4 weeks after. The pilot can run pre-peak; rollouts wait.
Do we need a project manager per wave?
One programme manager across the whole programme, plus a wave lead per wave. The wave lead becomes your operational champion in that batch of stores.
What if a store goes offline mid-rollout?
LS Central has offline POS — the store keeps transacting locally and syncs when connectivity returns. The wave plan should include a 24-hour LAN-only test on every store before go-live.
Can we do a big-bang instead of waves?
Yes for sub-5-store chains. For 5+ stores, every chain we've done big-bang has cost more in support hours than the wave version would have.
How do you train 50 store managers?
Train-the-trainer model: 6 super-users in wave 1, who then train wave-2 store managers. By wave 3 the training is fully delegated to internal champions.
Where to go next
Read the full overview of LS Central for retail. For a deeper dive into related capability, see NovaCare support. When you're ready to talk specifics, book a 30-minute call with a Novasoft consultant.