Menu
HubRise

Sending Orders

Connecting Deliveroo to HubRise allows you to receive Deliveroo orders directly in your EPOS. This page describes the information that is passed by Deliveroo Bridge for the orders you receive.

Items and Options

For items and options, Deliveroo provides either the ref code or the name, but never both at the same time.

  • If you specify the item or option ref code in your Deliveroo back office, Deliveroo API will only send this information to HubRise.
  • If you do not specify the item or option ref code in your Deliveroo back office, Deliveroo API will send the item or option name to HubRise, instead.

If your EPOS solution relies on item and option ref codes to correctly parse the item, make sure that items and options in your Deliveroo menu are mapped to the correct EPOS ref code. For more details, see Map Ref Codes.

Otherwise, if your EPOS solution does not support ref codes, leave this information blank in your Deliveroo back office.

Customers' comments on single items are not provided by Deliveroo API. If you rely on these comments for cooking or serving instructions (for example, "Medium rare cooking", or "Cut in slices"), you should add the corresponding items in your EPOS and include them as options in the Deliveroo menu, so that they are correctly encoded.

Items Encoding

For every item in the order, Deliveroo Bridge provides the following information:

  • sku_ref: The ref code of the item.
  • product_name: The ref code of the item, if present. Otherwise, the item name.
  • price: The price for a single item.
  • quantity: The quantity of items included in the order.
  • options: The array of options attached to the item.

Options Encoding

For every option in the order, Deliveroo Bridge provides the following information:

  • option_list_name: The default value is "Options".
  • ref: The ref code of the option.
  • name: The ref code of the option, if present. Otherwise, the option name.
  • price: The price for a single option.

Every option has single quantity. Multiple identical options are encoded in separate option objects.

Order Statuses

A Deliveroo order goes through several statuses during its lifecycle.

Changes to the order status originating from Deliveroo are reflected in HubRise in the following way:

  • New orders are created on HubRise with status new.
  • When an order is cancelled on Deliveroo, it is automatically marked as cancelled on HubRise.

When an order status changes on HubRise, Deliveroo Bridge notifies Deliveroo and the change is reflected in the tablet. The supported status values are the following:

  • accepted: The order has been accepted by the EPOS, and is confirmed on Deliveroo.
  • in_preparation: The order is in the kitchen.
  • awaiting_collection: The order is ready for pickup by the customer or the rider.
  • completed: The order has been collected by the customer or the rider.

Other HubRise status values are not supported and are not sent on Deliveroo.

Service Types

Deliveroo supports three service types:

  • Delivery by Deliveroo riders
  • Delivery by the restaurant's fleet
  • Customer collection

These are typically associated with specific ref codes in your EPOS. For more information, see your EPOS documentation in our apps page.

Customer Details

Deliveroo never provides the customer's full name and email address in their API. It only provides the customer's address for orders delivered by the restaurant.

Therefore, Deliveroo Bridge never creates customers in HubRise for Deliveroo orders, but always includes the customer's details directly in the order.

Customer Name and Email

Customer's name and email for Deliveroo orders have these default values for all types of orders:

Customer Address

For restaurant delivery orders only, Deliveroo Bridge retrieves the following information from Deliveroo:

  • address_1: The first line of the address.
  • address_2: The second line of the address.
  • city: The city of the address.
  • postal_code: The postcode of the address.
  • latitude: The latitude of the address.
  • longitude: The longitude of the address.
  • phone: Deliveroo support number. Note: This is not the customer's phone number.
  • delivery_notes: The access code to identify the order when calling Deliveroo support and the delivery notes left by the customer, in the format "Phone access code: access_code. note".

Discounts

The discount applied to the order is passed in a single object in the HubRise discounts array.

The available fields in the payload are the following:

  • name: The name of the discount, which is "Discount" by default.
  • ref: The ref code of the discount. Its default value can be set from the Configuration page of Deliveroo Bridge and should match the value in your EPOS.
  • price_off: The total amount of the discount.

Charges

Deliveroo Bridge encodes two types of charges: Delivery charges, and small order surcharges.

Delivery Charges

Delivery charges are applied for orders delivered by the restaurant.

The available fields in the payloads are the following:

  • name: The name of the delivery charge, which is "Delivery charge" by default.
  • type: The type of charge. It has always the value delivery.
  • ref: The ref code of the charge. Its default value can be set from the Configuration page of Deliveroo Bridge and should match the value in your EPOS.
  • price: The total amount of the delivery charge.

Small Order Surcharges

Small order surcharges, applied when the total price for an order is below the minimum order price.

The available fields in the payloads are the following:

  • name: The name of the charge, which is "Surcharge" by default.
  • type: The type of charge. It has always the value other.
  • ref: The ref code of the charge. Its default value can be set from the Configuration page of Deliveroo Bridge and should match the value in your EPOS.
  • price: The total amount of the small order surcharge.

Customers' Notes

Customers' notes about the order are encoded in the customer_notes field.

Feedback on this page