> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/growth/vouchers-and-membership.md).

# Vouchers & Membership

**Master Data → Vouchers.** One menu, two different uses.

## Discount vouchers

A code the customer enters at checkout to get a price discount. You define:

* **Discount type** — a fixed amount or a percentage.
* **Quota** — how many times the voucher can be used in total.
* **Validity period** — start and end dates.
* **Scope** — which services it applies to, at which branches.
* **Minimum transaction** — the minimum purchase value required to use the voucher.

The quota decreases when the voucher is used, and is **automatically restored** if the booking is cancelled or the payment expires. You don't need to restore it manually.

## Membership

A membership is sold to customers as a package or subscription. Customers buy it through the storefront, and the credits or entitlements are then stored in their account.

What sets it apart from a regular voucher:

* Tied to a specific customer, not a code that can be shared around.
* Can contain a number of visits that decrease with each use.
* Can be set so that bookings made by a membership holder are **confirmed automatically** without waiting for payment per visit.

Manage membership ownership per customer in **Customer → Customer Memberships**.

```mermaid
flowchart LR
  A["Customer buys<br/>package / membership"] --> B["Credit added to<br/>customer account"]
  B --> C["Next booking"]
  C --> D["Credit decreases"]
  D -->|"balance runs out"| E["Buy again"]
```

{% hint style="info" %}
Buying a package is a separate transaction and **does not generate a booking**. The booking is only created when the customer redeems their credit. This is normal and not a sign that any data is missing.
{% endhint %}

## Vouchers for internal bookings

A voucher can also be applied to a booking you create yourself from the portal, for example for a customer who walks in with a physical coupon.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diro.app/en/growth/vouchers-and-membership.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.