Finance
The Finance section is a set of management dashboards built from your orders, inventory purchases and staff shifts. No manual exports or spreadsheets: the data is collected automatically as the venue operates.
Open: Admin panel → Finance. Periods: Today, Yesterday, 7 / 30 / 90 days, 12 months or custom dates (from–to); compare with the previous period, the same period last year or your own dates. View all locations together or each one separately.
Tabs#
| Tab | What it shows |
|---|---|
| Overview | Key KPIs: revenue, order count, average check, cancellations, delivery fees, purchases, gross profit |
| Sales | Revenue by day/month, sales channels, payment methods, gross → net by channel (with platform commissions), per-location breakdown, taxes by rate |
| Purchases | Inventory purchase documents, spending dynamics, food cost |
| Expenses & P&L | Venue expense tracking and the profit-and-loss report |
| Cash shifts | Closed shift history, cash sales, cash reconciliation (discrepancies) |
| Delivery channels | Integration "health": online / paused / offline, downtime hours, estimated lost revenue, cancellations |
| Order sources | Attribution: where the order came from — UTM tags, search, social, referrals |
| Staff | Worked hours from employee shifts |
The comparison depends on the period: Today and Yesterday use the same weekday last week; 7/30/90 days use the preceding window of the same length. There is no comparison for 12 months.
Sales channels and payments#
Revenue is broken down by channel:
- Dining area — table orders entered by staff: the register or a waiter;
- Dining area · QR — orders the guest placed from their own phone through the table QR code (even if they paid at the register later);
- Kiosk — orders from a self-service kiosk;
- Delivery — your own delivery;
- Pickup;
- Glovo and Wolt — aggregator orders (via integrations);
- Other.
A separate breakdown covers payment methods: cash, card on delivery, online.
From a figure to orders. The rows of the Sales channels and Payment methods blocks are links. Click Cash, for example: the orders for the same period and location paid in cash open. The list total matches the block figure. There you can also narrow by staff, discount, item or table and export a CSV by item. The same works for the order count in the Sales by staff rows (orders of that waiter or cashier, per the chosen axis), the check count in the Discounts and promotions rows (orders with that promotion, discount reason or coupon), item names in the Items breakdown of the Taxes by rate block, and the labels of the Revenue, Orders and Average check cards on the Overview.
Channel commissions and net margin#
1,450 ₽ from the dining room and 1,450 ₽ from an aggregator are different money: the platform takes a percentage and often a per-order fixed fee too. Until commissions are set, "revenue by channel" compares incomparable things.
Set them in Extensions → the "By location" tab → the "Channel commissions" card: a percentage and a fixed per-order fee for each channel. Rates are set per location + channel pair: different venues have different contracts.
After that the "Sales" tab gains a "Gross → net by channel" table:
| Column | What it is |
|---|---|
| Gross | the channel's order total before the cut |
| Commission | percentage of revenue + the allocated share of the fixed fee |
| Net | the expected payout after commission |
The same arithmetic is applied to individual dishes in Menu engineering: a dish with an average in-house margin can go negative in an aggregator taking 30 %.
Commissions are stored separately from the integration's own settings, so they can also be set for channels with no integration at all (your own site, dine-in, pickup), and orders from a channel disconnected yesterday keep counting with the commission that applied.
Dayparts: breakfast, lunch, dinner#
To compare lunch with dinner, or weekday lunch with weekend lunch, use the Sales by daypart block on the Sales tab.
| Column | What it is |
|---|---|
| Daypart and hours | breakfast, lunch, dinner, night or your own dayparts with “from–to” hours |
| Orders | orders placed in those hours (cancelled ones excluded) |
| Sales | order total for the daypart |
| Share | the daypart's share of the period's sales |
| Avg. check | daypart sales / orders |
Below it is the Days × dayparts grid: by date (a weekly report with Breakfast / Lunch / Dinner columns) or by weekday with Weekdays and Weekend rows.
How an order gets its daypart. By the local hour it was placed and the dayparts of its own location: a coffee shop's breakfast may be 7–12, a restaurant's 9–11. Dayparts are applied when the report is built, so after you change the setting the whole history is shown the new way at once.
Setup. The ⚙ Set up dayparts button in the block (or Settings → Orders → Dayparts): name, start hour and end hour, up to 8 dayparts. An end hour earlier than the start runs past midnight (23:00–06:00). Without a setting the default hours apply: breakfast 6–11, lunch 11–16, dinner 16–23, night 23–6.
- Two dayparts cannot overlap — such a setting will not save.
- Hours outside every daypart are allowed: their sales go to the Outside dayparts row, and the block warns which hours they are. The rows always add up to order sales.
- Refunds and guest folios have no hour and are not in this block — it shows sales before refunds; the final revenue is on the Revenue card.
Categories by daypart and channel — in Dish statistics, the 🗂 Categories view: revenue, share, portions and average price of each menu category, split by Dayparts or Channels. The table total equals dish revenue; a dish in several categories counts in the first one, refunds are a separate column.
Sales by report group — a block under the top dishes: dish sales after order discounts by Food / Drinks / Alcohol / Other, independent of the menu layout; the total equals the dish total of the period, items without a group are a "No report group" row. Groups are set on categories and items in Dish statistics (the "Set up" link in the block). Merged duplicate items appear as one row under the primary item in the top dishes and in this block.
Sales by employee#
The Sales by employee block on the Sales tab shows how much each employee sold for the selected period and location:
| Column | What it is |
|---|---|
| Orders, Revenue, Avg. check | The employee's orders, excluding cancelled orders and staff meals; revenue is after order discounts |
| Tips, Tips % | Tips on their orders and their share of revenue (tips are not part of revenue) |
| Discounts | Discounts on their orders: check discounts, coupons and item discounts |
| Manual discounts, Voids | From the register's risky-operations log: how many manual discounts (amount and count) and voids the employee performed |
Attribute sales to — the switch above the table:
- Waiter (table) — the sale goes to the waiter the order belonged to;
- Cashier (paid by) — the sale goes to whoever took the payment: the receipt's PIN operator or the cashier signed in to the register.
These are different questions: a waiter served the table, but a manager may have settled the bill. Manual discounts and voids are credited to the employee who pressed the button in both views.
Row revenue adds up to order revenue for the period. Orders without a waiter (storefront, delivery) or not paid at the register appear as a No employee row — nothing is lost. Click a name to expand the employee's dishes (quantity and amount) and payments by method. The CSV button downloads the rows shown.
An employee with access to Finance sees only the locations in their scope: sales and operations of colleagues at other locations are not in the block.
By register#
The By register block on the Sales tab shows what each register of the location sold: checks, revenue, average check, share, and next to them the risky operations of that register (count and amount) and how many times the drawer was opened without a sale.
A register is the device where the bill was closed: a tablet, laptop or all-in-one with the register open. To see a clear name in the report instead of a number like #7K3F, name the register on the device itself:
- Open the register on that device.
- Open the POS appearance window (the gear in the register menu panel) and find the Register name field.
- Type a name, for example “Register 1 · bar”, and press Enter.
The name is stored on this device and applies to everyone who works on it. Sales and operations made after that appear under the new name.
The register app for Android, Windows and Ubuntu marks itself: in the report it shows under the device name — the tablet model (for example, “SM-T295”) or the computer name (for example, “TILL-1”). To see a clear name in the report, open the register’s device menu (on Android — the cross on the order screen, on Windows and Ubuntu — the menu button in the header) and fill in Register name, for example “Register 1 · bar”. The name is saved right away and applies from the next payment; an empty field brings back the device name. Two identical tablets still stay separate rows — a register is told apart by the device, not by its name.
The rows add up to the revenue of the period. Orders not paid at a register (online payment, delivery platforms), sales from a register app not yet updated to this version and sales made before this report appeared go into the Register not recorded row. The block appears when the period has at least one register with a mark.
The same breakdown is in the risky operations log: Statistics → Risky operations → By register (loss control).
Discounts and promotions#
The Discounts and promotions block groups every discount of the period by type:
- Check discount — by reason: promotion, loyalty, manual discount, staff discount, on the house and so on (the reason is chosen at the register when applying the discount);
- Coupon — by promo code;
- Item discount — discounts on individual receipt lines.
Each row shows the discount amount, the number of checks, the average depth (discount relative to sales before discounts of those checks) and the share of all discounts. Cards on top: total discounts, checks with a discount, percent of sales before discounts and the average depth of a discounted check.
Under the table is a reconciliation line: sales before discounts − revenue = total discounts. Refunds are not included (they have their own card on the Overview tab), nor are cancelled orders and staff meals. The CSV button downloads the block rows.
Taxes by rate#
Result: you see how much tax was collected on sales for the period and which rates, groups, categories or items it came from. The block's tax total equals the Sales tax collected card on the Overview tab.
- Open Finance → Sales tab.
- Choose the period: 7 days / 30 days / 90 days / 12 months or 📅 Custom dates. If you have several locations, pick one in the All locations list (the list is hidden when you have one location or a pinned one).
- Find the Taxes by rate block and choose Break down taxes by: Rates, Report groups, Menu categories or Items. The chosen breakdown is kept in the page address, so you can send the link to your accountant.
- Read the columns: Orders, Sales incl. tax, Tax, Net of tax and the Total row. The Items breakdown adds quantity and rate, and an item name opens its orders.
- The first 30 rows are shown; Show all opens the rest.
How to read the figures:
- Refunds are already deducted. Figures are net of the period's till refunds; a refund takes the tax rates of the order it reverses, just as the refund receipt repeats the sale receipt's rates. The Refunds, tax column shows how much tax went to refunds.
- Amounts before discounts. The Before discounts, incl. tax and Tax before discounts columns show what the items would have cost and how much tax they would have carried without item, check and coupon discounts; under the table, the Discounts cut tax by … line. These columns appear once the finance database has been recalculated with this data.
- Rate rows are labelled "VAT 20%", "VAT …% (simplified regime)", "VAT exempt", "Rate not set", "No tax", "Guest folios (tax)". "Several rates" means the order's tax was calculated at order level and split across its items in proportion to their revenue.
- The service charge is not in this block. It has its own Service charge card on the Overview tab, marked as not included in revenue.
- If there was no tax in the period, the block is not shown.
You can export the block with the XLSX, PDF or Print buttons in the page header — they save the tab exactly as it is on screen. So choose the breakdown and click Show all first, otherwise only the first 30 rows go into the file. More in Send figures to a spreadsheet.
Delivery channel health#
The "Delivery channels" tab answers the opposite question: how much you did not earn, and why.
- the current status of the location on each platform: online / paused (your own pause) / offline (the platform deactivated the venue);
- hours of pause and offline over the period;
- an estimate of lost revenue — downtime hours × the channel's average hourly revenue for that hour of the week;
- cancellations broken down by reason.
The status is polled by a background job roughly every 10 minutes; an involuntary offline sends the owner a push.
Purchases, food cost and gross profit#
If you use Inventory, receipt documents automatically form the cost side:
- Purchases — total receipts for the period;
- Food cost — purchases as a share of revenue;
- Gross profit — revenue minus purchases.
So the dashboard shows not just turnover but the venue's real economics.
Gift cards and guest debts#
Two amounts that must not be confused with revenue get their own place in the finance section — both summaries sit on the "Cash shifts" tab and load the first time you open it:
- Gift-card liabilities — an “issued / redeemed / outstanding” summary. A certificate sold is not money earned but a promise to deliver goods: revenue is recognised when the guest pays with the card, not when they buy it. The outstanding balance is what the venue still owes its guests.
- Guest debts — the totals of orders closed at the till with the “On account” tender, and their repayments. Open debts and each guest's balance are also visible in Customers and on the “Under control” tab of the work chat.
Selling a card and closing an order on account are fiscalised by each country's rules (in Russia, “prepayment” and “transfer on credit”), so they appear in X and Z reports as payment-method lines — see Cash shifts.
Staff#
The Staff tab sums worked hours from employee shifts — plan and fact per employee and role for the selected period.
Choose a period for the morning review#
The manager of Coffee Shop on Tverskaya wants to see whether yesterday was better than a typical day of the same week.
- Open Finance → Overview and select the location.
- Select Yesterday and check the figures and comparison label.
- Switch to 7 days for the broader trend: this compares two consecutive seven-day windows.
| Period | Dates included | Compared with |
|---|---|---|
| Today | Today's calendar date | The same weekday last week |
| Yesterday | Yesterday's calendar date | The same weekday last week |
| 7 days | Today and the preceding 6 days | The preceding 7 days |
| 30 days | Today and the preceding 29 days | The preceding 30 days |
| 90 days | Today and the preceding 89 days | The preceding 90 days |
| 12 months | From the first day of the earliest of 12 months through today | No comparison |
For example, on Tuesday, Yesterday compares Monday with the previous Monday, not with Sunday. Today is still in progress: a morning total is not a full day's result.
For sales strictly from 3 to 17 October, see the next section, Custom dates.
Custom dates and Compare with#
The accountant of Coffee Shop on Tverskaya reconciles revenue for 3–17 October with the bank statement, and the manager wants to compare this Tuesday with last Tuesday.
- In the period bar, click 📅 Custom dates — From and To fields appear, pre-filled with the period that was on screen.
- Pick 3 October and 17 October. Every tab with the period bar — Overview, Sales, Purchases, Expenses & P&L, Cash shifts, Delivery channels, Order sources — is recalculated for these dates. The Staff tab has no period bar.
- In Compare with, choose the base for the percentage change:
| Option | Compared with |
|---|---|
| previous period | The same number of days right before: for 3–17 October that is 18 September – 2 October |
| same day last week | Default for Today and Yesterday |
| previous day | For Today and Yesterday: yesterday vs the day before |
| same period last year | The same dates a year earlier; 29 February is compared with 28 February |
| custom dates | A second pair of date fields appears — for example, Tuesday 27 October and Tuesday 20 October |
| no comparison | No percentage change |
The label under the figures names the comparison base and its dates. If there are no figures for the comparison dates (order history is kept for about 400 days), a note says so — it is not a 100% drop.
Custom dates and the comparison are written to the address (?period=custom&from=2026-10-03&to=2026-10-17&cmp=yearAgo): a link to a colleague and F5 open the same view. Ranges longer than 92 days are charted by month; custom dates are limited to two years.
Day summary#
The manager of a coffee shop closes the day and wants the result in one table instead of collecting it tab by tab.
- On Overview choose Today, Yesterday or a single day in 📅 Custom dates.
- Below the day-to-day comparison a Day summary table appears:
| Row | What it shows |
|---|---|
| Revenue, checks, average check, guests | The same revenue as the Revenue tile; guests — from orders where the POS recorded them |
| Adjustments, total | Cancelled orders, refunds, discounts and items removed after sending to the kitchen — count and amount |
| Manual price changes / drawer opened without a sale | How many times that day (the cashier risk log) |
| Tips, service charge | Separately: not part of revenue |
| Payments | The day’s orders by payment method |
| Cost of goods sold | Amount and % by cost at the moment of sale; if it is known only for part of the items — the coverage |
| Labour cost, hours worked | From the day’s shifts and pay rates, as on Staff → Labour cost; until people clock in — from the schedule |
| Cash | Paid in, paid out and cash drops of the closed shifts |
| Check against Z reports | Sales of the shifts closed that day against the orders paid at the POS; “✓ matches” — the figures are equal |
| Hours by position | Hours and people per position |
- Need it on paper — the PDF or Print buttons at the top of the page export the tab with the summary.
Tips are part of the shift money (cash in the drawer, card tips in the terminal) but neither in the Z report sales nor in revenue, so the summary equals the sum of the day’s Z reports up to the tips. A “Difference” appears when an order was paid online (it never reaches a shift) or closed by a shift of another day.
Revenue plan and plan vs actual#
The owner of two coffee shops gives each a monthly target: 1,000,000 at “Centre” and 600,000 at “Embankment”.
- On Overview click 🎯 Revenue plan.
- Choose the location and year and fill in the months — Year total is shown below.
- A holiday or a banquet — add the day and amount in Days with their own plan: the rest of the month plan is spread evenly over the other days.
- Plans for all locations at once — Upload CSV with columns “Location; Period; Amount” (period —
2026-10,10.2026,2026-10-31or31.10.2026). Download CSV exports the plan in the same format. - Click Save.
Overview gets a Revenue plan tile: the percentage done and the plan of the period. If the period includes future days (a whole month, custom dates), “to date” below shows the percentage of the plan of the days already passed. The plan is split by days, so “30 days” is compared with the plan of exactly those 30 days; days without a plan are not counted — the tile says, for example, “plan set for 20 of 30 days”.
Location comparison (filter “All locations”) gets a Plan column: the location’s plan for the period and, for example, “85% done”.
Labor % on Overview#
A manager wants to see in the morning not only revenue but also how much of it went to staff shifts.
On Overview, the Labor % tile shows labor cost for the selected period and location divided by revenue. Under the percentage are the cost and hours, revenue per labor hour, and notes:
- “by schedule: 2 of 7 days” (example) — there are no clock-ins and clock-outs for these days (the day is still going or the timesheet is not kept), so cost is estimated from the shift schedule;
- “some shifts have no rate — understated” — someone who worked has neither their own rate nor a position rate at the location;
- “pay rates are not set or not visible to you” instead of a percentage — employee rates are visible to the owner and to people given payroll access. Finance access does not open rates: without them the tile shows no percentage rather than “0%”.
The calculation is the same as in Employees → Labor cost: hours × rate of each shift, a salary spread over the employee's planned hours of the month. That screen also has the breakdown by position with regular and overtime hours; it adds up to the total. Payroll taxes, commissions and tips are not included — this is an estimate, not payroll. Currencies are not added together: the percentage is calculated in the revenue currency.
The tile can be hidden with the page view gear (the “Simple” preset does not show it).
Totals from the previous POS#
A coffee shop moved to Cenaly in September, and the “a year ago” comparison is empty — there are no orders from last year in the system.
- Export daily totals from the previous POS to CSV: date, location, revenue and, if possible, checks and guests.
- On Overview click 📥 Previous POS totals → Choose CSV. Columns are recognised by the headers “Date; Location; Revenue; Checks; Guests” in any order; date —
2025-10-31or31.10.2025. - Check the line “… days will be uploaded” and the line errors, click Upload.
Now Compare with → same period last year and the previous-period comparison use the uploaded figures for days without orders here; a note appears under the comparison. Location comparison uses them for the previous period too. If a day has at least one order of its own, the uploaded total of that day is not used — nothing is counted twice.
Uploaded totals are not orders: they never go into the revenue of the selected period, menu statistics or accounting. Uploading the same day again replaces it; to delete everything for a location use Delete in the window’s list.
Day results by email on a schedule#
The owner of two coffee shops wants yesterday's figures every morning without opening the admin, and the accountant needs the same summary in their own inbox.
- On Overview click 📧 Day results by email.
- Turn on Send day results and choose the day: Yesterday, in the morning (08:00 by default) or Today, after closing — for example at 23:30. The time is local to each location: locations in different time zones get the summary in their own morning.
- Channels: email, Telegram (to the owner chats of the location's bot; the bot is connected in Integrations → Telegram) and push to the manager app.
- Who gets the email: Me (account email), more addresses separated by commas and staff positions — active employees of these positions with an email get it, and each sees only their own locations.
- If needed, tick locations — with none ticked the summary covers all of them.
- Click Save. To check right away, click Send a test now: the summary for the report day goes to the same recipients and the figures appear as a table in the window. The scheduled summary still arrives on time.
For each location the email shows revenue (and the change against the same day a week ago), checks, average check, cancelled (count and amount), discounts, plus refunds and tips if there were any; a network also gets a total, separately for each currency. A location with no sales, cancellations or refunds that day is left out; if that is true for all of them, no email is sent that day. The button in the email opens Finance for exactly that day.
Example. On 28.10 “Cafe North” has three paid orders of 27, 30 and 30 RUB (the first with a 3 RUB discount), one cancelled order and a 5 RUB refund. The email says: revenue 82 RUB (87 − 5), checks 3, average check 29 RUB (before refunds), discounts 3 RUB, cancelled 1 — the same figures as Overview for 28.10.
The figures come from the same finance base with the same rules as Overview: revenue is orders minus refunds; cancelled orders and staff meals are not included. The summary arrives within 30 minutes of the chosen time: the base updates every half hour and the summary is built right after the update. If the server was unavailable at the chosen time, sending is retried for three more hours; after that the summary for that day is no longer sent. Each day's summary arrives once, however many times the base updates.
A network using different currencies#
Your network has a Moscow coffee shop taking rubles and a Tbilisi location taking lari. Their revenue cannot be added as if these were the same currency.
- Allow all locations in the shared location selector, then choose All locations and 7 days in Finance.
- Keep Show in set to Each currency separately to see the original totals.
- Select RUB for conversion to rubles. Read the footnotes beneath the totals before comparing them.
For example, 70,000 ₽ in Moscow and 2,500 ₾ in Tbilisi are two weekly totals, not revenue of 72,500 ₽. Conversion uses each operation's date, so multiplying the whole week by today's rate can give a different result.
| Symbol or footnote | Meaning |
|---|---|
| ≈ and exchange-rate details | Conversion uses the official central-bank rate for the location's country on the operation date; the banks and rate dates are shown |
| Via ECB | No suitable rate from the location's own bank was available; fallback conversion through euros uses ECB rates |
| No central bank rate… | Some operations have no rate; their original amounts are listed and excluded from the converted total |
On non-publication days, the last published rate is used; an unavailable or excessively old rate is not replaced with zero. We have our own rates from the central banks of Russia, Georgia, Türkiye and the euro area. For a location in another country, conversion goes through the ECB if it publishes that currency; if not, a missing-rate footnote appears — compare such amounts separately.
Overnight revenue and time zones#
For one location, the period boundaries use that location's time zone. If all selected locations share a time zone, All locations uses it too. With different time zones, the browser's calendar supplies the current date for the shared period. Operations keep their locations' calendar dates: the shared period does not move every sale into the manager's time zone.
To check overnight revenue:
- Select one location to use its calendar.
- Review Yesterday, then Today.
- Reconcile the cash shift separately: a shift is assigned to its closing date.
For example, a sale at 00:30 on 28 October belongs to 28 October, even if the shift started on the evening of the 27th. Finance has no reporting day ending at 04:00; an overnight shift can span two calendar dates.
Save your report view#
Set up a personal page view to open the figures you need each morning.
- Click the Settings gear and open Page view.
- Choose Simple, Standard or Detailed. Individual changes can make the view appear as Custom.
- Set Tab on open, Period, visible tabs and metrics, and Show in. The default period offers 7, 30 or 90 days and 12 months.
Settings belong to your user profile and, once saved successfully, are available on your other devices. They do not change colleagues' views. You can select Today and Yesterday in the report and share them by link, but cannot set them as defaults in this panel.
For quick access, open a tab such as Sales and click Add to sidebar. It becomes a separate menu item. Overview cannot be pinned separately.
Send a colleague the address after selecting the tab, period and location. The ?period=7d parameter opens the last seven days; today, yesterday, 30d, 90d and 12m are also recognised.
The tab and loc parameters carry the tab and location; a period-only link does not specify them. The period in the address overrides the personal default.
This is a link to a changing slice, not a snapshot: tomorrow, 7 days covers different dates.
Custom dates are carried by from and to, the comparison by cmp (previous, yearAgo, custom with cfrom and cto, none).
A specific location selected in the shared header limits the colleague's report selection. For a network comparison, allow all locations in the header. A link does not grant access: your colleague needs permission for the section and locations. See Roles and permissions.
My reports#
A network manager keeps a few views at hand: "Yesterday · Tverskaya", "Week · whole network year on year", "Purchases this month".
- Set the tab, period, comparison and location.
- Click ★ My reports in the section header, type a name and click Save.
- Next time, open ★ My reports and click the name — the same view opens with today's figures.
The star moves a report to the top of the list; with six or more reports a search field appears. Saving under the same name updates the report instead of creating a copy. You can keep up to 150 reports; they live in your profile and appear on your devices, not your colleagues'. The same window is available in Statistics.
A report keeps parameters, not a snapshot of figures: tomorrow "Yesterday" shows a different day. To pin dates, save custom dates.
Send figures to a spreadsheet#
You can download the open tab as a whole — as it looks on screen.
- Choose the tab, period, comparison and location.
- In the header click ⬇ XLSX for Excel or Google Sheets, ⬇ PDF to send to an accountant or investor, or 🖨 to print the same PDF.
- The file starts with the period, comparison base and location, followed by the tab's blocks: key figures, charts as tables, shares and tables.
In XLSX, amounts and percentages are numbers (the currency is in the cell format), so they can be summed; cells showing several currencies separated by "·" stay as text. Metrics hidden in Page view are not exported. The same export is available in Statistics.
Individual tables can also be exported as CSV:
| What to export | Where | Format |
|---|---|---|
| Location comparison | Finance → Overview → Location comparison | CSV |
| Menu engineering | Menu engineering | CSV |
| Network stock | Inventory, Network stock | CSV |
| Search queries | Statistics → Search | CSV |
| Orders | Orders → Export CSV | CSV: one row per order, items in one cell |
| Accounting reports | Accounting, reports | XLSX, PDF |
If Location comparison is missing, choose All locations: the block appears when there is more than one location. CSV opens in spreadsheet software. The order-list export does not provide a separate row for each item. For other reports, see Reports.
What you need to get started#
- Accumulated sales — the dashboards are computed from your orders and receipts, and on empty history they are empty.
- Recipe cards with purchase prices — for cost of goods, food cost and gross margin (Inventory).
- Shifts and payroll settings — for the "Staff" view (Staff).
- Channel commissions — so that "net by channel" is not computed against zero.
- Expenses are entered manually (rent, utilities, subscriptions) — they do not appear on their own.
Limitations#
There is no business day ending after midnight: periods use the location's calendar dates.
Several periods cannot be compared at once — one comparison per view.
XLSX/PDF export covers the open tab, not all tabs in one file. Only day results are sent on a schedule — a summary of Overview figures, not a tab file.
Day results do not include hotel guest folios (accommodation, minibar): only POS orders and refunds.
Operations without a suitable exchange rate are excluded from the converted total; check the footnotes and original currency totals.
Data loading matters. Cash shifts and delivery-channel history require the analytical database; the browser fallback cannot reconstruct them. On cenaly.ru, direct order-history listing is also unavailable. Report a database error instead of interpreting it as an empty sales period.
Aggregator commissions are estimates: the rates come from your channel settings, not from the marketplace's actual deductions.
Labour cost is computed from the payroll databases but is not posted as an expense line in the finance database.
There is no single metric glossary. The same revenue in Statistics, Finance and at the POS may be computed differently — when comparing numbers, check the period and exactly what falls into the slice.
There is no reconciliation of acquiring or aggregator payouts against a bank statement.
There is no custom report builder — deliberately: for now we cover this with standard dashboards and export.
Troubleshooting#
The network total does not match the sum of the locations. Check currencies first: rubles and lari cannot be added directly. Choose Each currency separately or check conversion footnotes — some operations may lack a rate. Select one location on tabs warning about mixed currencies.
Last night’s revenue appears under today. Sales after midnight belong to the new calendar date. Check both days for the specific location; use the closing date when checking a shift.
A colleague opens the link and sees nothing. A link does not grant data access. Check Finance permissions, the employee’s location scope and the location selected in the shared header.
The section is empty or unavailable. On the Russian brand you will see the notice "Order history cannot be read in this cloud yet" — that is expected, and it has no Retry button. On other brands the notice "Could not load the figures" with a Retry button means a read failure — retry; if there are simply no figures, check the period: the opening period depends on your page view.
The numbers do not match the POS. Look for the difference in the period and in what the slice contains: refunds, tips, channel commissions and unclosed orders land in different reports differently. There is no single "truth about the number" yet, and we say so plainly.
Food cost is not calculated. There are no recipe cards or no purchase prices.
"Net by channel" looks too high. Commissions are taken from your channel settings — check the rates against the marketplace contract.
There are no expenses in the P&L. Recurring expenses are entered manually — add them in the expenses view.
Related#
- Orders — the sales data source
- Inventory — the purchases data source
- Staff & shifts — the labor data source
- Analytics — guest behavior in the menu (views, popular dishes)
- Menu engineering — dish margin adjusted for channel commission
- Loss control — cash discrepancies and stock losses as alert rules
FAQ#
How is Finance different from Analytics?#
Analytics is about guest behavior in the menu (views, dish popularity). Finance is about money: revenue, average check, purchases, profit.
How often does the data refresh?#
Automatically, several times an hour. The "Refresh" button pulls fresh data immediately.
Can employees see finance?#
Waiter, cook and courier roles do not see Finance by default. The owner can grant access through the employee’s role; the link itself does not grant it.
Are cancelled orders counted?#
Cancellations are shown as a separate metric and are excluded from revenue.
Can I save yesterday’s report for a colleague?#
A link with period=yesterday always opens the day before the viewing date. For a fixed file, export an available table as CSV; for exact dates, use Dashboard.
Why does the RUB total not include the entire network?#
Check the missing-rate footnote: the listed operations were excluded from conversion. Their amounts remain available separately in the original currencies.
How do I open the tab I need straight away?#
In Settings → Page view, set Tab on open and Period. For direct access, use Add to sidebar on any tab except Overview.