> 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/customers/customer-barcode-scanning.md).

# Customer barcode scanning

Print a barcode card for a customer and scan it to add them to the order.

Print a card with a customer-specific barcode, and scan it at checkout to attach the customer to the order — no manual lookup.

## What is this?

A way to identify a customer by scanning. Print a barcode for the customer once; each time they show it, scan it and Flow Retail adds them to the order.

Ideal for loyalty programs, B2B accounts, or any scenario where fast customer identification matters.

## How does it work?

**Scanning a customer barcode**

Scan or type the barcode in the product search field, or in the customer search field. If a match is found, the customer is added to the order and Flow Client shows **Customer added to order**. If the order already has a customer, you're asked to confirm with **Change customer**. An unknown barcode gives **No customers found**.

**Printing customer barcodes**

Open the customer in Flow Client and select **Print barcode**. With one suitable printer it prints straight away; with several, you choose one. The button is unavailable when no printer on the device can print customer cards. What prints depends on the printer:

* **Label printer:** a label with the barcode and the customer's name.
* **Receipt printer:** the barcode only, then the paper is cut.

## How do I get started?

Open any customer in Flow Client, select **Print barcode**, and fix the label to a card. Then scan it in the product search field at checkout.

{% hint style="warning" %}

#### Use cardboard cards - not plastic cards

We recommend simple credit card-sized cardboard cards with a blank area for the barcode label, preferably on the back side of the card.
{% endhint %}

### Printer required

To print the barcode, you need a label printer or a receipt printer connected to the device.

The label printer can be the one you use for Flow Gift Card labels and price labels.

{% hint style="info" %}

#### Not for every retailer

Not everyone wants to carry a card. Many prefer giving their phone number at checkout.

This feature works best for frequent shoppers, loyalty members, or B2B customers who benefit from fast identification.
{% endhint %}

### Does the barcode contain any personal information?

No. The barcode is the customer's internal ID number with the prefix `CUST#`.

It is not possible to reverse that number into a specific customer without explicit access to Flow Retail.

*Last updated 24.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/customers/customer-barcode-scanning.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.
