Skip to content
Reportkey
iiko
Restaurants and delivery

iiko delivery report for restaurants

Reportkey collects delivery and pickup orders from iikoCloud every day and shows a restaurant and its marketer how many orders came in, for how much, how many were canceled and which channels and locations handled them.

14 days free · no card required · all integrations
Sign up, add the iiko API key and choose organizations in a project. Delivery orders start collecting into the report from that day.
  • Delivery and pickup orders by day, week and month.
  • Average order and cancel rate for every outlet in the chain.
  • Ordering channels: website, app, aggregators and call center.
Sample Reportkey client report
Sample Reportkey client report
iikoDelivery orders, amount, cancels, and sources
30+
integrations
5 min
setup
14 days
trial
TL;DR

iiko integration: add an iikoWeb API key once on the integrations page and choose organizations in a project; from that day Reportkey stores delivery orders daily, and the report shows order count, amount, average order, cancellations and sources by location.

iiko delivery report for restaurants and marketers

iiko automates restaurants, cafes and quick-service chains. Its cloud part, iikoCloud, receives delivery and pickup orders from the website, app, aggregators and call center and passes them to the kitchen and couriers. A marketer or owner needs a short answer from that stream: how many orders, for how much, the average order, how many were canceled and through which channels. Reportkey reads this through the iikoCloud API and puts it into a recurring report where delivery sits next to ads, website traffic and payments.

Connecting iiko with an iikoWeb API key

The key is created in iikoWeb under integrations, API keys, and it determines which organizations, meaning the restaurants of a legal entity or chain, are visible. It needs the permission group for receiving delivery orders; menu, payment or stop-list rights are not required.

The key is added once on the Reportkey integrations page as a shared connection. A project then selects organizations and, inside them, terminal groups, which are the actual outlets. Run a chain as one project split by outlet, or give each manager a separate project. If the key is deleted in iikoWeb, the connection asks for a new one and the project keeps its selection.

Why history starts on the day you connect

This is the main property of iiko data. The delivery orders method returns a guaranteed window of only the last seven days; older orders are available only by customer phone lookup, which does not suit reporting. Reportkey therefore saves new and changed orders every day from the first day of the connection and builds the report on that stored base. Connect early: after a month you get full week-over-week comparisons, after a quarter month-over-month ones. Periods before the connection are not loaded, which is worth telling the client up front.

Orders, amount, average order and cancellations

The report counts orders that reached the delivered or closed status and lists canceled orders separately:

  • Orders — delivered and closed in the period.
  • Order amount — after discounts and surcharges, excluding cancellations.
  • Average order — amount divided by orders.
  • Canceled orders — with the cancel reason when staff entered one.
  • Cancel rate — canceled orders among all placed.

Order amount is not accounting revenue or confirmed payment, and dates use each outlet’s local time, which matters for chains across time zones.

Order sources, outlets and order types

Each order carries an ordering channel and a marketing source from the iiko list. The channel tells where the order was placed; the marketing source, filled by operators or integrations, may name a promotion, promo code or ad platform. The report shows orders, amount and average order for each. An outlet table with orders, amount and cancellations, split into courier delivery and pickup, shows where operations rather than ads cause problems.

iiko next to ads and payments

Add Yandex Direct campaigns, VK Ads and delivery site traffic from Yandex Metrica or Google Analytics 4 to the same report, and reconcile online payments with YooKassa or CloudPayments. Every sales source is listed under ecommerce integrations. AI insights and report branding are not on every plan. See the in-house marketer demo report and pricing for a 14-day free trial.

Metrics

What goes into the iiko report

These are the metrics that the iiko integration already brings into Reportkey reports.

Orders
Order amount
Average order
Canceled orders
Cancel rate
What this integration adds to the report
Delivery orders, amount, cancels, and sources
Pricing

iiko reporting: plans and free trial

14 days free, no card required. Prices and plan limits are on the pricing page.

Use cases

Why teams connect iiko to Reportkey

Real reporting jobs, typical pain points, and the outcomes teams get from iiko in client reports.

Pain points
  • A marketer launches delivery ads and learns the order count from the restaurant manager in a chat message, with no split by day or location.
  • iiko reports are built by accounting, so the delivery average order arrives only after month-end.
  • Website, app and call center orders blend together, and nobody knows which channel is growing.
iiko
An agency promoting restaurant delivery

Yandex Direct and VK ads drive traffic to the delivery website. A weekly report places spend, visits and iiko orders for the same week side by side, which settles whether the ads work.

iiko
A pizza or sushi chain

Every outlet has its own terminal group in iiko. The owner gets a monthly document comparing outlets by orders, amount, average order and cancel rate, with courier delivery separated from pickup.

iiko
A dark kitchen with its own site and app

The manager tracks channels: website orders, app orders and orders taken by the call center. The source block shows where demand moves after each promotion.

Report preview

How iiko appears inside the report

The report keeps the familiar Reportkey layout: source sections and period comparison.

Sample Reportkey client report
Sample Reportkey client report
One week of iiko delivery

Daily order bars with an amount line, tiles for average order and cancel rate, an outlet table with orders and cancellations, and a chart of ordering channels.

How to connect

Three steps to the first report

Connect the account once, choose the reporting scope, and save the setup for recurring client reports.

01
Connect the account
Save the iiko connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the iiko store or site that should supply orders, payments, or leads to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ

Frequently asked questions

Short answers about how the integration works in Reportkey today.

What do I need from iiko to connect it?
An API key from iikoWeb, under integrations and then API keys. The key defines which organizations can be read and needs the permission group for receiving delivery orders. Enter it once on the Reportkey integrations page and pick organizations or outlets in a project.
Why are past months missing from the report?
iikoCloud guarantees delivery orders only for the last seven days. Reportkey therefore stores orders daily from the moment you connect and builds the report on that accumulated history. The earlier the key is added, the longer the period comparison you get.
Is dine-in revenue included?
No. The report covers delivery and pickup orders that pass through iikoCloud. Dine-in sales, banquets and catering are outside this data, so the total is not the venue's full revenue.
Why does order amount differ from the till or accounting?
iiko calculates order amount after discounts and surcharges, but it is neither confirmed payment nor accounting revenue. Order dates also use the outlet's local time, while accounting may close shifts differently.
Can I see which ad campaign produced an order?
The order source comes from the iiko marketing source and the ordering channel: website, app, aggregator or call center. There is no automatic link to an ad campaign; if operators and the website fill the marketing source per campaign, the report breaks orders down by it.

iiko delivery report for restaurants

Sign up, add the iiko API key and choose organizations in a project. Delivery orders start collecting into the report from that day.

Start free