The single most effective thing you can do right now is run a short pre-call checklist before contacting your EPOS supplier, and then test your support line at a realistic trading hour this week. Most POS failures are fixed by simple checks — a restart, a cable swap, or a network reset — and knowing your vendor actually answers at 8 PM on a Saturday is worth more than any contract clause.
Start here — before you call support:
- Check your internet connection (router lights, speed test on a phone)
- Restart the EPOS terminal and card reader
- Check all cables are seated firmly (power, ethernet, receipt printer)
- Switch to offline payment mode if available
- Put up a simple “card machine temporarily unavailable” sign
- Note the time, error code, and what you were doing when the fault appeared
Do these six things and you will resolve a large share of incidents without a support call, keep customers informed, and give your vendor the information they need when you do escalate. Less downtime, calmer staff, and customers who leave rather than walk out.
Table of Contents
- Your 10-point POS support checklist to implement today
- How to train staff and build simple SOPs for POS incidents
- How to define a clear support process, escalation path and SLAs
- How to minimise downtime with redundancy, offline modes and spares
- Is your vendor’s 24/7 support actually 24/7?
- What to say to customers during a POS outage
- Which KPIs should you track for POS support performance?
- Staff troubleshooting flow: what to do when the POS fails
- What does POS support actually cost in the UK?
- How staff communicate during POS issues: the skills that matter
- Data security and privacy during POS support and troubleshooting
- Key takeaways
- Why fast POS support is a business-critical issue, not just an IT one
- Switch-and-save: EPOS systems built for UK trading hours
- Useful sources and further reading
- FAQ
Your 10-point POS support checklist to implement today
Pin this at the till or save it to your staff group chat. It covers the full arc from first symptom to resolution.
| # | Action | Done? |
|---|---|---|
| 1 | Check router lights and run a quick speed test | ☐ |
| 2 | Restart the EPOS terminal (full power cycle, not sleep) | ☐ |
| 3 | Restart the card reader and re-pair if needed | ☐ |
| 4 | Check all cables: power, ethernet, USB peripherals | ☐ |
| 5 | Switch to offline payment mode if your system supports it | ☐ |
| 6 | Open your cash float and note the amount available | ☐ |
| 7 | Put up customer-facing signage explaining the situation | ☐ |
| 8 | Log the fault: time, error code, what triggered it | ☐ |
| 9 | Call your vendor support line — not email, not chat | ☐ |
| 10 | Test your support line at 20:00 on a Saturday at least once a quarter | ☐ |
That last item is not a joke. Call your vendor at a busy trading hour to confirm a human answers. If you reach voicemail, you have learned something important before it costs you a Saturday night’s revenue.
How to train staff and build simple SOPs for POS incidents
Staff training for POS support does not need to be a day-long course. A single laminated one-pager at the till does more good than a manual nobody reads.
Divide incidents into two categories:
- Staff can fix: card reader restart, receipt printer jam, basic void or refund, switching to offline mode, logging a fault
- Must escalate: payment processing failure, full system outage, KDS (kitchen display system) offline, suspected data breach, hardware damage
For each “staff can fix” scenario, write a one-page SOP. Keep it to five steps maximum. Add a one-line customer script alongside each step — for example: “Apologies for the wait, we’re just restarting the card reader — it’ll be back in under a minute.” That script removes the awkward silence that makes customers anxious.
Your escalation tree should answer three questions: who do staff call first, what do they say, and what do they document? A simple version: (1) attempt the checklist, (2) call the duty manager, (3) duty manager calls vendor support. Staff capture the error code, time, and last transaction. That information cuts vendor diagnosis time significantly.
Pro Tip: Run a five-minute simulated drill once a month — ideally the duty manager triggers a fake “card reader offline” scenario during a quiet period. Staff who have practised once respond far more calmly during a real Friday-evening failure. See the staff training guide for a full drill framework.
A study of UK frontline retail workers found that many frontline employees cited lack of real-time visibility as a top issue, along with poor connectivity between systems. Simple dashboards and clear SOPs directly address both. According to a recent study, 47% of frontline employees identified lack of real-time visibility as a top issue, and 46% cited poor user experience and weak connectivity between systems.
How to define a clear support process, escalation path and SLAs
A support process is only useful if it is written down and tested. Here is what a practical escalation path looks like for a UK retail or hospitality business.
| Priority | Incident type | Target response | Target resolution |
|---|---|---|---|
| P1 | Full system outage, payment failure | 15 minutes | 2 hours |
| P2 | Single terminal down, printer offline | 1 hour | 4 hours |
| P3 | Reporting error, minor software glitch | Next business day | — |
For P1 incidents, SLAs must be measured in minutes, not hours. A “next business day” commitment is useless for a restaurant that loses a Saturday evening service. When negotiating with any vendor, ask explicitly: what is your P1 response commitment on a Saturday at 7 PM?
Keep an incident log. A simple spreadsheet with five columns works: date/time, incident description, error code, actions taken, resolution time. Review it monthly. Patterns emerge quickly — the same card reader failing every three weeks, or connectivity dropping every time it rains (a real issue in older buildings with poor cabling).
Phone support that connects to a human during trading hours is worth more than any 24/7 email or chat channel. When you are mid-service with a queue at the till, you need a voice, not a ticket number.
How to minimise downtime with redundancy, offline modes and spares
A single point of failure should never take your whole operation down. The fix is straightforward: keep spares, know your offline options, and protect your power supply.
Essential on-site spares:
- A spare card reader (pre-paired and tested monthly)
- A spare receipt printer or roll stock
- A mobile data dongle or backup router as a network failover
- A small cash float (minimum £50–£100 depending on your average transaction)
- Spare power cables and USB leads for your EPOS stack
Offline payment modes let your card terminal continue processing transactions without a live internet connection, storing them for batch submission once connectivity returns. Check with your payment provider whether your terminal supports this, and test it before you need it. Not all terminals handle offline mode the same way, and some have transaction limits.
A UPS (uninterruptible power supply) protects your EPOS terminal, router, and card reader from power cuts and surges. Prioritise the router first — most EPOS failures during power fluctuations are actually network drops, not hardware failures. A basic UPS costs less than an hour of lost trading on a busy Saturday.
A small cash float and clear physical signage are your fastest customer-facing mitigations. Keep both ready at all times. For hardware setup specifics, the POS hardware setup guide covers spare-parts planning in detail.
Is your vendor’s 24/7 support actually 24/7?
The short answer: verify it before you sign anything. Proactive monitoring catches and resolves many failures before staff even notice — but only if a real engineer is watching the dashboard, not an automated alert routing to an empty inbox.
Ask your vendor these questions directly:
- Who answers the phone at 9 PM on a Sunday? Name a person or a rota.
- Is out-of-hours support a live service desk or a voicemail with a callback promise?
- What is the escalation path if the first-line agent cannot resolve the issue?
- Does your monitoring cover network, terminal connectivity, and payment gateway status?
- Can you provide remote access to diagnose and fix issues without an on-site visit?
Remote access is a genuine time-saver. A vendor who can connect securely to your EPOS terminal and fix a configuration issue in 20 minutes is far more valuable than one who books an engineer visit for next Tuesday. Ensure any remote access is via a vetted, encrypted connection — never allow access over an unverified link or a personal email request.
Paying for genuinely always-on, monitored support is often cheaper than the combined cost of a single peak-period outage: lost revenue, operational disruption, and the reputational damage of turning customers away. That calculation changes how you think about the monthly fee. For more on what good EPOS customer support looks like in practice, it is worth reading through the full breakdown.
Scheduled patches and health checks outside busy trading windows are a sign of a mature support partner. Ask whether your vendor does this proactively or only when you report a problem.
What to say to customers during a POS outage
How you communicate during a fault matters as much as how fast you fix it. Customers are forgiving when they feel informed; they are not forgiving when staff look panicked and say nothing.
Simple staff phrases that work:
- “Apologies for the inconvenience — our card machine is having a brief issue. We can take cash, or if you’d prefer to wait two minutes while we reset it, we’re happy to do that.”
- “We’re aware of the issue and our team is sorting it right now. Thank you for your patience.”
- “We’re temporarily cash only — there’s a cashpoint just around the corner on [street name] if that helps.”
Keep a small stack of pre-printed signs at the till: “Card payments temporarily unavailable — cash accepted” and “We’re back up and running — card payments now available.” Digital signage is faster to update if you have a screen near the entrance.
For hospitality, keep a manual order pad and a carbon-copy receipt book behind the bar or at the host station. If your KDS goes offline, orders can still be taken and communicated to the kitchen verbally. It is not elegant, but it keeps service moving and customers seated rather than walking out.
Which KPIs should you track for POS support performance?
You cannot improve what you do not measure. These four metrics give you a clear picture without requiring a dedicated IT team to collect them.
| KPI | What it measures | How to collect it |
|---|---|---|
| System uptime (%) | Time the EPOS is fully operational | Incident log: total downtime minutes per month |
| Mean time to resolution (MTTR) | Average time from fault report to fix | Incident log: open time vs close time |
| First-contact resolution rate | Faults fixed on the first support call | Tick column in incident log |
| Customer-impact minutes | Minutes of trading affected per incident | Incident log: trading hours affected |
Run a monthly review of these four figures. If MTTR is creeping up, your vendor’s response is slowing — raise it with them before it becomes a pattern. If first-contact resolution is low, your pre-call checklist needs updating or your staff need a refresher drill.
A simple test plan: once a month, call your support line at a realistic trading time. Once a quarter, run a simulated Saturday-evening outage drill with staff. These two routines surface problems before customers do.
Staff troubleshooting flow: what to do when the POS fails
Give this to every member of front-of-house staff. It works under pressure because it is ordered and short.
- Check the obvious first. Are all cables plugged in? Are the power lights on? Is the router showing a connection?
- Check the network. Run a speed test on your phone using the shop Wi-Fi. If it fails, the issue is connectivity, not the EPOS.
- Restart the terminal. Full power off, wait 30 seconds, power on. This resolves a large share of software freezes and card reader pairing issues.
- Restart the card reader. Re-pair it to the terminal if needed. Check the card reader’s own status screen for error codes.
- Check the receipt printer. Paper jam? Cable loose? Out of paper? These are the three most common printer failures.
- Switch to offline mode if your terminal supports it and payments are failing.
- Log the fault. Time, error code, last transaction, what you were doing. This takes 60 seconds and saves 20 minutes of vendor diagnosis.
- Call the duty manager. Do not attempt further fixes beyond this point without authorisation.
- Duty manager calls vendor support. Have the incident log open when you dial.
Escalate immediately (skip to step 8) if: payment processing is completely down, the full system is unresponsive, the KDS is offline during service, or you suspect a security breach.
Pro Tip: Log the vendor’s case reference number the moment you call. If the issue is not resolved within the agreed SLA window, that reference is your evidence when requesting a service credit. Keep a dedicated notebook at the till for incident logs — a physical record is faster to hand to an engineer than scrolling through a phone.
What does POS support actually cost in the UK?
Support costs vary widely depending on what you are buying. Here is a realistic picture of the UK market in three bands.
- Budget (reactive only): No monthly fee, but you pay per call-out or per hour. Response times are typically next business day for non-critical issues. Fine for very low-volume businesses, but a single Saturday outage can cost more than a year of managed support.
- Mid-market (managed support, standard hours): Typically £30–£80 per month per site. Covers phone support during business hours, remote diagnostics, and scheduled maintenance. Response times of one to four hours for P1 incidents during covered hours.
- Premium (24/7 managed monitoring): Typically £80–£200+ per month per site. Includes out-of-hours cover, proactive monitoring, on-site engineer SLAs, and hardware replacement. The right choice for any hospitality or retail business trading evenings and weekends.
The cost-benefit case is straightforward. A busy restaurant or retail shop turning over £2,000–£5,000 on a Saturday evening loses that entire amount if the EPOS goes down and the vendor does not answer until Monday. A premium support contract at £150 per month pays for itself in a single prevented outage.
A claimed four-hour on-site response is meaningless if the nearest engineer is three hours away. Always ask for the engineer’s base location, not just the headline SLA figure.
How staff communicate during POS issues: the skills that matter
Technical fixes and communication skills are equally important. A staff member who handles a card failure calmly and clearly protects your reputation as much as the engineer who fixes it.
Three communication principles make the biggest difference. First, acknowledge the problem immediately and without blame — “We’re aware of an issue with the card machine” is better than silence or a shrug. Second, give a realistic timeframe: “We expect it back in two to three minutes” sets expectations and reduces frustration. Third, offer an alternative before the customer asks — cash, a different payment method, or a short wait. Customers who feel looked after during a failure often leave with a better impression than customers who had a flawless transaction.
For managers, the skill is slightly different: it is about staying visibly calm. Staff take their cue from the duty manager. If the manager looks panicked, the whole floor feels it. A short, confident briefing to staff (“Card machine is down, we’re on offline mode, keep smiling”) takes ten seconds and steadies the room.
POS-related customer interactions also benefit from a brief post-incident debrief. Ask staff: what worked, what felt awkward, what would you say differently? That feedback loop improves scripts faster than any training manual.
Data security and privacy during POS support and troubleshooting
POS systems handle payment card data, personal information, and transaction records. Any support or troubleshooting session is a potential security event if not handled carefully.
Never allow a vendor or engineer to access your system via an unverified link, a personal email, or a tool you have not approved in advance. Legitimate support access uses named, encrypted remote-desktop tools with session logging. Ask your vendor to confirm their remote-access method before you grant any connection.
During a troubleshooting session, do not share card numbers, PIN entry logs, or customer personal data verbally or via screenshot. If an engineer asks for this information, that is a red flag. Your EPOS system should never store full card numbers in the first place — if yours does, raise it with your vendor immediately.
After any support session, change your admin passwords. This is a simple step that most businesses skip. Also confirm with your vendor that no remote access session remains open after the issue is resolved. UK businesses handling card payments are subject to PCI DSS (Payment Card Industry Data Security Standard) requirements, and a poorly managed support session can create a compliance gap. If you are unsure of your current PCI DSS status, your payment processor can advise.
Key takeaways
Good POS support comes down to preparation: a tested checklist, trained staff, a vendor who actually answers at peak hours, and a few physical spares behind the counter.
| Point | Details |
|---|---|
| Pre-call checklist saves time | Run restart, cable, and network checks before calling support — most faults resolve without a call. |
| SLAs must match trading hours | P1 response targets should be measured in minutes; “next business day” is not acceptable for evening or weekend trading. |
| Test your vendor before you need them | Call your support line at 20:00 on a Saturday to confirm a human answers — not voicemail. |
| Redundancy prevents total outages | Keep a spare card reader, cash float, and backup network dongle on-site and test them monthly. |
| Switch-and-save provides UK-based support | Switch-and-save’s EPOS systems include UK-based technical support matched to retail and hospitality trading hours. |
Why fast POS support is a business-critical issue, not just an IT one
There is a tendency in small retail and hospitality businesses to treat POS support as a back-office concern — something to sort out after the shift. That framing is expensive. A Saturday-evening outage during your busiest trading window is not an IT problem; it is a revenue and reputation problem that plays out in front of your customers in real time.
UK retail and hospitality trading is heavily concentrated in evenings and weekends. A support contract that only covers Monday to Friday, 9 AM to 5 PM, leaves your most valuable trading hours completely unprotected. The businesses I see handle this well share one habit: they treat their support contract with the same seriousness as their lease or their insurance. They read the SLA, they test the line, and they know exactly who to call at 8 PM on a bank holiday.
Good support also reduces staff strain in a way that is easy to underestimate. When staff know there is a clear process and a reliable number to call, they stay calm. When they do not, a card machine going down for five minutes can feel like a crisis. That calm is worth something — both to your team and to every customer watching how you handle it.
Switch-and-save: EPOS systems built for UK trading hours
Downtime during your busiest hours is the real cost of a poorly supported EPOS system. Switch-and-save provides AI-powered EPOS systems designed specifically for UK retail and hospitality businesses, with UK-based technical support that matches your actual trading hours — not a 9-to-5 helpdesk that leaves you stranded on a Saturday night.
Every Switch-and-save system includes cloud-based remote access for faster diagnosis, real-time sales and inventory visibility, and hardware bundles that make spare-parts planning straightforward. Whether you run a single café or a multi-site retail operation, the SSPOS software gives your team the tools to stay trading even when something goes wrong.
Book a free demo or get a quote today at switch-and-save.uk and see how the right system and the right support make a measurable difference to your business.
Useful sources and further reading
- Why payment systems keep breaking in UK shops and what actually fixes it — practical pre-call troubleshooting and cash-float guidance
- EPOS Support for UK Restaurants 2026 — CloudMatters — SLA benchmarks, contract questions, and out-of-hours support validation
- 24/7 Restaurant IT Support: The Case for Always-On — Cardonet — proactive monitoring and the cost-benefit case for managed support
- UK retailers face frontline tech friction — IT Brief — data on real-time visibility gaps and connectivity issues
- EPOS customer service review UK — Smart Pub Tools — operator perspectives on phone support vs email/chat
- How to train staff on a new POS system — Switch-and-save — drill frameworks and onboarding guides
- What happens when an EPOS system goes down — Switch-and-save — outage impact and operational response
- POS hardware setup guide for UK retail and hospitality — Switch-and-save — spare-parts planning and hardware setup
FAQ
What should staff do first when the POS stops working?
Run the pre-call checklist: check cables and power, restart the terminal and card reader, and test the internet connection. Most faults resolve at this stage without a support call.
What are the 5 P’s of customer service?
Definitions vary across sources, but a widely used version covers: People, Process, Product, Place, and Promotion. In a POS support context, People (trained staff) and Process (clear SOPs and escalation paths) are the two that most directly reduce downtime and customer friction.
What does a good POS support SLA look like for UK hospitality?
P1 incidents (full outage, payment failure) should carry a response target of 15 minutes and resolution within two hours. “Next business day” is not a viable SLA for any business trading evenings or weekends.
How do you verify that a vendor’s 24/7 support is genuine?
Call the support line at 20:00 on a Saturday. If you reach voicemail or an automated system with no human callback within 15 minutes, the advertised 24/7 cover is not credible. Ask the vendor for their out-of-hours rota before signing any contract.
What security steps should you take after a POS support session?
Change your admin passwords immediately after any remote-access session, confirm the engineer has closed their connection, and check that no full card numbers or personal data were shared during the session. UK businesses processing card payments must comply with PCI DSS requirements.
