# Devices / terminals

## Adding new devices

Every device (Windows PC, Mac, iPad, mobile device, etc.) must be registered in Flow Retail before it can be used in a store environment.

### Step-by-step

1. Go to Backoffice > Stores > Devices, and click “Add device”
2. Enter a clear and descriptive device name
   * 💡[ *Be sure to follow the naming convention below*](#naming-convention-for-devices-and-registers)
3. Select the client type (Windows, Mac, iPad, Android Assistant, etc.)
4. Assign the device to the correct store
5. If the device will handle payments (e.g., for settling or refunding orders), assign a register
   * Ensure the register is already created, or create one under Backoffice > Stores > Registers
   * ✅ *Use the same suffix for the register as the device, since they are tightly linked*
6. Click Save
7. Copy the auto-generated one-time device key — you’ll need this when installing the client

### Onboarding the device in the client

1. Install the relevant client (Windows, Mac, iPad, or Android/iPhone Assistant)
2. When prompted, enter the device key from Backoffice
3. Log in using your username and PIN
4. Done! The device is now connected and ready to use

***

## Naming convention for Devices and Registers

A consistent naming convention helps with:

* Debugging
* System traceability
* Easier identification in multi-store environments
* User support and training

### Device naming convention

We recommend naming each device using the following format:

`d4762t01`

#### Breakdown

| Part | Meaning                                                                |
| ---- | ---------------------------------------------------------------------- |
| d    | Device (always starts with d)                                          |
| 4762 | Store number (unique per store)                                        |
| t    | Device type: t for till/POS device                                     |
| 01   | Device number (counting from entrance, left to right or front to back) |

#### Other possible device types

| Letter | Meaning                    |
| ------ | -------------------------- |
| s      | Store/admin terminal       |
| h      | Handheld device            |
| o      | Office/backoffice PC       |
| w      | Warehouse/logistics device |

### Register naming convention

Registers are logical units representing the payment context (e.g., cash drawer, payment terminal). They are not physical devices, but must be linked to a device for payments to work.

#### Recommended format for registers:

`r4762t01`

#### Breakdown:

| Part | Meaning                                            |
| ---- | -------------------------------------------------- |
| r    | Register (always starts with r)                    |
| 4762 | Store number                                       |
| t01  | Matches the associated till device (e.g. d4762t01) |

#### Example Pairing

| POS Device (Till) | Register (linked to Device)    |
| ----------------- | ------------------------------ |
| d4762t01          | r4762t01                       |
| d4762t02          | r4762t02                       |
| d4762h01          | *(no register, handheld only)* |

## Summary

* Keep a unique store number as part of both the device- and register names
* Use d for all device names
* Use r for registers, which represent the payment setup linked to a device
* Use t, h, o, s, etc. to indicate device type
* Always align register names with the device they are linked to

This convention ensures traceability, clarity, and scalability as your retail environment grows.


---

# 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/day-to-day-operations/devices-terminals.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.