Integrations
Nexora reads what you already run. It does not ask you to replace it.
It is not a point of sale, not a payroll provider and not a general-ledger accounting package. It sits between them: reading the POS, pricing the rota against it, reconciling purchases and expenses, and handing approved hours onward to payroll.
Point of sale — the one that matters
Everything downstream depends on this connection. Sales, orders, item mix and clocked hours arrive from the POS, per store, per day; sales per labour hour and cost per order are computed from it directly. Nexora asks nobody to key those figures in.
| System | What it carries | Status |
|---|---|---|
| PAR | Sales, orders, item mix, clocked hours and the POS employee list — the connection running the live twelve-store pilot deployment | Certified |
| Any POS that exports sales and timeclock data | The same fields, confirmed against your system before you commit to anything | On request |
The test is capability rather than brand. If your point of sale can export sales and timeclock data, we can connect it — but we will confirm it in writing before you commit, because we would rather decline a system we have not connected than discover it in week three of your onboarding.
Two point-of-sale systems across an estate — common after an acquisition, or where a franchisor changed systems mid-contract — is a materially different implementation from one. The definitions have to be reconciled before a store comparison means anything. It is the largest single variable in scoping, and it is the one most often left out of the first conversation.
The rest of the stack
Connected once under Settings → Admin → Integrations. Each carries a specific, narrow thing rather than general access.
| Connection | What it carries | Direction | Status |
|---|---|---|---|
| Slack | Shift notifications and schedule updates into channels | Nexora → Slack | Connected |
| Google Calendar | Published shifts into employees' personal calendars | Nexora → Calendar | Available |
| QuickBooks | Approved timesheets and labour cost into payroll | Nexora → QuickBooks | Available |
| Google Business Profile | Reviews and replies, per store, in one inbox | Read and reply only | Available |
| Snowflake | Warehouse sync for reporting and analytics | Nexora → warehouse | Coming soon |
| API keys | Connecting an external tool or a custom script to the account | Both | Settings → Developer |
What each connection is deliberately not
Reviews are read-and-reply only
Each location's Google Business Profile is connected once, per store. Nexora cannot delete a listing, transfer it, or change who has access to it — and it can be disconnected at any time from either side. A marketing platform that can lock you out of your own listing is a risk most operators only discover once.
Payroll gets approved hours, not raw hours
What flows to QuickBooks is approved timesheets and the labour cost derived from them. Nexora does not run payroll, does not hold tax registrations, and does not become the system of record for what someone is paid. It is the layer that gets the hours right before payroll prices them.
Expenses are proposed, never posted
Uploaded bank statements are read line by line and proposed as expenses. Lines the extractor is unsure of are held pending for a human to approve, reject or reclassify. Nothing posts itself into your books, which is the only version of automated bookkeeping an accountant will actually accept.
Ledgers are kept separate on purpose
Store-level expense entries, cost of goods, operating expenses and the documents queue are deliberately distinct ledgers, so a supplier invoice cannot be counted once as COGS and again as an operating expense. Double-counting is the most common way a restaurant P&L quietly stops reconciling.
What a connection changes in week one
Connecting the POS is not the finish line — it is what makes the real setup task visible. The point of sale knows every person who has clocked in. Your roster knows every person you employ. The two lists are never identical.
Rather than pricing unmapped hours at an assumed rate, Nexora leaves them out and says so on the page. That is why coverage is a headline number in the product rather than a footnote: below 100%, every labour ratio you look at reads lower than reality — and nobody investigates a good number.
Integration questions worth asking
How often does data refresh from the POS?
On your point of sale's own reporting cadence. Nexora reads what the POS publishes and cannot report faster than the source produces — and does not pretend to. Separately, the dashboard's Live · right now block reports the floor as it currently stands and ignores whatever date range you have selected. Yesterday closed is there in the morning; today's floor is there all day.
Do we have to change our payroll provider?
No. Nexora gets the hours right and hands them on. Most groups keep their payroll provider and their accountant — the monthly close becomes a confirmation rather than a revelation.
What if we change POS next year?
Ask this before you buy anything in this category, including us. The honest answer is that a POS migration is a reconnection and a re-mapping, and how painful it is depends on whether the new system exports the same fields. Tell us if a change is already on the table; it affects what we would recommend you do first.
Can we pull everything out programmatically?
Yes — API keys are issued under Settings → Developer. The product is explicit that most customers never need one, and reports export to Excel and PDF without it.
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