> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/discount-coupons.md).

# Discount Coupons

Workflow of a booking confirmation page with the voucher bundle activated

{% hint style="info" %} <mark style="color:blue;">Path: Homepage > All listings > Listing > Booking</mark>
{% endhint %}

* [Definition](#id-1.16.x-bookingconfirmationpages-voucherbundle-definition)
* [Create coupon](#id-1.16.x-bookingconfirmationpages-voucherbundle-createavoucher)
* [Read the coupon display](#id-1.16.x-bookingconfirmationpages-voucherbundle-readthevoucherdisplay)
* [Update a coupon](#id-1.16.x-bookingconfirmationpages-voucherbundle-updateavoucher)
* [Delete a coupon](#id-1.16.x-bookingconfirmationpages-voucherbundle-deleteavoucher)
* [Related resource](#id-1.16.x-bookingconfirmationpages-voucherbundle-relatedresource)

## Definition <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-definition" id="id-1.16.x-bookingconfirmationpages-voucherbundle-definition"></a>

The booking request process is made out of the checkout + the payment process + the final confirmation

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

Logged in users

## Create a coupon <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-createavoucher" id="id-1.16.x-bookingconfirmationpages-voucherbundle-createavoucher"></a>

Users cannot create vouchers.

Learn more on the voucher creation process here: [VCoupon feature - Business rules](/v2.0/core-concepts/coupon-feature.md)

## Read the coupon display <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-readthevoucherdisplay" id="id-1.16.x-bookingconfirmationpages-voucherbundle-readthevoucherdisplay"></a>

A voucher is applied to the booking request’s total amount minus platform fees. The fees are recalculated based on the new booking amount.

Vouchers expire:

* Upon reaching the end date set at its creation
* When the voucher is disabled by authorized administrators

## Update a coupon <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-updateavoucher" id="id-1.16.x-bookingconfirmationpages-voucherbundle-updateavoucher"></a>

Only 1 voucher can be per booking request&#x20;

During the booking request process, a voucher code can be entered on the Checkout Overview page.

The asker enters the voucher code (figure 1) and validates it. The booking summary now displays the updated total price (figure 2).

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/ZpLYDMzp7f0ppHPJwkDx/image.png" alt=""><figcaption><p>Figure 1</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/daiwuoSAfltFSVib2ek3/6988792985.png" alt=""><figcaption><p>Figure 2</p></figcaption></figure>

## Delete a coupon <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-deleteavoucher" id="id-1.16.x-bookingconfirmationpages-voucherbundle-deleteavoucher"></a>

Users cannot delete a voucher.

## Related resource <a href="#id-1.16.x-bookingconfirmationpages-voucherbundle-relatedresource" id="id-1.16.x-bookingconfirmationpages-voucherbundle-relatedresource"></a>

**SBO :**

* [Vouchers management (Coupon feature)](/v2.0/superadmin/coupon.md)

**Business rules:**

* [Coupon feature - Business rules](/v2.0/core-concepts/coupon-feature.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 by asking a question.

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

```
GET https://features.scnd.com/v2.0/front-office/discount-coupons.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.
