> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-shopify/shopify-reference/order-cancellation.md).

# Order Cancellations

Easily manage order cancellations when using both Shopify and HotWax Commerce.

Customers and retailers may need to cancel orders made online for various reasons. If a merchant uses both Shopify and HotWax Commerce, cancellations can occur in two ways:

1. Cancellations made in Shopify and updated in HotWax Commerce.
2. Cancellations made in HotWax Commerce and updated in Shopify.

However, HotWax Commerce suggests canceling orders on Shopify and then updating them on HotWax Commerce, following the same process as used for order creation. This approach ensures that cancellations are handled consistently by both customers and the customer service team. In special cases, such as auto cancellations and mass pre-order cancellations, Shopify retailers can use HotWax Commerce to cancel orders and update them on Shopify.

HotWax Commerce import cancellation updates in two cases:

1. **Full Order Cancellations-** Customers have requested order cancellations from Shopify or CSR teams have canceled orders due to suspected fraudulent orders.
2. **Partial Order Cancellations-** Customers have requested to remove any item from the order or the CSR team canceled the order item due to inventory variance.


---

# 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.hotwax.co/documents/learn-shopify/shopify-reference/order-cancellation.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.