iiko Delivery Integration: How It Works

With iiko integration, orders from your website, Telegram bot, app and aggregators are not entered into the POS by hand: they reach iiko by themselves, while menu, prices and stop-list are taken from iiko and updated in every channel. Connecting usually takes one working day.

If your restaurant works in iiko, you don't need to replace the POS. Below we look at what the integration does, what it syncs and what to check before connecting.

Key points:

• An order reaches iiko, the cashier screen and the kitchen without manual entry.
• Menu, prices, modifiers and stop-list sync in both directions.
• A multi-branch chain connects each branch to its own iiko and manages everything from one panel.

How does an order reach iiko?

When the customer confirms an order on the website, bot or app, it goes to iiko through the API. It is visible on the cashier's screen and in the kitchen at once, and if needed it prints on the kitchen printer. The operator rewrites nothing.

The order contents are complete: dishes, modifiers, guest comment, payment type and address. Fiscalization and reports stay in iiko's usual process.

What gets synced?

Menu, prices, modifiers and stop-list. If you change a dish price in iiko or put a dish on the stop-list, the change updates on the website, bot, app and connected aggregators. So you no longer keep the menu in two places.

The most useful part is the stop-list: when a dish runs out, the customer can't order it. We wrote about how the stop-list works in the general article.

Which iiko versions does it work with?

According to the Delever site, iiko 7.x (server version) and iiko 8.x (iikoCloud) are supported, as well as the iiko RMS, iikoFront and iikoOffice components. If you have an older version, check with the Delever team before connecting.

How does it work in a multi-branch chain?

Each branch connects separately with its own menu, prices and stop-list in iiko, while management is in one Delever panel: orders and analytics for each location, and an overall view. When a new branch is added, the connection is repeated in the same way. Managing a multi-branch restaurant.

How does it work with aggregators?

Delever acts as the hub: an order from an aggregator reaches Delever first and goes from there to iiko. So no separate tablet stands next to the register, and all orders are in one POS. More on one screen instead of aggregator tablets.

How does the connection go?

A Delever specialist sets up the API connection, takes the menu from iiko, maps categories and modifiers, checks fiscalization and trains the team. This is included in the plan. Usually one working day.

Check these yourself before connecting:

• your iiko version, and whether API access has been granted;
• whether every dish in the menu has the right price, size and modifiers;
• how payment types are named in the POS;
• whether delivery needs a separate sales point or zone.

Conclusion

• Put your iiko menu in order: this one source feeds every channel.
• After connecting, place a few test orders: check contents, price and payment arrive correctly.
• Test stop-list sync separately.

We show how to connect iiko to Delever with your own menu: delever.io or @delever_bot on Telegram.