# Store and User License policy

## Store License

The Store License is a monthly fee per store, regardless of size or number of users. The head office counts as one store. The same applies to any external warehouses/central warehouses that are not linked to a specific store/outlet.

Billing starts in the month you go live, regardless of the specific day of the month.

## User License

The User License is a monthly fee per user who has been active during the billing period. The fee is the same for all users, regardless of role or access level. API access (essentially one system) counts as one user license. If multiple systems require API access, one user license per system access will be billed.

Users who are not part of the head office but work across multiple physical stores will count as one user for the store to which they have primary affiliation. If they have no specific store affiliation, they are defined as a head office user.

Billing starts in the month the user logs in for the first time, regardless of the specific day of the month.

### Fair Use – Fair Pricing

Flow Retail requires personal user accounts, and it is assumed that all users have their own login. The number of active users per store is automatically counted/reported throughout the month and forms the basis for billing. User accounts not used during the month will not be included in the billing in the upcoming month.

### User Cap on User Licenses

The User Cap defines the maximum number of active users per store that are billed. Any users beyond this cap are free of charge. The user cap only applies to stores, not to the head office or central warehouse.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flowretail.com/docs/store-and-user-license-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.