About Nexora
What Nexora is, what it is not, and what is actually finished.
Nexora is a restaurant operating platform for people who run more than one restaurant. It is not a scheduler with reports bolted on, and not an accounting package with a rota bolted on. It is one system where the schedule you build, the staff you hire, the stock you buy and the money the tills take are the same data.
In one paragraph
Nexora joins the point of sale, the rota, the purchase ledger and the accounting feed into a single set of books — so a multi-unit operator can see what a shift costs while it is still running, not three weeks after the month closes. Everything in the product is scoped to a store or a set of stores, and every figure it shows is either measured or clearly labelled as planned. That distinction runs through the whole interface: ACT for what actually happened, PLAN for what was scheduled or budgeted. Nothing is silently estimated.
Why it exists
A restaurant group's two largest controllable costs are food and labour. Added together and divided by net sales they give prime cost — the one ratio that most reliably decides whether a location makes money. Most operators learn theirs when the accountant closes the month, roughly three weeks after the period it describes. By then every shift in it has been worked and every case of chicken has been used.
And the gap that costs the most is not between a good month and a bad one. It is between stores. Across the live pilot estate in August 2026, the best location ran a prime cost of 23.60% and the worst ran 75.84% — both trading under the same brand, the same menu and the same suppliers, eleven miles apart.
Where the numbers come from
Nexora does not ask anyone to key in the figures it reports on. Its job is to reconcile three inputs against the plan you set.
Point of sale
Sales, orders, item mix and clocked hours, per store per day. Sales per labour hour and cost per order are computed from it directly.
Purchase & expense ledger
Supplier order history for stock, plus an expense log and an accounting feed for rent, utilities, insurance, payroll and fees.
Your plan
The rota you build and the labour budget you allocate — the PLAN side that actuals are measured against.
Where it is honest about gaps. In the pilot estate, labour cost covered 67.9% of hours worked — 6,043 hours in the period carried no POS cost, because those employees were not yet mapped to a Nexora record. Rather than pricing those hours at an assumed rate, the platform leaves them out and says so on the page. Linking a POS employee is a one-time action that applies retrospectively to every hour they have ever worked.
What Nexora is not
| Not this | What it does instead |
|---|---|
| A point-of-sale system | It reads your existing POS. PAR is certified today; other systems that export sales and timeclock data are connected on request. |
| A payroll provider | It hands approved timesheets and labour cost to payroll — QuickBooks today. It holds no tax registrations and does not decide what anyone is paid. |
| A general-ledger accounting package | It produces a store-level P&L from POS sales and expense data. Most customers keep their accountant; the monthly close becomes a confirmation rather than a revelation. |
| A scheduling tool with reports attached | The rota is priced against the same data the P&L is built from, which is what makes a labour percentage true rather than defensible. |
| A finished product | Live and in active use across a real multi-store deployment. New capability ships on an ongoing basis, and anything not yet live is marked as such in the product itself rather than hidden. |
Who it is built for
Multi-unit restaurant operators, from three locations to three thousand: owner-operators, multi-unit directors, franchisees, franchise groups and restaurant CFOs. Three altitudes of access, each seeing the same system scoped to what they are accountable for.
| Role | Scope | Primary work | Financial visibility |
|---|---|---|---|
| Executive · CEO · CFO | Global — all stores | Fleet-wide monitoring, global reporting, configuration strategy | Full: net sales, prime cost, COGS, wage rates, budget variances |
| Multi-Unit · Area Manager | Assigned region | Cross-store rota creation, shift approvals, POS unlinked mapping | Operational: labour costs, hourly rates, overtime metrics |
| Store General Manager | Single store | Local schedule building, daily clock-in reconciliation, live shift monitoring | Store level: store labour totals, schedule budget versus actual |
Honest status — what is live and what is coming
Dashboard · Schedule · Team · Inventory · Reviews · P&L · Expenses · Planning · Reports · Scheduled Reports · Corporate Library · NexAI · Command Center · Settings
Attendance · Time Off · Onboarding · Equipment & IoT · Food Safety · Required Actions · Insights · Benchmarking · Forecasting
We publish this list because a buyer who reads P&Ls for a living will find it anyway, and finding it themselves in week three costs more than reading it here in week zero. If a coming-soon module is the reason you are looking, say so on the call and you will get the honest timeline rather than the hopeful one — including when the answer is that you should buy something else this year.
How every headline figure is defined
Operators compare across systems, and a prime cost that quietly includes operating expenses is not the same number as one that does not. Every ratio in the product is stated with its formula.
| Measure | Definition | Target |
|---|---|---|
| Prime cost % | (COGS + labour cost) ÷ net sales × 100. Food and labour only — operating expenses excluded. | Under 65% |
| Labour % | Reported labour cost ÷ net sales. Covers only hours the POS put a cost against. | 25–30% |
| Food cost % | COGS ÷ net sales. | By format |
| Sales per labour hour | Net sales ÷ hours worked. | Higher is better |
| Labour cost coverage | Costed hours ÷ total hours worked. Below 100% means unmapped POS employees. | 100% |
| Planned labour cost | The scheduled rota priced out at each employee's rate. | Within budget |
| Actual labour cost | What the POS reported, for hours it costed. Uncosted hours are excluded, not estimated. | — |
| Schedule health | Weighted toward overtime risk, with deductions shown per store rather than only the total. | Grade A |
About the figures on this site
Every pilot figure published across this site is read from the live product for the period stated — principally 1–31 August 2026 across twelve stores. They are a snapshot: POS and expense data continued to land during the period, so the same measure captured a few days apart will differ. Where a store shows 0.00% labour or an unbalanced balance sheet, that is the real state of the data, not a rendering error — and it is exactly what the platform is designed to surface. No customer result is published on this site without a named customer who has approved it in writing.
Bring your worst-performing store
Twenty minutes, your own POS data, no deck. If we cannot show you something you did not already know, we will say so and leave.
Book a 20-minute demo