> 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/points-and-ways-to-earn/award-points-for-repeat-product-purchases.md).

# Award points for repeat product purchases

Award bonus points every few products a customer buys, counted across their orders, with control over which purchases and which products count.

The **Product Purchase Rewards** way to earn pays points each time a customer's product count reaches the next multiple, for example 100 points at 3 products, again at 6, and again at 9.

It counts **products, not orders**. A customer who buys three in one go reaches the reward just as fast as one who buys three times, so there is nothing to gain from splitting an order.

You choose which purchases count, which products count, and the date counting starts.

### Set it up

In **Loyalty Program → Points**, click **Add way to earn** and choose **Product Purchase Rewards**.

{% hint style="warning" %}
You can configure one Product Purchase Rewards earner per program. Once you have one, the type appears dimmed in the **Add way to earn** list.
{% endhint %}

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FFMaoKLTDOqb0S3N4Regz%2FScreenshot%202026-10-28%20at%2010.04.40%E2%80%AFAM.png?alt=media&amp;token=a700d8d9-e92c-4758-8faa-8ae5cef1c191" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Reward

Set **Products per reward** to the number of products that earns a reward, and **Points awarded** to the points paid each time.

For 100 points on every third product, that is `3` products and `100` points.

Then set the **Display name** and **Description** customers see in the storefront loyalty widgets.
{% endstep %}

{% step %}

#### Products

This is where you decide what the rule actually counts.

**Purchases that count** is a choice of three:

* **Subscription and one-time purchases**
* **Subscription purchases only**
* **One-time purchases only**

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FvEOQExE3oI3CnwB3v8YE%2FScreenshot%202026-10-28%20at%2010.04.58%E2%80%AFAM.png?alt=media&amp;token=5133209a-84a0-4ee2-acde-31462c0cd13e" alt=""><figcaption></figcaption></figure>

**Products that count** narrows it further, to specific products or a collection. Leave it blank to count every product you sell.

A collection is usually the better choice of the two, because you can add and remove products in Shopify without coming back to the rule.
{% endstep %}

{% step %}

#### Counting

**Count orders placed on or after** sets the date counting begins. Orders placed before it are never counted.

You can choose today or a future date. An existing rule keeps whatever date it was saved with, but once you set the earning rule to active, you cannot set it back to an earlier date.
{% endstep %}

{% step %}

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F8XgcF2prbaMWESsFu89u%2FScreenshot%202026-10-16%20at%201.11.20%E2%80%AFPM.png?alt=media&amp;token=cc2c081e-522b-4890-bb55-ee34ceab207d" alt="" width="563"><figcaption></figcaption></figure>

#### Icon

Choose **Use default icon**, or **Upload your own icon** for the storefront tile.
{% endstep %}

{% step %}

#### Membership tier eligibility

Leave this empty to allow all customers, or select tiers to restrict the reward to those members only.

Read the tier rule below before you use it, because it behaves differently from the other ways to earn.
{% endstep %}

{% step %}

#### Check the Summary and activate

The **Summary** panel on the right restates the rule in plain English, including what counts, the counting date and the refund behaviour. Read it back before you go live; it is the quickest way to catch a reward you did not mean to configure.

Set **Status** to **Active**, and **Storefront widget display** to **Visible** or **Hidden**. A hidden earner still awards points.
{% endstep %}
{% endstepper %}

### How the count works

The count is the total number of qualifying product units a customer has bought on orders placed since the counting date, less any products that have since come off those orders.

A reward is paid each time that count reaches the next multiple of your **Products per reward** setting. At `3`, that is 3, 6, 9 and onward.

* **Extra products carry forward.** The count never resets. A customer who buys 4 products is paid once, at 3, and starts the next reward one product in.
* **One order can pay more than one reward.** A count that goes from 2 to 8 passes 3 and 6, and both rewards are paid on that order.
* **The count follows the rule's current settings.** Any changes to the earning rule change the count immediately.

The count moves when the order is placed, not when it is fulfilled. You can see where any customer currently sits in **Product purchase count**, on their loyalty profile.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Ft8x10A1yyB94BnWYPRzg%2FScreenshot%202026-10-28%20at%2010.38.39%E2%80%AFAM.png?alt=media&amp;token=a2ca83d5-2a0b-49d0-be22-7a16b5ac3c4d" alt="" width="303"><figcaption></figcaption></figure>

The same figure appears on each of that customer's subscription contracts, in the **Customer Subscription History** card, listed as **Loyalty rewards count**. That card totals across all of their subscriptions, so it reads the same on every contract they hold.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F8KoG2GEnI4PhJ4uoq0Hu%2FScreenshot%202026-10-28%20at%2010.48.04%E2%80%AFAM.png?alt=media&amp;token=c4b5975c-fb85-4396-bc45-39be6a72d92b" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Subscription orders** and **Subscription products** in that same card are lifetime totals for the customer, and are not what this reward counts. Expect them to be higher, since the reward counts only qualifying products bought since your counting date.
{% endhint %}

{% hint style="info" %}
A few smaller rules worth knowing. Draft orders count. Products count whatever they cost, including free ones. Guest orders with no customer record count for nothing, since there is nobody to award.
{% endhint %}

### Tier eligibility is judged before the order

If you restrict this reward by tier, eligibility is decided on the tier the customer held **before** the order was placed, not the tier they end up in afterwards.

So an order that promotes someone into an eligible tier does not itself earn the reward. Their next qualifying purchase does.

{% hint style="info" %}
Products bought while the customer was in an ineligible tier **still count** toward their total. They are not earning yet, but they are not starting from zero either.
{% endhint %}

A reward missed this way is not paid retrospectively when the customer is later promoted. This is worth explaining to customers if you run a tier-restricted version, because it is the one part that reliably generates a support ticket.

### Refunds, returns and order edits

What matters is whether the product comes off the order. If it does, it stops counting. If it stays on the order, the count does not move, whatever the customer gets back.

If the count does drop back below a reward you have already paid, those points are taken back in full, even if the customer has since spent part of their balance. If no reward had been paid at that point, nothing is taken back.

#### Products you have not fulfilled yet

On Shopify's **Refund** screen, the quantity box against each line is what decides it.

* **Refunding quantity takes the product off the order, so the count drops.** Set a line to 1 of 1 and that unit leaves the count. A full refund of the order takes every product on it.
* **A custom discount leaves the product where it is, so the count holds.** Leave the quantity at 0 and apply a **Custom discount** instead. The line keeps its product at a lower price, the customer still has it, and it still counts.

#### Products you have already fulfilled

Fulfilled products go through a return rather than a straight refund, and the count waits for that return to finish.

While the order shows **Return in progress**, nothing changes. The product is still on the order and still counts, even though you are expecting it back. The count drops only once the return is closed, which is when you click **Process and refund**.

So if a customer is close to a reward and returns something, expect their count to hold until you close the return off, not from the moment they request it.

#### Cancellations and order edits

Cancelling an order, or removing a product in the order editor, also takes those units out of the count.

An order edit is checked the moment you save it. It does not wait for money to be refunded, and it applies even if the payment has not been captured yet.

For example, take a customer on 7 products who has been paid a reward at 6. You edit their order to remove two products. The count drops to 5, and the points for the reward at 6 come back off the balance there and then.

### Changing the rule later

This is the part worth reading before you edit a live rule.

Changing **Purchases that count**, **Products that count**, or **Products per reward** recalculates every customer's count straight away, and makes rewards already paid **final**. Those points are kept even if the count later drops below them, and the same reward cannot be earned again.

{% hint style="warning" %}
Editing only the points, the display name or the tier eligibility does **not** count as that kind of change, so earlier rewards stay open to being taken back if the count drops.
{% endhint %}

Two more consequences are easy to miss:

* **Raising Products per reward pushes the next reward further out than you might expect.** Rewards are tracked by number rather than by the count they sit at. Going from 3 to 5 for a customer already on 7 means their next reward lands at 15, not 10. Lowering it can pay several rewards at once on the next order.
* **If the count passes a reward without an order, the next order pays it.** Saving the rule, adding a product to the counted collection in Shopify, or orders placed while the rule was in draft can all push a count past a threshold. Nothing is paid at that moment, but the customer's next order settles it.

Changing the **counting date** behaves differently. Rewards above the recalculated count are released: the points already paid stay with the customer, and those rewards can be earned again.

### What the loyalty timeline shows

Every outcome is written to the customer's loyalty timeline, with the counts spelt out so you can see exactly what happened:

* **Earned** — the points paid and the products that triggered them, with the order and the count before and after.
* **Not earned** — when the customer's tier was not eligible, or when the reward had already been earned, the entry says which and confirms the purchases still counted.
* **Reward removed** — names the order, the count before and after, and the reward the points had been paid for, for example "took products purchased from 7 to 5, below the 6 this reward was paid for".
* **Reward not reversed** — logged when the count drops past a reward that was paid under the rule's earlier settings, so the points stay with the customer.
* **Nothing to remove** — logged when the count drops but no reward had been paid at that point.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FnaFoH73E2jxD2xRixCOm%2FScreenshot%202026-10-28%20at%2010.31.50%E2%80%AFAM.png?alt=media&amp;token=f871f292-5e21-4c8a-8368-51c544835963" alt="" width="298"><figcaption></figcaption></figure>

An order that pays several rewards writes one entry. A drop that crosses several rewards writes one entry for each, so you can see what happened to every one.

Point History shows the same thing in the **Details** column, as a reward against a product count, and as a reversal where points were taken back.

### Current limits

* One Product Purchase Rewards rule per store.
* Counting runs all-time from the counting date. There are no yearly or rolling windows.
* There is no cap on how many rewards one customer can earn.

### Related guides

* [Ways to earn points: overview](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/ways-to-earn-points-overview.md)
* [Reward subscribers with loyalty points](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/reward-subscribers-with-loyalty-points.md): the tag-based alternative, for rewards this earner cannot express
* [Award points for placing an order](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/award-points-for-placing-an-order.md)
* [Understanding a customer's loyalty timeline](https://docs.roadmap.so/loyalty-and-rewards/customer-management/understanding-a-customers-loyalty-timeline.md)
* [Managing point adjustments post-fulfilment](https://docs.roadmap.so/loyalty-and-rewards/points-and-ways-to-earn/managing-point-adjustments-post-fulfilment.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/points-and-ways-to-earn/award-points-for-repeat-product-purchases.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.
