Integration · Zonal
Zonal EPOS integration for UK restaurant and pub groups
Connect Zonal EPOS to your ordering app, master menu, loyalty and group reports. Zonal opens its API only for projects with a shared customer, so access starts with you.
Takes two minutes. An engineer reads it, and Max replies within 1 business day.
- API
- iOrder, table service, loyalty APIs
- Access
- Shared customer project only
- Docs
- Not public
- Market
- UK, 16,000+ businesses
In short
A Zonal integration connects Zonal EPOS to ordering apps, delivery, loyalty and reporting. Zonal has no public developer portal: it opens API access only for a project with a shared customer, through its Integrate with Zonal form. Through iOrder, integrators read menus, inject orders and run pay at table; loyalty has its own APIs. Your Zonal account manager enables access. dev.family builds and runs EPOS connectors for UK groups under an SLA.
What data moves
What a Zonal integration moves
Read means we can get it from Zonal. Write means we can send it to Zonal. From integrator documentation; Zonal's own reference is not public.
| Object | Read | Write | What the API supports |
|---|---|---|---|
| Menus, prices, modifiers | Yes | No | Through iOrder, including availability |
| Orders | No | Yes | Order injection into the EPOS through iOrder |
| Pay at table | Yes | Yes | Bill sync and split payments through the table service API |
| Loyalty | Yes | Yes | Zonal calls the partner connector; needs Aztec 3.33 and POSint 1.58 or later |
| Stock | No | No | No real-time stock through iOrder |
| Sales and labor reporting | No | No | No reporting or labor API found in public sources |
Common setups
How UK groups connect Zonal
Order at table
Your appZonalBar and kitchenGuests order and pay from their phone; the order lands in Zonal like a till order.
Delivery into Zonal
Delivery app orders reach the EPOS through a partner integration or middleware.
Group reports
After an acquisition, sites on Zonal and on another EPOS report into one warehouse.
API access
How Zonal API access works
Zonal grants integration and API access only for shared customer projects. The partner applies through the Integrate with Zonal form and names the Zonal customer. In practice, the operator's Zonal account manager switches on iOrder access and agrees the commercial terms.
So for a group, the request comes from you. We prepare the scope and the technical questions, and you raise them with your account manager.
Docs zonal.co.uk/integrations · no public API reference · checked November 9, 2026
What we need from you
- An introduction to your Zonal account manager
- Your Aztec and POSint versions
- Which sites, brands and menus to connect
- A test site
Getting access:
depends on your account manager; Zonal publishes no timeline.
Platform limits
Where Zonal integrations break
No public docs. The API reference isn't public, so scoping depends on what Zonal shares for your project. Budget time for questions.
Version minimums. Loyalty integrations need Aztec 3.33 and POSint 1.58 or later. Older sites need an upgrade first.
No live stock. iOrder doesn't give real-time stock, and payments taken on the terminal aren't tracked through it. Sold-out items need another source.
Commercials per operator. API access is agreed per customer, so each new operator in a group may mean a new conversation with Zonal.
Run
Who fixes it when the platform changes its API
Monitoring
We check the connector against the live API every day and log every failed call.
Versions
We track the platform's changelog and move the connector to a new version before the old one is retired.
Alerts
Lost or stuck orders page the on-call engineer, who fixes them under the SLA.
Questions
Didn't find your answer? Ask on the call.
Zonal doesn't publish an open developer portal. It gives API access for projects with a shared customer: you apply through its Integrate with Zonal form and name the Zonal customer you're working with. Zonal says it has more than 200 technology partners.
Through Zonal's iOrder API, integrators read menus with prices, modifiers and availability, inject orders into the EPOS and run pay at table with bill sync and split payments. Loyalty runs through Zonal's loyalty APIs. Real-time stock isn't available through iOrder, according to integrators.
The operator's Zonal account manager enables iOrder access and agrees the commercial terms. The credentials are a brand token and a device identifier, plus a signing secret for table service.
Zonal publishes no timeline, and we found no sourced market estimate. Access is the slow part: it runs through your account manager. We fix the price per scope once we know what your contract allows.
Yes, through Zonal's partner integrations or middleware. For a group, the work is keeping menus and sold-out items the same on every app and at the bar.
Yes. Our Lisbon workday matches UK hours, and contracts and data processing run under EU rules.
Get a scope estimate for your Zonal integration
Tell us how many sites run Zonal, which versions and what they need to talk to. An engineer will reply with the questions for your account manager and a rough timeline.
a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work
Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors
Max will reply within 1 business day with what's possible, what access we need and a rough timeline.