> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/troubleshooting/points-on-an-order-only-came-from-one-earning-rule.md).

# Points on an order only came from one earning rule

Why an order awarded points from a single Place an order rule when two rules with different product eligibility were active — and what's changing.

An order can qualify for two **Place an order** earners with different product eligibility. Roadmap applies the most generous eligible rule.

#### Why this happens

Roadmap applies one **Place an order** configuration per order. This keeps earning predictable and prevents rules from stacking on the same items.

For example, if an order includes a double-points collection item, the double-points rule applies. The default rule does not also award points for remaining items.

#### What to do today

* For storewide promotions, set product eligibility to **All products earn points**.
* For collection promotions, mixed orders use the most generous matching rule. Use a storewide promotion when full coverage matters most.

{% hint style="success" %}
This behavior is being enhanced. An upcoming update will let orders earn from multiple **Place an order** configurations. Check the in-app **Change Log** for updates.
{% endhint %}

#### Related guides

* [Run a double-points promotion](/loyalty-and-rewards/points-and-ways-to-earn/run-a-double-points-promotion.md)
* [Award points for placing an order](/loyalty-and-rewards/points-and-ways-to-earn/award-points-for-placing-an-order.md)


---

# 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.roadmap.so/loyalty-and-rewards/troubleshooting/points-on-an-order-only-came-from-one-earning-rule.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.