> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/gerer-les-reservations-avec-yoplanning/vendre-un-ou-plusieurs-bons-cadeaux.md).

# sell one or more gift vouchers

Make a manual sale in the back office for one or more gift vouchers.

***

### When to use manual selling?

The customer is at the counter, on the phone, or you're processing a gift voucher without using the online booking system. The sale is done manually via an order.

### Steps

1. **Open an order**: either an existing customer order, or a **blank order** — menu **Orders** → three small dots in the top right corner → **Create a blank order**.
2. **Provide customer information** (name, email…): the voucher will be linked to them.
3. Click on **“Sell a voucher”**.
4. **Choose the correct one** from the list. It contains all the vouchers configured for your products, as well as your prepaid plans.
5. **Check the price and quantity**, then confirm.
6. **Collect** the order and **send the ticket** to the customer: it contains the **code** to use for the reservation.

### Selling multiple gift vouchers

To sell multiple vouchers to the same customer, repeat the **“Sell a voucher”** operation as many times as necessary on the same order: each voucher generates its own code, and the customer receives one ticket per voucher.

You can also adjust the **quantity** when selling a classic gift voucher: the system then issues as many vouchers — therefore as many codes — as the quantity requested.

### Case of the voucher book

If the selected voucher is a [voucher booklet](file:///yoplanning-academie/yoplanning-parametrage/parametrage-produit/les-forfaits-prepayes-bons-cadeaux-cheques-cadeaux/carnet-de-bons.md) (multiple uses included), the screen changes slightly:

* the price field becomes **"Price for 10 uses"**: this is the price of the complete booklet, not the price of one session;
* The quantity is occupied by the number of uses of the notebook — so you sell **one notebook at a time**. For two notebooks, repeat the operation.

The customer receives **a single code**, valid as many times as the booklet contains uses.

### Follow up

All vouchers sold, manually or online, are visible in the **Vouchers** menu: code, customer, expiry, status (*Valid*, *Partially Used*, *Used*, *Expired*) and counter "Remaining: X / Y" for booklets.

### Namely

* The voucher must already exist in the product sheet (section **Gift voucher**) to appear in the list.
* The expiry date is calculated from the **validity in months** set on the voucher; you can adjust it at the time of sale.
* To use a voucher already sold on an order, see [Use a Customer's Credit or Prepaid Package](file:///yoplanning-academie/yoplanning-au-quotidien/manipulation-et-gestion-des-commandes-dans-yoplanning/utiliser-le-credit-ou-le-forfait-prepaye-dun-client.md).


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/gerer-les-reservations-avec-yoplanning/vendre-un-ou-plusieurs-bons-cadeaux.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.