Orqestra for Clover
A reporting and operations app for Clover POS
Clover's dashboard tells you what sold. Orqestra connects to the same account and adds the reports and tools Clover does not have: P&L with prime cost, ingredient inventory that follows every order, expenses and cash flow, TV menu boards that follow your Clover menu, and a website that always shows today's prices.
In short: connect Clover once (OAuth or a dashboard API token), Orqestra reads orders, items, customers, employees and tenders on a 15-minute schedule (2 minutes with webhooks), and never writes to your Clover account unless you turn on two-way menu sync.
What Orqestra reads from Clover
Everything stays read-only by default. Orqestra asks for read access to these Clover objects and keeps syncing them:
| Clover data | What Orqestra does with it |
|---|---|
| Orders, line items, payments, refunds | Sales by day, hour, channel and tender; average ticket; refunds and discounts; menu margins; recipe depletion |
| Tenders | Names each payment method (cash, credit card with its brand, gift card, custom tenders) instead of 'other' |
| Items, categories, modifiers, item stock | Your menu in Orqestra, TV menu boards, the QR menu, the website menu, cost per item for margins |
| Customers | Repeat rate, new vs returning, top spenders, loyalty and CRM |
| Employees and shifts | Who took each order; labor cost and sales per labor hour when the Clover app has the employees permission |
| Merchant and locations | One Orqestra location per Clover merchant; multi-location reports on Enterprise |
Two ways to connect
- 1
Sign in with Clover
From Orqestra's Connect page, approve read access on Clover's own screen. Nothing to install on the device.
- 2
Paste a dashboard API token
Create a token in your Clover web dashboard (Setup, API tokens), paste it in Orqestra, and the first sync starts. Handy while Clover App Market listings are pending.
- 3
First sync
Orders from the last 90 days, the whole menu and your customers come in on the first run. Later runs read only what changed.
- 4
Keep syncing
Every 15 minutes by schedule, every 2 minutes when Clover webhooks are on, and on demand with Sync now.
Reports Clover does not give you
- P&L with prime cost and food cost: net sales minus the cost of what you sold (recipes) and bought (bills), plus labor from the time clock or Clover shifts. Prime cost is the number most owners want and Clover never shows.
- Sales by daypart and day of week with the same period last week, month or year next to it, so a slow Tuesday is obvious.
- Average ticket and items per order by channel: dine-in, online ordering, delivery marketplaces.
- Menu engineering: popularity against margin for every item, using the recipe costs you enter once.
- Alerts when sales drop, stock runs low, a sync fails or prime cost crosses your target, by email, phone push or the in-app bell.
Operations that follow your Clover menu
Because the menu lives in Clover, Orqestra treats it as the source of truth. TV menu boards list the categories you pick and update themselves on their next poll when you reprice or 86 an item. The QR menu and website read the same data. Inventory depletes recipe ingredients as each Clover order syncs, so counts and low-stock warnings stay honest.
Two-way menu sync (editing items in Orqestra and pushing them to Clover) exists but stays off unless you turn it on; it is the only write Orqestra ever makes.
Clover App Market and security
Orqestra is listed as a Clover app (the App Market approval is in progress; the API-token path works today). Access tokens are encrypted at rest with a key the database never sees, you can disconnect from the Connect page at any time, and disconnecting deletes the stored Clover access. The full data policy is in the privacy policy.
Questions
Does Orqestra replace the Clover dashboard?
No. Clover stays your POS and system of record for orders and payments. Orqestra is the reporting and back-office layer on top of it.
Which Clover plan do I need?
Any Clover plan that gives you web dashboard access works. Orqestra reads through Clover's API, not through the device.
How far back does the history go?
The first sync reads 90 days of orders. Longer history can be loaded on request for an Enterprise business.
Can I use it with Square or Toast instead?
Square and Toast connections exist for early-access customers, and any POS can send a CSV export. Compare them on the Clover vs Square and Clover vs Toast pages.
See it with your own numbers
Request access, connect Clover in a minute, and your first reports are ready after the first sync. No card needed.