> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/readme-1/work-with-vouchers/transactions-selling-vouchers.md).

# Sell vouchers to customers

This topic describes how cashiers and salespeople can sell vouchers, such as gift cards and gift certificates, to customers.

Vouchers can include **gift certificates** and **gift cards**. Gift certificates are typically printed on paper or card stock. Gift cards are typically plastic cards that have a bar code or magnetic stripe. Customers purchase vouchers as a form of prepayment for items or services. Customers typically purchase vouchers as gifts and give them to other people to use.

1. Do one of the following:

* Scan the **voucher barcode** (or enter the barcode number into the lookup field).
* Enter the voucher **item lookup code (ILC)** into the lookup field.

2. If prompted, do one of the following to select or enter the voucher **Serial Number**:

* Scroll through the list of serial numbers and tap the correct one to select it.
* Enter the serial number printed on the voucher into the **serial number lookup field** and press **Enter**.
* Click **Add New #**, enter the serial number printed on the voucher, and press **Enter**.

{% hint style="info" %}
Partial lookup does not work for voucher serial numbers. For example, if the serial number ends with 150, and you type 150 into the serial number lookup field, POS will display a message "Voucher number 150 was not found." You must type the full voucher serial number into the serial number lookup field.
{% endhint %}

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-855c83751850facac6a1ab72df0c6107249c1932%2FPOS_voucher_serial_number.png?alt=media" alt=""></div>

3. Tap **Select**. The voucher is listed as an item on the POS transaction screen.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-4f2a209206fa4887a883d963de453d641259cc62%2FPOS_voucher_item.png?alt=media" alt=""></div>

{% hint style="info" %}
If your store sells vouchers for predefined amounts, e.g., $10, $25, $50, that amount displays in the Price column.
{% endhint %}

4. If prompted, enter the **Price** and tap **OK** or press **Enter**. This is the prepaid amount the customer wants to load on the voucher.
5. Add other items to the transaction as required.
6. Tap **Transaction** | **Tender Sale**. You can also press **F12** or **Enter**.
7. On the **Tender** screen, enter the tender amount next to the relevant tender type.

{% hint style="warning" %}
In POS, a voucher cannot be used to purchase another voucher. If the customer is purchasing a voucher, they must use a different tender type, such as cash, debit card, credit card, or check.
{% endhint %}

8. Tap **OK**.
9. Tap **Yes** to print the receipt.
10. Tap **Yes** or **No** when prompted to print a gift receipt.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-e558501bc0aab530e44e6678a77134c52619a31a%2FPOS_voucher_receipt.png?alt=media" alt=""></div>


---

# 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.rmhpos.com/readme-1/work-with-vouchers/transactions-selling-vouchers.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.
