> 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/manage-the-cash-drawer/performing-no-sales.md).

# Perform "no sale" transactions

In retail terminology, a "no sale" transaction refers to opening the cash drawer without actually tendering a sale. There are many reasons for performing a "no sale" transaction. For example, if you are getting low on a particular type of coin in your cash drawer, you might ask a senior cashier or a manager to bring out a roll of coins for you. You would open the cash drawer using a "no sale" transaction and "buy out" the roll of coins using cash from your drawer.

{% hint style="info" %}
You must have the **Allowed to perform No Sales** permission to perform "no sale" transactions in POS.
{% endhint %}

1. Tap **Transaction** | **Sale/Return/No Sale** | **No Sale**.
2. (Optional) If your store requires reason codes for "no sale" transactions, tap the browse icon next to the **Reason Code** field, tap the appropriate reason code to select it, and tap **OK**.
3. (Optional) If your store requires receipts for "no sale" transactions, tap **Yes** to print a receipt.


---

# 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.rmhpos.com/readme-1/manage-the-cash-drawer/performing-no-sales.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.