Large-Scale EPOS Deployment

Royal Ascot and similar major events need an EPOS estate that is configured, installed, paid, printed and supportable before trading starts. This work covers planning and delivering that estate across approximately 750 terminals, 180 outlets and 35 sites — including retail, hospitality, fine dining, bars, boxes and cellar operations.

A deployment of this size fails in the gaps: a terminal that looks installed but is not configured, a printer on the wrong outlet, a payment device that has not been paired, or a site that is physically ready but operationally incomplete. Informal tracking does not survive hundreds of devices.

• Consistent terminal configuration across outlets
• A way to track installation and readiness by site and outlet
• Printer, network and payment device checks included in the same process
• A support path for issues found before and during trading
• Documentation that other people can actually use on site

Led EPOS delivery in a permanent senior capacity: KAPPTURE configuration, deployment readiness, issue tracking and operational coordination of approximately 10 internal staff plus 6+ KAPPTURE engineers. The job was to make the estate predictable, not just to place hardware.

• Define what 'ready' means for a terminal, outlet and site — configuration, peripherals, payments and network
• Track installation against that definition rather than against a simple delivered/not-delivered flag
• Keep printers, payment devices and networking in the same checking process as the till
• Route issues into a support process with enough context to fix them without another site walk
• Coordinate with operational stakeholders so exceptions are visible before trading, not during it

The estate is hierarchical: site → outlet → terminal → payment device. Readiness has to be true at each level. A site is not ready because most terminals are on; it is ready when the outlets that will trade can take an order, print, take payment and be supported.

• Standardised configuration patterns for terminal types and outlet roles
• Installation and deployment checks covering hardware, peripherals and payments
• Digital operational checklists for installation, testing and issue management
• Support processes for pre-event faults and in-event failures
• Documentation and training for installers, support and operational leads

• Temporary infrastructure and compressed timelines
• Mixed device types: counter terminals, MPOS, printers and payment devices
• Keeping configuration, physical install and payment pairing in sync
• Communicating status in a way operations can act on

The estate could be talked about in operational terms — which sites and outlets were ready, which checks were outstanding, and which issues would block trading. The same delivery model has also supported other major hospitality operations including PGA Wentworth and the Royal Windsor Horse Show. Scale figures describe the size of the operation, not a software product metric.

• Estate visibility across sites, outlets and terminals
• Fewer last-minute unknowns at go-live
• A repeatable checking process instead of informal sign-off

• Deployment quality is a process problem as much as a technical one
• Readiness needs a definition that includes payments and printing, not only the till being on
• Tracking only works if the unit of work matches how the venue actually trades

• Tighter exception dashboards for outstanding checks
• Faster pairing of payment device status with terminal status
• Reusable playbooks for different venue types