> 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.md).
# Selling
Sell in Touch mode or Keyboard mode, and find your way to orders, payments and margins.
This section covers selling in Flow Client: the two sales modes, order states, payments, exchange notes and margins.
## Touch mode vs Keyboard mode
Flow Client has two ways to sell: Touch mode and Keyboard mode. Most stores settle on one, but where the device setting allows it, you can switch with the **Touch** switch next to **Sale** in the menu.
Each device's **Touch mode** setting, under **Admin → Settings → Devices**, decides the starting point:
| Setting | Effect |
| ----------------------------- | ------------------------------------------------ |
| **Optional - On by default** | Starts in Touch mode; the switch is available |
| **Optional - Off by default** | Starts in Keyboard mode; the switch is available |
| **Always on** | Touch mode only; no switch |
| **Always off** | Keyboard mode only; no switch |
## Touch mode
The most used mode, built for touch screens such as iPad. Buttons and text are larger. Many stores also use it on regular Windows or Mac computers.
## Keyboard mode
Built for speed, for stores with a steady queue at the till. The sales features are available from the keyboard:
| Shortcut | Action |
| --------------------------------- | -------------------------------------------------- |
| Ctrl+N | Search for a product |
| Ctrl+K | Search for a customer |
| Ctrl+B | Browse product groups |
| Ctrl+P | Park the order (or confirm it, if it has payments) |
| Ctrl+Enter | Go to payment |
| Hold Ctrl+D | Show cost and contribution margin |
On Mac, use Cmd instead of Ctrl.
## In this section
* [Order vs Receipt vs Offer](/docs/day-to-day-operations/selling/order-vs-receipt-vs-offer.md) — how a sale becomes a receipt, and what an offer is
* [Order states](/docs/day-to-day-operations/selling/order-states.md) — open, parked, confirmed, complete and canceled
* [Payments](/docs/day-to-day-operations/selling/payments.md) — taking payment and combining payment methods
* [Exchange note](/docs/day-to-day-operations/selling/exchange-note.md) — a gift slip without the price
* [Understanding contribution margins](/docs/day-to-day-operations/selling/understanding-contribution-margins.md) — how much a sale leaves, and how much discount you can give
*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/selling.md?ask=&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.