> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/integrations/deliveroo/deliveroo-cancellations.md).

# Deliveroo Cancellations

When Deliveroo receives a cancellation request on an order, Deliveroo will get in touch with the site/venue. When the site/venue agrees to a cancellation, Deliveroo will cancel the order on their end and the order's status gets updated in the Boss It POS system to cancelled. Boss It has no control over this process — it simply reflects the status received from Deliveroo.

### Deliveroo's Order Cancelation Process

> Reference: [Deliveroo Documentation](https://api-docs.deliveroo.com/docs/cancelled-orders)

1. A customer places an order.
2. Deliveroo sends the order to the partner and **the partner accepts the order**.
3. While the order is being prepared, the customer calls our Customer Service Team to request cancelation.
4. Our customer service gets in touch with the site.
5. The site agrees to a cancelation. If, for example, the order is running late and hasn't been prepared yet (e.g. the site is facing a high volume of orders).
6. Our customer service agent cancels the order in our system.
7. For tablet-based sites, a cancelation notification appears on the site's tablet.
8. We send the `order.status_update` event with canceled status via the Order Events webhook and the `cancel_order` event via the Legacy POS webhook.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bossithq.com/integrations/deliveroo/deliveroo-cancellations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.