iiko integration with Delever

What flows into iiko

Orders arrive in iiko complete: items, modifiers, quantity, guest comment, payment type, address and delivery time — so they look exactly like a cashier-entered order and appear in all standard iiko reports. Menu, prices, modifiers and stop-lists flow back from iiko into Delever. You keep managing the menu where you already manage it.

Stop-lists: usually the real reason

The most expensive failure in delivery is an item that ran out but was still orderable. You have taken the money, and now someone has to call and apologise. With the integration, the iiko stop-list propagates to every channel at once — the item disappears from your site, your bot and every connected aggregator with no human involved.

What changes operationally

The person who retypes orders disappears from the process. In peak hours that person is the bottleneck: the order sits unaccepted, the kitchen gets it late, the guest waits. Orders go straight to the kitchen display. Couriers pick up available orders in the app themselves, or a dispatcher assigns them; if you run short, the order is passed automatically to Yandex Delivery, Wolt Drive, Taxi Millennium or Noor.

How to connect

You need iiko Cloud API access for your organisation, issued from your iiko account. The rest is configured on our side: mapping outlets, payment types and delivery zones, then verifying a test order. No development required, and connection takes a day. Delever integrates with sixteen POS systems, so mixed-POS chains stay in one system.

Connecting iiko to your website

This is the most common request, and there is usually one of two different tasks behind it.

The first is “I want to take orders on my website and have them land in iiko”. Then you don't need a separate integration: the website in Delever is a channel — it takes the menu from iiko and sends the order back there in full, with items, modifiers, payment type, address and delivery time. The storefront is assembled with a builder in the panel; no development is required.

The second is “I already have a website on Tilda or a custom build, and it needs to work with the POS”. The honest answer here: connecting an arbitrary website directly to iiko is only possible through development, and you will have to maintain it yourself. It is more practical to plug Delever in as a layer between them — then the existing website passes the order to the platform, and the platform holds the connection to the POS and survives iiko updates. We have an open API for this.

The choice between these paths usually comes down to one question: who will fix the integration when the POS gets updated.

iiko and 1C: who is responsible for what

The “iiko plus 1C” combination is common in Uzbekistan, and the roles in it are clearly split.

iiko handles the venue's operational accounting: cost of goods, inventory, write-offs, recipe cards, shifts. 1C handles bookkeeping and reporting for the legal entity. Delever replaces neither: it is responsible for sales and delivery, and passes order data to the POS, from where it moves on into the accounting loop.

We also offer 1C as a separate integration — for chains where some locations don't run on iiko. In that case data is exchanged directly with 1C, and orders are consolidated at the brand level.

The practical point: when you connect delivery, you don't touch your established accounting setup. The only thing that changes is where orders come from.