> 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.md).

# Customers

Customer types, their fields, and the rules Flow Retail applies to them.

**Flow Retail's customer register covers both B2C and B2B: private customers, companies, and contract customers with their own credit terms.**

Customers are created and edited in Flow Client — at the till or under **Customers → Customers**. Each holds addresses, consents, customer groups and contacts; companies can also have departments.

{% hint style="warning" %}

## Important information on GDPR

Flow Retail uses a single, centralized customer database across all stores and organizational units within the same tenant. Personal customer information — such as email addresses and phone numbers — may therefore be accessible across different legal entities (e.g., subsidiaries or franchise stores).

To ensure transparency, we recommend clearly stating this in your privacy policy with wording such as:

*“By becoming a customer, you consent to the sharing of your customer data across all our stores, including any franchise or partner locations operating under the same brand.”*
{% endhint %}

## What are the different customer types?

A customer is one of three types, chosen at the top of the customer form:

1. **Person** — private person / consumer
2. **Company** — a business with no special agreement
3. **Contract customer** — a business with a credit limit and payment terms

{% hint style="warning" %}
**Contract customer** is only available with the B2B extension.
{% endhint %}

### Private person

Most customers are persons, and **Person** is the default when adding a new customer. Only first name, surname and country are required, but a telephone number is highly recommended.

| Field (as shown in Flow Client) | Required     | Validation                 |
| ------------------------------- | ------------ | -------------------------- |
| First name                      | Yes          | -                          |
| Surname                         | Yes          | -                          |
| Telephone                       | Configurable | Phone number, with country |
| E-mail address                  | Configurable | Valid email address        |
| Address                         | Configurable | -                          |
| Postal code                     | Configurable | Valid format per country   |
| Town                            | Configurable | -                          |
| Country                         | Yes          | Dropdown list              |
| Ledger account number           | No           | -                          |
| Internal info                   | No           | -                          |

"Configurable" fields are made required in **Flow Admin → Settings → Tenants**, on the **Settings** tab. There are separate lists for **Person**, **Company** (which also covers contract customers), **Department** and **Contact**. Three of them have a duplicate check:

* **Person:** duplicate check on **Mobile and email**
* **Company:** duplicate check on **VAT Number**
* **Contact:** duplicate check on **Email**

### Company (standard)

The same fields as a person, with company name and organization number instead of first name and surname:

| Field               | Required             | Validation                                  |
| ------------------- | -------------------- | ------------------------------------------- |
| Company name        | Yes                  | -                                           |
| Organization Number | Yes (in Flow Client) | Checked against the country's number format |

With the EHF extension, the form also has **EHF-invoice** and **EHF address**.

With the Company Registry extension, you choose the **Country**, enter **Organization Number** and select **Find information** before creating the company or contract customer. The company name and organization number are then filled in from the registry and cannot be edited.

### Company (B2B)

A **Contract customer** is a company you sell to on agreed terms.

**Functionality for B2B:**

* Set payment terms: the number of days before an invoice is due.
* Set a credit limit. The form shows the remaining **Outstanding balance**, and a B2B invoice payment that exceeds it is refused. If the B2B extension uses an external credit system, the remaining credit is checked there instead.
* Connect each sale to a contact person. A B2B invoice cannot be paid without a customer contact on the order.
* A B2B invoice must cover the whole remaining amount on the order.

| Field         | Required | Validation |
| ------------- | -------- | ---------- |
| Credit limit  | Yes      | Amount     |
| Payment terms | No       | Whole days |

Only tenant administrators can change **Credit limit** and **Payment terms**.

*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.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.
