Back

Guide: Deliveroo

How Do Core Concepts Map to Tenzo?

Key: ✅ Supported   🚸 Work in Progress   ❌ Not supported

Location ✅ Site (matched on Deliveroo's site ID)
Delivery Order ✅ core_orders
Delivery Order Issue ✅ core_missing_or_incorrect_items and core_refunds
Review ✅ core_site_ratings
Commission ✅ core_orders
Delivery Availability ❌ Deliveroo does not include uptime in this feed

Deliveroo orders usually reach Tenzo twice. Your till already records them as sales, so this integration does not import revenue again. It brings in the things only Deliveroo knows: which orders went out wrong, what was refunded and who paid for it, how long each stage of the order took, and what customers said. The Delivery GMV metric exists to put refunds and rates in context — it is not a sales figure and should not be added to your net sales.

Online time is not available for Deliveroo. The report feed Deliveroo sends covers orders, refunds, missing items and ratings, but not how long your tablet was online. If you connect Uber Eats or Just Eat as well, online time will cover those providers only.

Data Ingestion

Real-time optionally available? ❌
Default polling frequency Deliveroo writes a set of files to your own cloud storage each night; Tenzo reads them hourly
Data retrieved on each poll Each day's files contain the previous day's orders, refunds, missing items and ratings
Historical data From the start date entered during setup, as far back as Deliveroo has kept files

Requirements

Deliveroo delivers these reports into a cloud storage bucket that you own. To connect it, Tenzo needs four things:

  • the bucket name and its region;
  • the folder inside the bucket that Deliveroo writes to (often deliveroo/);
  • an IAM role Tenzo can assume, granting read access to that folder;
  • the External ID that role's trust policy requires.

You do not need to create a user or hand over an access key — not having to is the whole reason for this version of the integration. Your Tenzo CSM will give you the exact role permissions and the Tenzo principal to trust.

If your organisation would rather supply an access key and secret than a role, use the Deliveroo AWS integration instead.

What You Will See in Tenzo

  • Inaccuracy rate — the share of completed orders where a customer reported a missing item, an incomplete order or food cooked incorrectly.
  • Refunds — reported separately from inaccuracy, and split into what Deliveroo absorbed and what you did. The restaurant-paid share as a percentage of Delivery GMV is usually the most useful of the two.
  • Delivery rating — your Deliveroo star rating, which appears in the Reviews module under the Deliveroo source alongside your other review platforms.

How Do I Compare Data to Data in Tenzo?

In Deliveroo Hub, open Reports and compare the order count for a site and date range against the Delivery Orders metric in Tenzo.

For accuracy, Hub's Order issues view lists the same orders Tenzo counts in Delivery Inaccurate Orders.

Exceptions

Ratings and refunds arrive after the order they relate to, often a day or two later. A recent day's figures may therefore change for a short while after the fact.

Where an order had several missing items, Tenzo records one issue for the order rather than one per item, so the order counts once toward the inaccuracy rate.

Still need help?

Our support team is ready and waiting to assist.

Contact support