> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/redemptions/understanding-voucher-redemptions-and-how-to-handle-mistaken-redemptions.md).

# Understanding voucher redemptions and how to handle mistaken redemptions

This FAQ is intended for business staff managing customer rewards and redemptions in Perkville. It explains what happens when a customer redeems a reward, the meaning of voucher statuses, and how to handle cases where a customer redeems a reward by mistake.

***

### What happens when a customer redeems a reward?

When a customer clicks the **"Redeem"** button for a reward:

1. **Points are immediately deducted** from the customer’s balance.
2. A [**voucher**](https://docs.perkville.com/features/vouchers.md) **is generated**, allowing the customer to claim the reward from the business.
3. The transaction appears in the customer’s Perkville account and is visible to staff in the [customer's profile](https://docs.perkville.com/features/customers.md#accessing-a-customers-profile).

Even if the customer does not actually use the voucher, the points are already spent at the time of redemption.

***

### What does the "Unused" status mean for a voucher?

A voucher with an **Unused** status means that it:

* Has not been **marked as used** by the business.
* Has not been **manually voided**.
* **Still exists**, but the points are already spent.

**Important:** The "Unused" status does **not** mean that the customer still has the points. It only indicates that the voucher hasn't been used or voided yet.

***

### What should I do if a customer accidentally redeems a reward?

If a customer contacts you saying they redeemed a reward by mistake, and they have not received or used the reward:

1. **Check the** [**customer’s profile**](https://docs.perkville.com/features/customers.md#accessing-a-customers-profile) to confirm that the [voucher](https://docs.perkville.com/features/vouchers.md) is marked as **Unused**.
2. If the customer has not received the reward, [**void the transaction**](https://docs.perkville.com/features/customers.md#voiding-transactions).
3. Voiding the redemption reverses the transaction and **returns the points** to the customer's balance.

Only staff members with the [appropriate permission level](https://docs.perkville.com/features/settings/staff-members.md#staff-member-roles) can void transactions.

***

### Should I void the voucher if the customer already received the reward?

No. If the customer has already received the reward, **do not void the voucher** merely to return the points.

The voucher should only be voided when:

* It was clearly a **mistaken redemption**; and
* The customer **did not receive or use the reward**.

***

### Summary

| Voucher Status | Description                                            | Can points be returned?                                                                                                 |
| -------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **Unused**     | Voucher not yet used or voided. Points already spent.  | Yes, by voiding the redemption transaction when the customer did not receive the reward.                                |
| **Used**       | Voucher has been marked as used.                       | Technically reversible by staff, but it should not normally be voided because the customer already received the reward. |
| **Voided**     | Voucher has been canceled and the redemption reversed. | The points have already been returned.                                                                                  |


---

# 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.perkville.com/faqs/redemptions/understanding-voucher-redemptions-and-how-to-handle-mistaken-redemptions.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.
