> 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/incentive-groups.md). # Incentive groups An **incentive group** (also called an item group) is a mechanism to group items for the purpose of implementing unique collection and redemption settings for that group. Incentive groups can be either included in (or excluded from) collection schedules and redemption schedules. Using incentive groups is optional. If a collection schedule or redemption schedule do not include an incentive group, it means that the collection schedule or redemption schedule applies to all items indiscriminately. An incentive group may contain individual items or all items assigned to specific departments or categories. You can create multiple incentive groups. Although it is possible to add individual items or all items assigned to specific departments or categories to more than one incentive group, adding items to multiple incentive groups should be used with caution. Make sure that there is no clash between the loyalty programs that inherit these incentive groups from the respective collection and redemption schedules. --- # 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/loyalty-manager/loyalty-concepts/incentive-groups.md?ask=&goal= ``` `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.