Operations: one screen where every order is visible

Intake, kitchen and hand-off

The pain: orders in five systems, receipts spilling out of the printer, nobody knows the priority or how long an order has already been waiting.

“Kitchen → Kitchen orders” gathers every order from every channel with the full status chain: pre-order, new, accepted, in the kitchen, ready, on the way, completed. Each order has a running timer — you don't see “lots of orders”, you see the specific order that has been waiting 14 minutes.

Screens are split by station: production, buffer, pass. Changing a status takes one tap, so an order doesn't get lost on the counter between assembly and hand-off. On top there are filters by channel, payment, operator and branch, and receipts and shift closing are handled right from the panel.

Stop-lists

The pain: a manager manually takes an item off in five dashboards, and a guest manages to order something the kitchen no longer has. Then comes the call, the cancellation and a negative review.

Menus, prices and stop-lists are the same for the website, app, bot and aggregators: one source of truth. “Kitchen → Stop-list” shows two lists — “Stopped” and “Available products” — and an item is taken off in one click across all channels at once.

The effect is direct: guests don't order what is unavailable, so the cancellation rate doesn't grow and you don't pile up negativity that later has to be dealt with in reviews. Stop-lists can be managed by ingredient — then a product that runs out takes off every dish that uses it.

Single catalogue

The pain: the menu lives in five dashboards — the website has its own, the aggregators have theirs — edits go round in circles and still drift apart.

“Catalogue → Products” holds categories, tags, modifiers and combos; hundreds of items are managed in one list with statuses, prices and categories. Any product scenario is supported: a simple product, variations, a modifier, a combo set.

Bulk operations are built for real work: the menu is loaded from a file or via API, and prices and statuses are edited in batches rather than one item at a time. Menus can be built per channel and per time of day — for example, a separate breakfast menu until 11 a.m.

Per-channel pricing and availability

The pain: the aggregator takes up to 30% commission, yet the price is the same as in the dining room. The margin melts away, and there is nowhere to fix it across five dashboards.

The price matrix shows one item across all storefronts in a single row: dine-in, aggregators, superapps, your own channels. Availability is switched on with a checkbox — an item is sold in the dining room but hidden on the aggregator. Auto-adjustment applies a channel markup to the whole menu at once, rounded to a sensible price.

This is the fastest way to win back margin without negotiating with the platform: the price in a channel should reflect what that channel costs.

Product card and AI content

The pain: hundreds of items without photos or descriptions, and in several languages at that — a content manager spends weeks filling them in, and an item without a photo sells worse.

Right from the product card you can generate an image if there is no photo of the dish, and generate a selling description from the name and ingredients — with one button. The platform is multilingual, so the card is filled in all connected languages at once, without translating each item by hand.

The same card holds variations, SEO fields, a recommended-items block and menu assignment — all on one screen, without jumping between sections.

Dispatch and live map

The pain: the dispatcher calls round the couriers for every order, delivery takes 60–70 minutes, and nobody can say where a given order is right now.

“Orders → Show on map” is a live map with orders, couriers, branches and traffic. Orders are split by branch, and couriers accept them in their own app. Dispatcher mode shows which couriers are online, how many current orders each has, how long they have been in a status and even their phone battery level.

External delivery is called automatically: Yandex Go, Wolt Drive, Millennium and Noor are summoned from the system without a single phone call. In the Oqtepa Lavash case delivery time dropped from 60–70 to 30–40 minutes. To be honest about it: there is no automatic courier assignment in the system — the courier takes the order in the app, or the dispatcher assigns it.

Courier app

The pain: the courier calls the dispatcher, the guest calls the restaurant, and nobody knows where the order is.

The courier app has the order, the route and navigation: accepted, picked up, delivered — statuses are recorded automatically. The guest sees the courier on the map with live tracking and so doesn't call the till — which noticeably takes load off operators at rush hour.

Courier settlements are kept in the system, not in a notebook: cash, card payments and totals for each courier go into a report. The courier app is available on the ENTERPRISE plan.

POS integration

The pain: a typical integration works on a “send the order and forget it” basis — statuses, cancellations and payments drift apart between systems, and month-end reconciliation turns into an investigation.

Delever has its own plugins for iiko and r_keeper: the plugin sits right on the POS, keeps a connection to the cloud and reconnects on its own, and new versions are installed centrally, without visiting every branch. It is not an API wrapper that breaks when the POS is updated.

Synchronisation is configured in the interface: more than 40 options — order completion and cancellation, statuses, stop-lists, couriers, in both directions. Delever's and the POS's order types, payment methods and statuses are mapped pair by pair. Surcharges, service fees, cashback and deposit wallets reach the POS correctly. For your own systems there is an open API.

Branch monitoring and error handling

The pain: the POS “went down” overnight, orders never arrived — and you found out in the morning from guest complaints.

For every branch you can see its status: online, plugin version, time of the last connection check. If a branch is unreachable or closed, order intake stops automatically — the channel switches itself off instead of collecting orders that nobody can cook. The system also makes sure every channel serves the current menu and up-to-date prices.

A separate section covers errors and resends: a problem order is flagged with the exact cause of the failure, errors are grouped by branch and integration (so you see a systemic problem, not a one-off), and the order can be resent to the POS right from the interface, without manual entry.

Overview

Manage dispatching, couriers and kitchen from one dashboard Dispatcher assigns orders in one click, couriers accept them in the app