Built for restaurants. Designed to grow with your business.

It is built to work at both ends and to grow with you in between. A single independent restaurant uses the same core — tills, orders, payments, stock and reporting — without the multi-site machinery getting in the way. As you add locations, the estate-level features (rolled-up reporting, central menus, role-based access across sites) become available without moving you onto a different product or re-platforming. The design goal is that the system you start on is the system you scale on, so ask us to walk through what your first site looks like and what changes when you open the second.

Onboarding time depends on how much menu, hardware and integration work your setup involves — a single site with a straightforward menu is a very different job from migrating an estate with existing integrations. Enterprise customers get a named customer success manager who works through data migration, hardware, staff training and go-live with you. Rather than quote a number here, the honest answer is that we scope it with you up front so you know the timeline before you commit. Ask for an onboarding plan for your specific number of sites and menu size.

Plans start from $49/mo, and the exact price depends on which modules and how many locations you run — the pricing page has the current plan breakdown, and payment processing is quoted separately because rates vary by region and volume. “Everything included” on the marketing pages refers to Vertex shipping the core modules in one platform rather than selling each as a separate add-on; it is not a promise that every enterprise feature or third-party fee is free. For a firm figure covering your outlets and the modules you need, see the pricing page or ask sales for a written quote.

Often, yes — Vertex offers a documented API, webhooks and integrations so it can sit alongside systems you already run rather than forcing a rip-and-replace, and it supports enterprise-grade hardware. Whether a specific integration or a particular piece of equipment you already own is supported is a scoping question, because the answer depends on the third party and the version involved. Bring your current stack and hardware list to our team and we will tell you what connects directly, what needs the API, and what would need to change — in writing, before you decide.