> 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/process-a-basic-transaction/bag-fees-collecting.md).

# Collect bag fees

This topic describes one method for collecting bag fees. Your store may have different methods for collecting bag fees. Refer to your store's policies and procedures for more information.

Stores may collect bag fees from customers who require bags to carry their purchases out of the store. You must inform customers of any applicable bag fees and get their consent to pay the fees before adding bag fees to a transaction.

{% hint style="info" %}
Follow your store's policies and procedures for collecting bag fees.
{% endhint %}

{% hint style="warning" %}
This procedure assumes that the store is using a custom command button in POS that adds a bag item. There are many ways to add bag items to transactions. Follow your store's procedures for adding bag items to transactions in POS.
{% endhint %}

1. Enter all items in the transaction.
2. If the customer requests bags for their purchase:
   1. Confirm that the customer is willing to pay the applicable bag fees.
   2. Add a bag item to the transaction.
   3. (Optional) If the customer requires more than one bag, tap **Action** beside the bag item and change the bag quantity.

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

3. Tender the transaction.

The bag item (and the associated bag fees) display on the 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-26bc11405937615ec71e3f0a9e36b90cb31ce584%2FPOS_bag_fee_collecting_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/process-a-basic-transaction/bag-fees-collecting.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.
