Oct 29, 2026Chain Operations
Multi-Site Ware Rollouts: From One Store to Fifty
The fleet change that works in one store fails in fifty. The rollout system — pilots, waves, the kit discipline and the legacy fleet's exit — that scales without chaos.
The fleet change that works in one store fails in fifty: the color that drifts by region, the kit that misses a piece, the old fleet that never quite leaves. The multi-site rollout is its own discipline — pilots that prove, waves that scale, kits that are exact, and the legacy fleet's managed exit. This guide is the rollout system.
The Pilot Gate
No fleet change scales from the showroom: the pilot gate — the change run in two or three real stores, for a real period, measured against real criteria. The pilot's tests: the operational fit (the wash, the stack, the service flow), the guest response (the comment cards, the server feedback), the durability's reality (the cycle count in the house's machines), and the color under the stores' light. The pilot's exit criteria written before it starts — the gate that separates enthusiasm from evidence.
The Wave Plan
The rollout runs in waves: stores grouped by region or by fleet age, each wave's window stated, the support resourced per wave. The wave logic: the first wave after the pilot carries the lessons (the kit's corrections applied), the waves sized to the support's capacity (the distribution center's picking, the training's reach), and the sequence that respects the calendar (the peaks avoided — no fleet change during the holiday storm). The wave plan is the rollout's tempo: steady, resourced, reversible.
The Kit Discipline
Every store receives the same kit: the exact piece list per format (the baseline's pieces per cover, the buffers, the small ware), versioned and audited. The kit's rules: the manifest checked at receiving (the missing piece discovered at the dock, not the dinner rush), the kit's cost transparent per store (the capex line the P&L sees), and the versioning's rigor (kit v2's changes documented — the fifty-store confusion that version drift creates). The kit discipline is the rollout's unit of trust: the store that opens its boxes knows what should be there.
The Legacy Fleet's Exit
The old fleet's exit is the rollout's half-finished job: the legacy pieces retired, redistributed or stored — deliberately. The exit's options: the retirement line (the worn pieces out on schedule), the redistribution (the legacy fleet to the staff canteen, the secondary brand, the charity channel), the storage (the transition set that covers the gap weeks), and the sale where the assets are worth it. The exit's discipline: the legacy fleet's exit date on the rollout plan — the two-fleet patchwork that "temporarily" lasts a year is the rollout's most common scar.
The Training Wave
The new fleet changes handling: the training wave rides the rollout — the care rules for the new materials, the dish-pit's boundaries (the new glaze's chemistry, the new rack), the service's adjustments (the new piece's carry, the new stack's height). The training's tools: the one-page care card per material (posted at the pit and the pass), the fifteen-minute shift briefing, and the pilot store's trainers who carry the lessons forward. The training wave is where the rollout's investment is protected — the fleet that is bought but not taught is the fleet that breaks early.
The Distribution Center's Role
The rollout's logistics hub: the DC receives, checks, kitting and ships — the rollout's flow depends on its discipline. The DC's tasks: the incoming batch checks (the color against the sealed reference, before the fleet ships), the kit assembly's manifest discipline, the wave's shipping calendar, and the returns handling (the legacy fleet's inbound, the damaged pieces' quarantine). The DC is the rollout's throat: its accuracy decides whether the waves land complete.
The Measurement Layer
The rollout is measured, not assumed: the adoption rate (the kit in service, per store, per week), the defect read (the breakage and complaints in the first cycle), the guest and staff response (the pilot's criteria, measured network-wide), and the budget's actuals (the kit's cost against the plan). The measurement's discipline: the dashboard per wave, the variances investigated, the lessons folded into the next wave. The rollout that measures itself finishes; the one that assumes drifts into the patchwork.
The Completion Line
The rollout ends with a line drawn: the completion audit (every store's kit verified, the legacy fleet's exit confirmed, the fleet age map updated), the lessons documented (the next rollout's playbook improved), and the program's handoff (the rollout team's plan to the operations team's routine). The completion line is where the change becomes the standard: the fleet that was new is now the fleet.
Frequently Asked Questions
Why run a pilot gate? The showroom lies: the change proven in two real stores — operational fit, guest response, durability, color — with exit criteria written before it starts.
How are waves planned? By region or fleet age, sized to support capacity, sequenced around the calendar's peaks, with the pilot's lessons folded in before wave one scales.
What is the kit discipline? The exact piece list per format, versioned, audited at receiving: the store that opens its boxes knows what should be there.
What is the rollout's most common scar? The legacy fleet that never exits — the two-generation patchwork that "temporarily" lasts a year. The exit date goes on the plan.
What does the completion line add? The audit that verifies every store, the lessons documented for the next rollout, and the handoff from project to routine — the change becomes the standard.
