Multi Site EPOS Rollout
Replacing point of sale across an estate looks like a technology project and behaves like a logistics one. The system itself is usually proven. What breaks is doing the same installation over and over, at sites that each have their own trading pattern and their own manager.
Elisabeth Butler is an interim IT Programme Manager who takes ownership of multi site EPOS rollouts and delivers them. She has delivered till estates as part of full infrastructure programmes, coordinating vendors under a single delivery framework in environments where the public facing operation could not be interrupted.
EPOS Rollout Programme Management
The engagement is hands on delivery leadership, not advisory work. It covers four things.
- A repeatable installation model: Turning the rollout into a factory process. Standardised installation packages, hardware pre-configured before it leaves the warehouse, and a fixed sequence that any installation team can execute identically at any site.
- Single vendor framework: Bringing hardware supply, software configuration, connectivity, payment processing and physical installation under one governance structure with shared milestone tracking and clear accountability for each supplier's deliverables.
- Store scheduling that respects trade: Building a rollout plan with retail operations rather than at them, working around peak trading, local events and site specific constraints so that store managers stop resisting the schedule.
- Delivery to full estate completion: Owning the programme through to every site live, stable and handed over, including the tail of difficult locations that rollouts usually abandon.
Why Multi Site EPOS Rollouts Stall
These programmes rarely fail on technology. They fail on coordination, and the pattern is consistent.
- Multiple sites with restricted access means installation teams arrive at sites that are not ready.
- Installations are treated as individual projects rather than a repeated process, so nothing gets faster after the tenth site.
- Trading disruption is underestimated, store managers push back, and the schedule enters a cycle of rescheduling that becomes impossible to manage.
- Escalations take weeks to resolve because there is no route to a decision maker with authority over every supplier.
- The rollout rate is reported against the original plan long after the original plan became fiction.
- Difficult sites get deferred repeatedly until a tail of unfinished locations sits there for months.
The Factory Model for Store Rollouts
The single biggest change available to a stalled rollout is converting it from a series of projects into a production line. Hardware arrives pre-configured rather than being built on site. The installation package is identical everywhere, so the team is executing a known sequence rather than solving problems. Connectivity and payment integration are confirmed as ready before an install slot is committed, not discovered on the night.
On the programme Elisabeth led, sequencing and pre-configuration were what protected trading hours, particularly at sites that stayed open to the public throughout.
Independent Leadership on Estate Wide Rollouts
The EPOS vendor can deliver its own component competently and still be unable to run the programme. It has no authority over the site, no standing with your store operations team, and an obvious interest in how its own performance is reported.
An independent interim Programme Manager carries none of that. The reporting to the board is accurate because there is no reason for it not to be, and the vendors are held to measurable commitments by someone whose only interest is the estate being finished.
Elisabeth has delivered programmes across enterprise technology, financial services, heritage and the public sector, and works with organisations across the UK.
Common Questions
How long should an EPOS rollout take?
Six to nine months is realistic with a standardised install package and coordinated vendor scheduling. On a recent heritage programme Elisabeth delivered infrastructure across ten sites in five and a half months, reaching first wave go live two weeks ahead of schedule. What determines the answer is whether installation has become a repeatable process.
How much trading disruption should we expect?
A single overnight window per site. Poorly planned rollouts routinely cost stores two to three trading days each, which is where most of the resistance to the schedule comes from.
Can a stalled rollout be recovered without starting again?
Almost always. The hardware and licences are already bought and the configuration work usually holds its value. What needs rebuilding is the delivery model and the vendor framework around it, not the technology.
What is the difference between EPOS and POS?
None that matters here. EPOS is the standard term in UK retail and hospitality, POS is more common in international and enterprise settings. The delivery challenge is identical.
Related reading:
Related case studies:
- Heritage IT Infrastructure Programme
- Legal Deeds Digitisation
- Enterprise ERP Programme Rescue
- Public Sector Digital Transformation
Related services:
Need experienced programme leadership for a rollout across your estate? Get in touch.