> 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/create-a-collection-schedule/creating-collection-schedule.md).

# Create a collection schedule

1. Click the **Collection** tab.
2. In the **Collection** button group, click **Add**.
3. Enter the **Name** and **Description**, and then select the collection **Type**:

* Price Points
* Basket Points
* Quantity Points

![](/files/Q5n5V7wD5LfqPngIlkFz)

4. Click **Save**.
5. In the **Rules** button group, click **Add**.
6. From the **Rule** drop-down, select the type of rule:

* **Points per unit** (mandatory for Price Points and Quantity Points)
* **Points per Basket Value** (mandatory for Basket Points)
* Include item incentive group(s)
* Include customer group(s)
* Exclude item incentive group(s)

For example, for a price points program, the mandatory rule is points per unit. If you keep the default value of 1, for every dollar they spend the customer will receive 1 price point.

![](/files/rDupskTG77o6YFmDUd7Y)

7. If desired, add other price points rules. Refer to [**Collection rules**](/loyalty-manager/create-a-collection-schedule/collection-rules.md) for more information.

{% hint style="info" %}
If you want to limit the scope of point collection, you may want to include rules for incentive item group(s), and customer group(s). If you do so, only those items and customers defined in the included groups will generate or receive points. If you do not limit the scope of point collection, it means that all items and all customers will generate and receive loyalty points in every transaction.
{% endhint %}

8. Click **Save**.
9. Click **Save**.


---

# 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/create-a-collection-schedule/creating-collection-schedule.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.