> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/loyalty-program/organizing-earning-rules.md).

# Organizing earning rules

Group earning rules into categories and choose their display order for customers.

Categories keep related earning rules together, while **Display order** controls their sequence. For example, you can group membership tier rules under **Membership rewards** and display Basic, Silver, and Gold together.

### Group rules in a category

1. Open **Settings → Perk Categories**.
2. Select **Create a perk category**.
3. Enter a **Category name**, such as **Membership rewards**.
4. Choose **Earn** as the **Perk type**. You can also set the category's **Display order** to position it among your other categories.
5. Select **Save**.
6. Open each earning rule you want to group and select the same category in its **Category** field. Save each rule and review any confirmation summary.

For membership tier rules, open **Settings → Loyalty Program → Membership tiers**, select the tier, and find **Category** in the **Optional** section. For other earning rules, open **Loyalty Program → Rules & Activities** and select the rule.

Perks assigned to a category are grouped together. Categorized perks appear before uncategorized perks. Use an **Earn** category for earning rules; **Redeem** categories are for redeeming rules.

### Set the display order

1. Open the earning rule you want to position.
2. Enter a whole number in **Display order**. For membership tier rules, this field is in the **Optional** section.
3. Save the rule and review any confirmation summary.
4. Repeat for the other rules you want to arrange. For example, use 1 for Basic, 2 for Silver, and 3 for Gold within the same category.
5. Open your program's earning page to check the result.

Rules with a specified display order appear before rules without one. Rules without a display order are sorted by point value. When using categories, review both the category's display order and the display order of its rules.

### Display order and tier position

[Membership tier rules](/features/earning-rules/membership-tiers.md) have a separate **Tier position** field. These settings serve different purposes:

| Setting       | Purpose                                                                                   |
| ------------- | ----------------------------------------------------------------------------------------- |
| Category      | Groups related rules together for customers.                                              |
| Display order | Arranges how rules appear to customers.                                                   |
| Tier position | Defines the membership hierarchy used to determine which lower-tier rewards are included. |

Set **Tier position** to 1 for the entry tier and use higher, unique numbers for higher tiers. Changing a category or display order does not change the membership hierarchy. Keep the customer display consistent with that hierarchy so members can follow the progression.


---

# 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.perkville.com/features/settings/loyalty-program/organizing-earning-rules.md?ask=<question>&goal=<user_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.