Receive Orders

Connecting Wolt to HubRise allows you to receive Wolt orders directly in your EPOS or any other solution connected to your HubRise account.

This page describes the information Wolt sends to HubRise and how delivery information is synchronised between the two platforms. It helps you understand how orders will be received on your EPOS and how delivery tracking works.

Order Transmission

Wolt sends orders to HubRise immediately when they are placed by the customer.

Orders can be either instant orders or pre-orders (scheduled orders):

• Instant orders: Should be prepared immediately and delivered or picked up within the standard preparation time.
• Pre-orders: Have a scheduled pickup or delivery time specified by the customer.

Order Statuses

---

IMPORTANT NOTE: In this section, we capitalise the first letter of Wolt statuses to make them easier to distinguish from HubRise status names. For example, Created is a Wolt status, while new is a HubRise status.

---

Wolt Statuses

Wolt orders go through several statuses during their lifecycle:

• Created: The order has been placed.
• Sent to POS: The order has been acknowledged by the EPOS. This status is used by Wolt for troubleshooting.
• Confirmed (pre-orders only): Confirmed pre-orders are automatically accepted by Wolt as the scheduled time approaches, based on preparation time. Wolt does not specify a time limit for confirming pre-orders.
• Accepted: Instant orders must be accepted within 3 minutes, or they will be automatically cancelled by Wolt.
• Ready: The order is awaiting pickup or delivery.
• In Delivery (delivery orders only): The courier has picked up the order and is en route to the customer.
• Courier at Customer (restaurant delivery only): The restaurant courier has arrived at the customer's location.
• Delivered: The order has been delivered to the customer or picked up.
• Canceled: The order has been cancelled by the customer, restaurant, or Wolt.

When the Status Changes in HubRise

When an order status changes in HubRise, Wolt Bridge notifies Wolt of the change according to the following mapping:

HubRise status	Wolt status
new (order creation)	Accepted or Confirmed, if configured (*).
received	Sent to POS. Can also trigger Accepted or Confirmed, if configured (*).
accepted	Accepted or Confirmed, if configured (*).
rejected	Canceled. The order is rejected with a predefined reason.
cancelled	Canceled. The order is cancelled with the reason from seller_notes, or a predefined message.
awaiting_shipment or awaiting_collection	Ready.
in_delivery (restaurant delivery only)	In Delivery.
completed (restaurant delivery or takeaway)	Delivered.

Other HubRise status values are not supported and are not sent to Wolt.

(*): Wolt Bridge lets you decide which HubRise status triggers the transition to the Accepted status in the Order statuses section of the Configuration page. The available options are:

• Immediately when they are sent to HubRise.
• When their HubRise status changes to received.
• When their HubRise status changes to accepted.

How orders are accepted depends on the order type:

• Pre-orders: The bridge confirms the pre-order, which is then automatically accepted by Wolt as the delivery time approaches, based on preparation time.
• Restaurant delivery: The bridge accepts the order with an optional delivery time from the confirmed_time field.
• Delivery by Wolt: The bridge accepts the order with an optional pickup time adjustment from the confirmed_time field. The adjustment cannot exceed 25 minutes from the original estimate.
• Takeaway orders: Same as Delivery by Wolt orders.

When the Status Changes in Wolt

When an order status changes in Wolt, Wolt Bridge updates the corresponding order in HubRise:

Wolt status	HubRise status
Ready (for venues using Wolt tablets)	awaiting_shipment (for delivery) or awaiting_collection (for takeaway)
In Delivery (delivery by Wolt only)	in_delivery
Delivered	completed
Canceled	cancelled

Delivery Tracking

Wolt Bridge keeps Wolt and HubRise in sync for delivery progress. The direction of updates depends on who provides the courier.

Delivery by Wolt

When an order delivered by Wolt is accepted, Wolt Bridge creates a Delivery resource in HubRise with the following information:

• carrier: Set to "Wolt"
• status: Set to pending
• estimated_pickup_at: The estimated time when the courier will pick up the order

When a Wolt courier is assigned to the order, the delivery is updated with the following information:

• status: Updated to pickup_enroute
• estimated_pickup_at: Updated with the courier's estimated arrival time

When the courier picks up the order, the order status in HubRise is updated to in_delivery.

Restaurant Delivery

For orders delivered by the restaurant's own fleet, the bridge relays the status updates from HubRise to Wolt as follows:

HubRise order status	HubRise delivery status	Wolt status
in_delivery	-	In Delivery
-	dropoff_waiting	Courier at Customer
completed	-	Delivered

Service Types

Wolt supports three service types:

• Delivery by Wolt
• Restaurant delivery
• Takeaway

These are typically associated with specific ref codes in your EPOS, which you can set in the Configuration page of the bridge. For more information about ref codes, see your EPOS documentation in our Apps page.

Order Times

The timing information provided in HubRise depends on whether the order is an instant order or a pre-order.

Instant Orders

For instant orders, the expected_time field is not populated, as these orders should be prepared as soon as possible. If the order is delivered by Wolt, the Delivery object's estimated_pickup_at field is populated with the courier's estimated pickup time as soon as a courier is assigned.

To adjust the pickup or delivery time, update the confirmed_time field in HubRise before or at the same time the order is accepted in Wolt. The adjusted time cannot be more than 25 minutes later than the original estimate.

Pre-Orders

For pre-orders (scheduled orders), the expected_time field is set to the scheduled pickup or delivery time selected by the customer.

The pickup or delivery time for pre-orders cannot be adjusted.

Customer

Wolt provides limited customer information. The amount of information varies depending on the order type.

Wolt Bridge does not create customers in HubRise, but includes the customer's details directly in the order.

For every type of order, Wolt Bridge sends the following information in the customer object:

• first_name: The customer's first name, or first part of the name.
• last_name: The rest of the customer's name (if full name is enabled) or just the initial.
• email: The customer's email address (when provided).
• phone: The customer's phone number (when provided).
• company_name: The company name for business orders (when provided).

Additionally, for restaurant delivery orders, Wolt Bridge sends the following fields:

• address_1: The street address.
• address_2: The apartment number, formatted as "Apartment n. X" if provided.
• postal_code: The postcode.
• city: The city name.
• country: The two-letter ISO country code.
• latitude: The latitude of the delivery address.
• longitude: The longitude of the delivery address.
• delivery_notes: Delivery instructions from the customer, extracted from the formatted address field.

Items and Options

Wolt orders can include either single items with options or deal items (special offers that bundle multiple products together).

Single Items Encoding

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

• sku_ref: The ref code of the item.
• product_name: The product name.
• price: The price for a single item, before discounts.
• quantity: The quantity of items included in the order.
• tax_rate: The VAT percentage.
• options: The array of options attached to the item.

Deal Items Encoding

When an order contains a deal (a bundled offer), Wolt Bridge encodes it differently:

• Each product in the deal becomes a separate item in the HubRise order.
• All items belonging to the same deal are linked together with a deal_line reference.
• The minimum price of the deal, calculated from all possible deal line combinations, is included in the first item's price.
• Each subsequent item includes only the price difference from the minimum deal price.

The deal information is stored in a deals object with:

• name: The name of the deal.
• ref: The ref code of the deal.

Options Encoding

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

• option_list_name: The name of the option group.
• name: The option name.
• ref: The ref code of the option.
• price: The price for a single option, before discounts.
• quantity: The quantity of the option.

Discounts

Wolt orders can include two types of discounts: basket discounts and delivery fee discounts.

Basket Discounts

When a customer receives a discount on their order items, Wolt aggregates all item-level discounts into a single total discount. Wolt Bridge encodes this in a single discount object with the following fields:

• name: Set to Discount.
• ref: The ref code of the discount. Its value can be set from the Configuration page and should match the value in your EPOS.
• price_off: The total amount of the discount applied to the basket.

Delivery Fee Discounts

When a discounted delivery fee is applied to an order, Wolt Bridge encodes the corresponding discount with the following fields:

• name: Set to Delivery fee discount.
• ref: The ref code of the delivery fee discount. Its value can be set from the Configuration page and should match the value in your EPOS.
• price_off: The amount of the delivery fee discount.

Charges

Wolt Bridge encodes various types of charges depending on the order type and applicable fees. All charges include the following fields:

• name: The name of the charge.
• ref: The ref code of the charge. Its value can be set from the Configuration page and should match the value in your EPOS.
• price: The charge amount.
• tax_rate: The VAT percentage applied to the charge.

Delivery Charges

Wolt Bridge encodes all delivery-related charges using the same ref code, which can be configured in the Configuration page.

Delivery charges may include, the base delivery fee, an extra distance delivery fee, and a priority delivery fee.

Delivery Tip

When a customer adds a tip for the courier, Wolt Bridge encodes it as a charge with the ref code for tips, configured in the Configuration page.

Other Charges

Other types of charges that may be included in Wolt orders are:

• Service fee
• Small order surcharge, applied when the order value is below the minimum order amount.
• Marketing campaign fee

Each of these charges can have its own ref code configured separately in the Configuration page.

Payments

Wolt supports two payment methods: online payment and cash payment. Wolt Bridge encodes the corresponding payments with the following fields:

• name: Either Online payment or Cash payment.
• ref: The ref code for the payment method. Its value can be set from the Configuration page and should match the value in your EPOS.
• amount: The amount paid using this payment method.

Customer Notes

Order-level customer notes left by the customer at checkout are encoded in the customer_notes field. These notes typically contain special requests or instructions for the restaurant.

Note that delivery instructions for restaurant delivery orders are provided separately in the delivery_notes field of the customer object, not in the order-level customer_notes.

Pause

When order acceptance sync is enabled in the Configuration page, Wolt Bridge syncs the order_acceptance field from HubRise to Wolt.

The order_acceptance.mode field controls the store status:

• normal or busy: Store open
• paused: Store paused with optional scheduled resume time

When the store is paused, you can optionally specify a resume_at time in HubRise, and Wolt will automatically reopen the store at that time.

---

IMPORTANT NOTE: Wolt does not support updating preparation time via API. Preparation times must be managed directly in the Wolt dashboard.

---