> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/playbook/faq/returns-and-cancellations.md).

# Returns and Cancellations

### How do I handle points deduction on returns and cancellations?

You can set up single or multiple campaigns for return transactions, with a reverse logic to your current campaigns. To find out more about this type of campaign, please refer to the article below.

{% content-ref url="/pages/tF02RJHopYvKMvWypApc" %}
[Broken mention](broken://pages/tF02RJHopYvKMvWypApc)
{% endcontent-ref %}

***

### Is the progress reverted once a return is made?

At the moment, return transactions work as a separate flow. It does not revert the member’s status or tier if it was affected by the original transaction, nor adjusts campaign limits or counters that were impacted by the initial purchase.


---

# 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 dynamically by asking a question.

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

```
GET https://help.openloyalty.io/playbook/faq/returns-and-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 `build a script that syncs our docs to a CMS` 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.