Multi-site groups: how to run a payments rollout without disrupting trade

The main reason groups consolidate is visibility: what each site made, by revenue centre, comparable week on week. That structure — sites, regions, departments, revenue centres — needs to be agreed and configured before terminals are deployed, because retrofitting it across live sites is painful and usually gets half done.

Agree who owns which report, how often it is produced, and what decision it informs. A reporting hierarchy nobody uses is just configuration.

Choose a mid-volume site with typical connectivity, not the flagship and not the quiet one. Run it for two complete trading weeks so you capture two weekends, a delivery cycle, a stocktake and at least one thing going wrong.

Collect the issues formally — from the site manager and the bar or floor staff, not just the head office view. The problems that derail rollouts are almost always operational details: where the terminal sits, how it charges, who reprints a receipt, what happens at cash-up.

After the pilot, deploy in waves of three to five sites, ideally early in the week. Keep the outgoing terminals live and physically on site for the first week of each wave. It costs almost nothing and eliminates the worst-case scenario during a Saturday service.

Do not schedule a wave into a site's peak week. Nobody should be learning a new terminal during a Christmas party season or a bank holiday weekend.

Training a general manager is not training a site. The people who need fifteen minutes of hands-on time are the bar staff, servers, receptionists and duty managers who will be alone with the terminal at nine on a Friday.

Leave one printed page per site: how to take a payment, how to refund, how to reprint, how to cash up, and who to phone. That single page prevents most out-of-hours support calls.

Groups accumulate legacy contracts. Before committing, check each site's existing terminal leases and processing agreements for notice periods and end dates — leases signed separately from the processing agreement are the usual trap and can run for years after the processing has moved.

Build the rollout schedule around those dates so you are not paying twice for longer than necessary.

The clearest difference between a smooth rollout and a bad one is having a named account lead who answers the phone at eight on a Saturday evening, rather than a portal that opens a ticket for Monday.

That is how we run every group rollout: one point of contact through pilot, waves and the first trading quarter, with direct access to Teya rather than a call centre queue. For groups, that responsiveness is usually worth more over a year than a marginal rate difference.