> 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/loyalty-manager/loyalty-concepts/loyalty-batch.md). # Loyalty batch This topic explains the role of the loyalty batch. A **loyalty batch** is a set of loyalty transactions that is completed when a reward is received. If a customer participates in one or more loyalty programs, he or she always have one open batch per loyalty program and a history of the closed batches. Each closed batch signifies that the customer has received a redemption for that loyalty program. The very first batch for a loyalty program is created when the customer has collected their first loyalty points in that program. The batch is closed when the redemption was received. By counting the number of the closed batches per customer, the manager knows how many rewards the customer has received and for which loyalty program type. {% hint style="info" %} If not all points are used for the reward and the batch is to be closed because the redemption has been received, the remainder of the points is transferred to the newly opened loyalty batch of the same **loyalty program**. {% endhint %} --- # 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/loyalty-manager/loyalty-concepts/loyalty-batch.md?ask=&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.