The five IT support challenges every UK retailer is wrestling with
Tills going down isn't an IT problem, it's a trading problem. The challenges that make retail IT support genuinely different from anyone else's.
Retail IT is a different sport. The estate is spread across postcodes, the customers are present in the room, and the busiest hour of the year is also the least forgiving. A generic IT support contract written for an office-bound business will keep head office happy and let the stores down on a Saturday afternoon.
These are the five challenges that come up in nearly every conversation with a multi-site retailer. None of them is exotic on its own. The combination is what makes retail support its own discipline.
1. Stores are remote branches that trade in cash
Every store is, in IT terms, a small remote branch with its own network, its own peripherals and its own assumption that someone will fix things before opening. That assumption is doing a lot of heavy lifting. When a circuit drops in a Sheffield branch at 11am on a Saturday, the manager wants the connection back, not a ticket reference.
The retailers who run this well treat each store as a monitored site rather than a postcode. Circuits are watched, EPOS terminals are watched, payment terminals are watched, and the support team sees the incident at the same moment the store does. Crucially, there is a runbook for the three or four faults that account for most of the calls, so the resolution is not improvised every time.
2. Peak periods do not forgive
Black Friday, the Christmas run-up and Boxing Day sales are not the moments to discover the ecommerce platform doesn't scale or the firewall rules at head office are wrong. They are also not the moments to be deploying anything new. The peak window is, for an IT team, a freeze: changes are minimised, monitoring is heightened, and the support shift pattern looks different.
Underneath that is a year-round capacity conversation. The platform that coped last year may not cope this year because the marketing team has more budget; the third-party fulfilment integration that worked at 1,000 orders a day may sit down at 4,000. The retailers who get through peak without drama are the ones who modelled it in October, not the ones who hoped in November.
3. Card data and PCI carry weight
Even when card payments are outsourced to a provider like Adyen, Stripe or Worldpay, the network the terminals sit on, the staff using them and the supporting systems remain in PCI scope. Auditors and acquirers know this. 'We don't store card data' is a starting point in the conversation, not the end of it.
Practically, that means the cardholder network is segmented from the rest of the store, the staff have current training, the evidence sits in a folder somebody could find at short notice, and the annual self-assessment isn't a fortnight of panic in March. Most retailers know roughly where they sit on this and roughly where they should sit; the gap is usually time and attention, not money.
4. Omnichannel sounds simple, isn't
Customers expect to see live stock on the website, reserve it in store, return a web order to a branch, and have a refund hit their card without a phone call. Behind that promise is a mesh of integrations: EPOS to ERP, ERP to ecommerce, ecommerce to warehouse, warehouse back to EPOS. Each link has an owner, a maintenance window, and a way of breaking that nobody documented properly.
This is where most retailers find their integration debt. Click-and-collect, in particular, makes the debt visible: a customer standing at a counter holding a confirmation email is a difficult audience for 'the systems aren't talking right now'. The fix is rarely a single big platform replacement. It is steady, boring work: monitoring the integrations, owning them, and giving someone the budget to fix them when they wobble.
5. Seasonal staff churn through accounts
Retail hires fast and lets go fast. Christmas temps, summer extras, regional cover and the constant churn of weekend staff all need accounts, devices and access. They also need to lose them cleanly when they leave. A joiner-leaver process that works at twenty people a year falls over at two hundred.
Identity hygiene at retail scale is mostly about automation. Entra ID groups driven from the HR system, conditional access that doesn't require IT to think about every hire, and an offboarding flow that revokes access the day employment ends rather than at the next quarterly cleanup. MFA needs to be the default for everyone with any access to head office systems, no exceptions for managers who find it inconvenient.
What good looks like
A retail-savvy partner monitors stores as sites, knows the EPOS vendor and the payment provider, and has a trading-day playbook everyone trusts. They help head office get sensible use out of Microsoft 365, Power BI and SharePoint without turning it into a bureaucracy. Around peak, they are more present, not less.
Tell us how many stores, which EPOS and which payment provider. We will introduce you to a UK partner that already supports retailers and understands that a Saturday afternoon outage is a trading event, not a ticket.
Need the right partner for this?
We'll connect you with a UK specialist.
Tell us where you are and we'll introduce a Microsoft-focused managed support specialist who fits.
Connect me with a specialistMore in strategy
- 22 April 2026 · 7 min
Why Copilot rollouts stall before they pay back
Most Microsoft 365 Copilot pilots get bought, lit up, and quietly stall. The problem usually isn't the AI - it's the data and the habits underneath it.
Read - 25 March 2026 · 8 min
Internal IT hire or managed partner? Two different problems
The choice between hiring in-house and outsourcing isn't really about cost. It's about the kind of work you need someone to own.
Read