iiko ↔ Zoomda integration: step-by-step guide and pitfalls

Why integrate iiko with Zoomda

iiko is an excellent back-office system: menu, inventory, fiscal receipts, reporting. But it doesn’t give you an online channel — no website, no Mini App, no mobile app, no push-driven loyalty program.

Zoomda is the opposite — strong in online channels. Pairing iiko (POS) with Zoomda (online) gives you the best of both worlds: you keep your POS, don’t retrain staff, and still get everything Zoomda offers.

What gets synced

• Menu (categories, dishes, modifiers) — both ways.
• Stop list — from iiko to Zoomda instantly (if the kitchen runs out of mozzarella, it’s automatically hidden on the website).
• Orders — flow from Zoomda into iiko as regular orders, with no manual re-entry.
• Fiscal receipts — issued through iiko, with fiscal data sent to the OFD.
• Inventory levels — to calculate the cost of website orders.
• Guests — a single database shared by iiko and Zoomda CRM.

Step by step

1. Create an API user in iiko (Settings → API → Create). Send the login and password to Zoomda.

2. Set up the connection in Zoomda and choose which locations to sync.

3. Run the initial menu sync — it takes 5–10 minutes for 200–500 items.

4. Test an order: create a test order in Zoomda and check that it appears in iiko and a fiscal receipt is issued.

5. Turn on automatic updates for the menu (every 5 minutes) and the stop list (instantly via webhook).

Pitfalls

• Duplicate dishes: if the same item sits in two categories in iiko, Zoomda imports it once. Fix it with mapping settings.
• Modifiers: every modifier needs a unique ID. If iiko has “Cheese” on one pizza and “Cheese” on another, make sure they’re the same object.
• Per-location pricing: if your prices differ between Tashkent and Samarkand, set up price zones in iiko before integrating.