What an EPOS integration actually is

The short version

An EPOS integration is a link between your till and another system, so that information you’d otherwise have to type in twice moves across on its own. A card payment settles on the terminal and shows as paid on the till. A booking made online lands on the right table without a phone call. A sale nets off against stock or a set of accounts without anyone touching a spreadsheet. That’s it — no new dashboard to learn, no second till on the counter, just two systems that already talk to each other.

What it replaces

Before an integration exists, the two systems simply don’t know about each other. A card machine takes the payment; the till records the sale as a separate, unconnected event, and someone reconciles the two by hand at the end of the night. A hotel PMS holds the room and rate; the till has no idea a guest wants their bar tab on room 14 until someone walks over and asks. A delivery app takes the order; someone in the kitchen re-types it onto the till, misses an allergen note, and the ticket prints five minutes late. None of this is broken exactly — it’s manual, and manual work is where mistakes and delays creep in on a busy Friday night.

The kinds of integration you’ll actually meet

Most EPOS integrations fall into a handful of categories, and ICRTouch — the till software we fit most often — organises its own integration partners the same way:

• Payments: card terminals and payment providers that settle a transaction and pass the result back to the till, so the payment and the sale are one record, not two.
• Property management (PMS): hotel and venue booking software that lets a guest charge a bar or restaurant bill straight to their room instead of paying twice.
• Accounting: cloud accounting packages that pull sales and payment totals in automatically instead of someone keying in a Z-read every morning.
• Delivery and online ordering: platforms such as Deliveroo, or your own webshop, where an order placed online lands directly on the till and in the kitchen, with the menu kept in sync from one place.
• Staff management: rota and time-and-attendance tools that use real sales data to plan the next shift, rather than guessing.

Each of these exists because a business asked for it. ICRTouch alone lists dozens of named partners across these categories, and the list keeps growing as new systems become worth connecting.

How the connection actually works

Underneath, an integration is usually one of three things: the two systems exchanging small messages over the internet as things happen, the till periodically checking in and asking “anything new?”, or one system dropping a file that the other picks up on a schedule. Which one fits depends on how urgent the information is and how the two systems were built — we cover that choice properly in our article on webhooks, polling and file drops. For most day-to-day purposes you don’t need to know which mechanism sits behind a given link; you just need to know it’s there, it’s been tested, and it keeps working after the person who installed it has gone home.

Off-the-shelf, or built to order

Some integrations are already built and just need switching on — a payment provider your EPOS software already supports, or an accounting package with a ready-made link. Others don’t exist yet, because your combination of systems is less common, or because you want the connection to behave slightly differently from the standard version. That’s when it gets built specifically for you rather than picked off a shelf. We write about how that build actually happens, and why AI coding agents have changed what a small integrator can take on, in our article on AI coding agents and small integrators. Where ICRTouch is the till software in question, its own developer interfaces — the XML socket interface, the JSON remote interface, and the ETAL scripting engine — are usually where that custom work happens; we go through what each of those actually is in our ICRTouch developer interfaces article.

What to ask before you rely on one

If someone tells you an integration “exists”, it’s worth asking a few follow-up questions. Does it exist for the exact product you’re buying, or an older version? Is it actively maintained, or was it built once and left? What happens when the other system changes its own software — does the link keep working, or does someone need to fix it? A working integration isn’t just code that ran once; it’s something that keeps working as both sides of it change, which is as much about ongoing support as it is about the initial build.

Where this fits at RED EPOS

We fit and support ICRTouch, CES Software, Oxhoo and Aures, and we build the integrations that join a till to whatever else a business runs on — payments, PMS, delivery, accounting or a webshop. Some of that is switching on a link that already exists; some of it is custom work, written and tested against your own setup before it goes live. See the systems we already connect to on our integrations and AI page, or browse them directly in the integrations directory.

Sources

• ICRTouch, “Webshops” integration category
• ICRTouch, “Payment Solutions” integration category
• ICRTouch, “Accounting” integration category
• ICRTouch, “Property Management” integration category
• ICRTouch, “Staff Management” integration category