> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/loyalty-points.md).

# Loyalty points

Let members pay with the balance they have built up in your loyalty program.

## What is this?

Loyalty points let a member pay with the balance they have earned in your loyalty program. The balance itself lives with your loyalty provider — Flow Retail reads it at the till, spends against it, and reports the spend back.

{% hint style="info" %}
This is the spending half of a loyalty program. What a member earns, and when it expires, is decided by the program, not by Flow Retail.
{% endhint %}

***

## How does it work?

Attach the customer to the sale first. Without one, the till asks you to add a customer before it will let you pick the method, and a customer who is not a member is turned away with **The customer is not enrolled in the loyalty program. Loyalty points cannot be used as a payment method.**

Their **Available balance** shows on the customer's **Loyalty** tab. Spend up to that balance and no further — ask for more and the till answers **There is only a balance of … available for this order.** Only one loyalty payment goes on an order; the rest is paid with something else.

Flow Retail reserves the amount with the provider, then turns the spend into discount lines on the order so VAT lands correctly on the receipt and in your accounts.

{% hint style="warning" %}
A loyalty refund has to point back at the sale it came from. Find the original sale and refund from there, rather than starting a fresh return.
{% endhint %}

***

## How do we get started?

Loyalty points runs on an integration with your loyalty provider, so start by talking to us about your program.

We then switch on the Loyalty points extension, connect your provider, and you enable the payment method in the stores where members should be able to spend.

***

*Last updated 17.09.2026*


---

# 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.flowretail.com/docs/day-to-day-operations/selling/payments/payment-methods/loyalty-points.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.
