> For the complete documentation index, see [llms.txt](https://help.trybeans.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.trybeans.com/liana/rules/loyalty.md).

# Loyalty

Use this rule to reward customers with points for placing orders in your store. This is the perfect rule to increase repeat purchases and build customer loyalty. The Loyalty rule allows you to choose the number of points to reward your customers for every dollar spent. We recommend you set it between 5 and 20 points per dollar spent on the store.

Points are calculated based on the value of the order after discounts and before shipping, and taxes. For example, if the subtotal is $100 and the customer uses a coupon code of $20, pays shipping fees of $30, and taxes of $40, they will earn points for $100-20=$80. 

## Settings

![](/files/-Ltytk5H064XGU_gyq7k)

1. **Points:** The number of points a customer gets for spending $1


---

# 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://help.trybeans.com/liana/rules/loyalty.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.