ZADENO: Designing an Offline-First Restaurant POS, Kitchen Display, and Delivery Architecture
How we architected ZADENO's point-of-sale, kitchen display, and delivery-dispatch system to keep working through a real connectivity drop — because a restaurant's front counter cannot stop taking orders because the internet did.
The Challenge
Most restaurant POS platforms today are cloud-first: the register, the kitchen screen, and the delivery tracker all depend on a live internet connection to function. That is a real operational risk for a restaurant on a weak or shared connection — the counter cannot simply stop selling because the connection dropped. We designed ZADENO around the opposite assumption: the terminal has to keep working offline, and sync when connectivity returns, not the other way around.
Architecture
ZADENO separates into distinct layers — Core, Data, Services, Desktop, a Local API, and a Remote sync layer — so that the point-of-sale terminal and kitchen display run against a local data store first, with the Local API handling day-to-day operation on the restaurant's own network regardless of whether the wider internet is up. The Remote layer handles licensing, cross-branch synchronization, and centralized management once connectivity is available, without blocking the counter from operating in the meantime.
What We Built
- Point of sale: a fast, offline-first terminal built for a busy front-of-house counter.
- Kitchen display system (KDS): real-time screens that route orders straight to the correct station as they're placed.
- Delivery and dispatch tracking: built in from order to doorstep, not bolted on as a separate app.
- Desktop and mobile companion devices: the same system runs on fixed terminals and on mobile devices for staff working the floor.
- Per-branch licensing with centralized management: each branch activates its own license, while a multi-branch operator manages all of them centrally.
Outcome
The result is a system a restaurant can run entirely on its own local network if it has to, with the cloud layer adding convenience — centralized reporting, multi-branch management, licensing — on top rather than acting as a single point of failure for taking an order. ZADENO's licensing runs on the same infrastructure Zetraxa built for its own multi-tenant platform.