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: 7 / 30 / 90 days or 12 months; view all locations together or each one separately.

Available on AWS brands (cenaly.com, cenaly.ru and others), not on cenaly.ru. The platform's analytical database these figures come from is not deployed in the Russian contour, so the "Cash shifts" and "Delivery channels" tabs are always empty there — they have no fallback calculation. The other tabs are computed straight from orders and work on every brand.

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
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). AWS brands only
Delivery channels	Integration "health": online / paused / offline, downtime hours, estimated lost revenue, cancellations. AWS brands only
Order sources	Attribution: where the order came from — UTM tags, search, social, referrals
Staff	Worked hours from employee shifts

All key metrics are compared to the previous period — growth and decline are visible at a glance. The one exception is the "12 months" period: it has no comparison, being a calendar slice without a preceding stretch.

Sales channels and payments#

Revenue is broken down by channel:

Dining area — table orders (QR menu and POS);
Delivery — your own delivery;
Pickup;
Glovo and Wolt — aggregator orders (via integrations);
Other.

A separate breakdown covers payment methods: cash, card on delivery, online.

Channel commissions and net margin#

100 GEL from the dining room and 100 GEL 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 %.

This is the expected payout computed from your own rates. Reconciliation against the platforms' real settlement reports is not done yet.

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.

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.

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#

⚠️ The section runs on the AWS contour. It does not exist on cenaly.ru: there is no analytics database in the Russian contour, so reads honestly answer "no database".
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 section is empty or unavailable. If you are on the Russian brand, that is expected. On other brands check the period: 7 days is the default.

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.

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?#

No, the section is available to the account owner. Waiter, cook and courier roles don't see finance.

Are cancelled orders counted?#

Cancellations are shown as a separate metric and are excluded from revenue.

💰 Finance