Analytics: the business in real time
The costliest reporting problem is not missing data but late data. In Delever the numbers come from operations itself, so the dashboard updates as the branch works, not a week later.
Business dashboard
The pain: metrics are compiled in Excel a week after the fact, while decisions are needed today.
The dashboard shows delivery time, average check, number of orders and revenue at a glance — with the trend against the previous period, so a number reads as “worse/better” rather than an abstract figure. Next to it is the sales funnel by channel: delivery, pickup, aggregators, dine-in, completed and cancelled orders by month.
Any period and any branch can be sliced right in the interface — no exports and no requests to IT. This is the minimum an owner usually logs into the system for: 30 seconds in the morning instead of half an hour in spreadsheets.
Order structure by channel
The pain: it is clear there are plenty of orders. It is not clear where they come from and which of them are profitable.
This section shows each channel's share of the total flow: call centre, app, bot, aggregators, website. Separately, it shows payment types and ratings for each channel: how people pay and how they rate you. These are exactly the two views that reveal how a channel with many orders can bring in less money than a channel half its size.
Order geography is shown as a density map: where to grow the delivery zone and where it makes sense to open the next branch. The decision to open a location stops being a gut feeling — it rests on a map of real demand.
Branch cash reconciliation
The pain: end of shift at a branch — cash is with the couriers, payments are in Click and Payme, and the manager balances the till from memory and a notebook.
The branch till-closing tool (“Kitchen → Finance”) breaks things down by payment type: Click, Payme, Uzcard, cash, aggregators — totals for delivery, pickup and dine-in for any period. You can also see the money held by each courier: how much cash and card payments they have on hand, i.e. how much the manager has to collect when closing the shift.
Cancelled orders are there too: cancellation totals by payment type. This is the most common place for money to leak, and it should be visible as a number rather than surface at the end of the month.
Twelve ready-made reports
Reporting is covered by ready-made breakdowns, not “export it to Excel and work it out yourself”. The platform has 12 reports: revenue forecasting, general report, aggregators in one table, daily report, by product, by order, by external delivery, by late orders, by operator, by branch, by courier and by call.
The late-orders report shows not an average time but the specific orders that went over the standard — with the branch and the courier. The product report shows what actually sells and what just takes up space on the menu. The aggregator report brings every platform into one table, so reconciling with each of them stops being a separate month-end task.
Audit log and access control
The pain: who changed a price, who deleted an order, who gave a discount — there is no way to find out, and asking is pointless.
The change history (“Settings → Change history”) keeps a complete log: user, object, old and new value, time. Any action in the system can be reconstructed from this log.
Roles and permissions separate areas of responsibility: operator, manager, branch manager, owner — each sees only what is theirs. Multi-branch support lets you run the whole chain in one account: access, menus and prices are configured for each branch separately, while the summary covers the entire chain.
Call reports
The call centre is the only channel where a loss leaves no trace: the order simply never happened. Integration with OnlinePBX and Asterisk makes these losses visible.
Calls are broken down by hour, so you can see the peak hours when there are not enough operators. Statuses and answer rate show the share of answered, missed, unanswered and dropped calls. The breakdown by operator gives, for each one: total calls, answered, missed, average duration.
AI assistant digest
The pain: there is plenty of data but no time to put reports together — and decisions are once again made on gut feeling.
A digest arrives in Telegram every morning: revenue, orders, delivery time, best branch. The numbers come with recommendations: where to step up marketing, what to tighten in logistics, where to grow order frequency.
The key difference from external analytics: the assistant works on the platform's own data — it sees orders, the kitchen and logistics, not just a sales export. Alerts arrive in the same place: POS unreachable, payment failed, order stuck — the message reaches the branch's Telegram straight away, not after a guest complains.
Frequently asked questions
How “real-time” is the data?
The dashboard is built on the same order flow as operations: an order, a status change or a payment shows up in the metrics immediately. Period reports are generated on request for any interval and any branch, without overnight exports.
Can we export the data to our own systems — BI or 1C?
Yes. Reports are exported from the interface, and there is an open API for your own systems. 1C is already on the list of supported integrations.
How can I view data for just one branch?
Every report and dashboard can be filtered by branch and period. Permissions are set up so that a branch manager sees their own branch and the owner sees the whole chain: it is the same system, just different roles.
Are aggregator orders included in the overall analytics?
Yes, aggregators are a channel just like the app or the bot. Their orders go into the overall funnel, the channel breakdown and the reconciliation by payment type, and a separate report brings all platforms into one table.
Who can see guests' personal data?
Access depends on the role. Guests' personal data is hidden in notifications and in error reviews, and every change in the system is recorded in the log with the user, the time and the old value.