> 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/a-discount-is-smaller-than-the-points-value-shown.md).

# A discount is smaller than the points value shown

A customer redeemed points and the discount on their order was smaller than the value shown against the redemption. Here is why, and how to fix it.

**Symptom:** a customer redeemed points, their loyalty history shows the reward as one amount, and the order applied a smaller discount. For example, the history reads **500 points / €30** and the order shows **€25.47 off**.

This happens on stores selling into more than one market through Shopify Markets.

### Why this happens

The two figures come from different places.

* The **€30 in their history** is a display figure. It comes from the rate you entered for that market under **Loyalty Program** → **Points** → **Currency Conversion**.
* The **discount on the order** is the real value of the code, which is a fixed amount of your store's base currency. Shopify converts it into the customer's currency at checkout, at its own exchange rate.

If the display rate you entered is more generous than the live exchange rate, the customer sees the larger number first.

In the example above, the EUR market was set to 100 points = €6, which assumes 1 NZD is worth €0.60. The real rate was closer to €0.50, so a $50 NZD reward converted to €25.47 rather than €30.

### How to fix it

1. Go to **Loyalty Program** → **Points** → **Currency Conversion**.
2. For each market, work out the display rate from your default rate and the current exchange rate. A default of 100 points = $10 NZD at a rate of 0.50 means the EUR market should be near 100 points = €5.
3. Round down rather than up, so the figure customers see is slightly conservative.
4. Click **Save**.
5. Review these rates periodically. They are fixed numbers you enter, not live rates.

{% hint style="info" %}
Changing a market's display rate does not alter points already earned or rewards already issued. It only changes the money figure shown alongside points.
{% endhint %}

### What this is not

* It is not a discount code failing to apply in full. The code applied correctly, for its full base currency value.
* It is not a tax or shipping difference.
* It is not something a different reward setup would avoid. Every reward is valued in your base currency.

### Related articles

* [How loyalty works across multiple currencies](/loyalty-and-rewards/getting-started/how-loyalty-works-across-multiple-currencies.md)
* [How to configure your point settings](/loyalty-and-rewards/getting-started/how-to-configure-your-point-settings.md)
* [A customer's loyalty coupon isn't working](/loyalty-and-rewards/troubleshooting/a-customers-loyalty-coupon-isnt-working.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/a-discount-is-smaller-than-the-points-value-shown.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.