ICRTouch developer API
The starting point for most of our work. Sales, products and stock out of TouchPoint and TouchOffice Web, in a shape another system can read.
Custom EPOS integrations, built fast with AI coding agents
If your till and your other systems do not talk to each other, somebody is typing the same numbers in twice. We write the bit in the middle, and AI coding agents have made that a job a small UK integrator can now take on.
How your till connects to everything else
A small piece of software that sits between your till and something else, translates between them, and keeps going when one of them changes.
What an integration actually is
A small piece of software that sits between your till and something else, translates between them, and keeps going when one of them changes. That is it. The work is in knowing what both sides expect, and in handling the days when one of them is down — the card network is slow, the PMS is offline, the delivery platform changes its order format without warning.
Integration families
We build and support integrations across seven families. Each one links through to the directory, filtered to that category.
Payments
Pin pads and card readers that take the amount from the sale and send the result back, so the cash-up matches the card report.
PMS and hotel systems
Room charges from the bar and the restaurant, posted to the right folio with the right tax treatment.
Delivery platforms
Third-party orders arriving as normal orders, in the kitchen queue and in the reports.
Accounting
Nightly journals into the package your bookkeeper already uses, in their chart of accounts and not ours.
Webshops
One stock figure across the counter and the website, instead of two numbers that drift apart.
Loyalty
Points and vouchers recognised at the till, rather than on a separate reader or a paper card.
How we build one
01
Discovery
We sit with both systems and find out what each one can actually give and take. Most of the surprises live here, not in the code.
02
Spec
A short written spec: the fields that move, what happens on failure, and what you will see when it works.
03
Build with AI coding agents
The agents draft the bulk of the connector and its tests from the spec. It is fast, and it is not magic — it still needs a spec to work from and a person to judge the result.
04
We check it line by line
We read the code ourselves, especially anything touching money, tax or personal data. Nothing goes live because a machine said it was fine.
05
Test on your data
A copy of your real menu and real transactions run through it before it goes anywhere near a live service.
06
Deploy and support
We put it live, watch it through the first week, and it comes under the same support arrangement as the rest of your system.
Why a small UK integrator can do this now
Bespoke integration work used to be priced out of reach for a single pub or a two-site group, because writing a connector from scratch was slow, specialist work. AI coding agents have changed that arithmetic: the agent reads both systems' APIs, drafts the connector and the test suite, and we spend our time on the part that actually needs judgement — what should happen when the PMS is down, how a refund reverses on both sides, whether the tax lands right.
We are not claiming the machine does the job. We are saying the routine part of it now goes much faster, which is why we can quote for integration work we would have turned down a few years ago.
Talk to us about your setup
Tell us the two systems you want joined up and we will tell you whether it is a day, a week, or not possible, before you spend anything.