Use Cases
How CNX Connects Restaurant Systems
How CNX connects restaurant systems you already run. Source records, workflows, and connection proof stay separate. A link to your ordering tool is part of the Business Partnership plan.
We do not ask you to rip out the POS or ordering rails that already take tickets. Those products stay with their vendors. Where a link makes sense, we can build it so your operator isn't the integration.
Work with what you already use
Discovery names the systems, fields, and workflows for your engagement. Your POS, ordering tools, reservations, loyalty and supplier data stay where they are.
Square, Toast, Clover and Olo all give us a way in; so do most ordering tools. Connecting your tools is part of the Business Partnership plan.* Whether a link is possible is confirmed in discovery, not promised for every setup. A few tools only open up through their own partner programmes, and we say so before you pay.
* Some tools take longer and need a workaround. Connecting your tools is part of the Business Partnership plan. Tool names belong to their owners; naming one means we can work with it, not that they endorse or certify us. See what we connect.
Three things that must stay distinct
Restaurant operations fail quietly when these three get collapsed into one “it synced” label.
Source record
The invoice, ticket, reservation, campaign draft, or guest note that started the work. Saving it in one system is a fact about that system.
Workflow
The decision path: who reviews the options, what may change, which destinations are in scope, and which approval rules apply. A workflow can prepare a price change, a guest-facing send, or a supplier award without having executed it.
Connection proof
Evidence that a named destination actually accepted the chosen fields—or that it returned an exception.
A saved source record is not proof that another system changed. Each destination is checked on its own. Success or an exception is recorded for that connection.
What exists where
| Layer | What it is | What it is not |
|---|---|---|
| Source | The record in the system that originated the fact | Proof that a POS, menu, or channel updated |
| Workflow | The operator path from signal to approved action | A universal connector |
| Connection proof | Per-destination success or exception | A single “synced” badge for every system |
Where we build a link, expert humans set it up and run it. Your GM is not the integration team. The point is one decision path—not another login to reconcile.
Ownership after we build
CNX owns the CNX platform. You own the customer-specific systems and assets we agree to build and transfer—menus, workflows, automations, and guest records. Your POS, marketplace, and ordering vendors still own their products. Third-party accounts stay in your name. Your agreement defines export, hosting, and the transfer boundary.
DoorDash, Uber Eats and Owner.com each offer restaurants their own branded ordering site and app for repeat orders. How is what you build different, and does it work with them?
We can't speak for their packages, so here is what we do. It starts with a strong foundation: a brand worth remembering, photos worth showing, a fast site on current technology, and ordering your guests enjoy using. Then we connect that site and app to any delivery app or ordering tool you use or want to use. It is not either/or. Your repeat guests sign in to your own site and app, with an account that's yours.
We are an Olo developer and partner. An order placed on your own site can hand off to a delivery app through Olo, and Square, Toast and Clover all give us a way in. US Egg runs this today: a loyalty program with guest logins, a digital menu, an HR system, managed advertising and managed technology support, all built for them. The website and the menu are the Foundation plan; loyalty and the delivery and POS links are part of the Business Partnership plan. We charge no fee of our own per order.
Related
- Restaurant Marketing Excellence — Campaigns tied to visits and orders, with operator approval.
- Connected Spaces for Hospitality — The longer hospitality picture.
- What Is Build-to-Own? — What transfers, and what stays the CNX platform.
- Your Restaurant Systems. Connected. — The restaurant landing page: operate, market, and guests.