from kickoff to first live location
active locations since January
of in-house development avoided plus permanent maintenance
WHO
NX is a restaurant POS platform built for operators who want the power of an enterprise system without the enterprise headache — front counter to back office, ordering, kitchen display, scheduling, and reporting in one place. NX goes to market through a network of resellers who know their local restaurants by name, and that channel is central to the company. Partners are in the restaurants, and they grow with them.
WHAT
NX needed DoorDash, Uber Eats, and Grubhub available natively inside its platform, so that operators and resellers could switch delivery on without leaving the system they already use every day. Building those connections in-house was estimated at roughly six months and never fully scoped, because not all delivery providers allow direct integrations. The ceiling on a build-it-ourselves approach was lower than it looks from the outside.
WHY
Delivery is a core part of how restaurants operate now, not a side channel. Operators were already doing the volume — they just had no good way to control it. And the build was never the real cost: the maintenance is. Every delivery platform changes on its own schedule, and NX didn't want that permanent burden sitting on an engineering team that should be building the things only NX can build.
NX partnered with KitchenHub to deliver DoorDash, Uber Eats, and Grubhub as a native part of the NX platform. Setup and ongoing management happen directly in the NX portal — no separate dashboard, no parallel login, nothing new for a reseller to learn. Menus, prices, stock status, and orders sync in both directions, and KitchenHub absorbs every API change the delivery platforms make.
The integration was completed in January. Test locations were running in a matter of weeks, and the first live location went into production about a month from the start of the project.
Resellers and operators enable and manage delivery inside the system they already use every day. That part is key: no one has to adopt a second tool to turn delivery on.
Price changes and out-of-stock items sync instantly across every platform. When a restaurant 86s an item, it's 86'd everywhere. When they change a price, they change it once.
KitchenHub owns the connections to each delivery platform, so NX engineering stays focused on the product only NX can build.
NX and KitchenHub mapped the delivery requirements against the NX portal architecture, defining how setup and management would live inside the existing NX experience.
KitchenHub adapted its APIs to NX's specifications so that menus, pricing, stock status, and order flow would sync natively, with no separate interface for operators or resellers.
Test locations were running within weeks. Menu accuracy, order routing, and real-time 86 sync were verified before production rollout.
Resellers began switching delivery on for their own customers, location by location. NX went from zero in January to 29 active locations, with a steady few coming online every month.
Stacks of tablets at the expo window — one for every delivery platform
A separate menu to maintain on each platform, with no single source of truth
Orders keyed in by hand, with misses and errors accepted as the cost of doing delivery
Price changes and 86'd items updated one platform at a time
Reseller partners carrying setup and support load for every delivery channel
Six-plus months of in-house development — and permanent maintenance — on the engineering roadmap
Our operators were already doing the delivery volume — they just had no good way to control it. Now they light those channels up from inside the system they use every day, and after that there's very little left to do. Our resellers feel it too: setup and support used to land on them, and now it doesn't.
