> 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/collection-types.md).

# Collection types

There are three different types of collection schedules:

* Price points (PP)
* Basket points (BP)
* Quantity points (QP)

The collection type defines what triggers loyalty value accumulation.

### **Price points**

In price points loyalty collection the trigger is the item’s purchase price. Ultimately, the number of collected loyalty points depends on how much money the customer spends at the store. The points are awarded based on the item’s price. For example, for each $1 get 1 loyalty point.

### Basket points

Basket points loyalty collection forces the loyalty program to look at the transaction subtotal. With this type of loyalty collection, the merchant awards the customer with a certain number of points only when the transaction subtotal (basket size – hence the name) reaches a certain value; otherwise the customer receives no points. By gradually raising the basket value over time, the merchant will encourage a higher average ticket. For example, spend $30 – get 10 points; spend less – get no points.

{% hint style="info" %}
Basket points is per-visit type of loyalty. Basket points collection type can also be used to award customers with points per visit. For example, create a collection schedule of the basket points type, and select $1 as the trigger to award 100 points. That means that each time the customer visits the stores and purchases anything worth more than $1, they will be awarded 100 points.
{% endhint %}

### **Quantity points**

With quantity points the loyalty points are awarded per item count, over a period of time. For example, buy 1 medium bag of dog food – get 1 point.


---

# 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/collection-types.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.