> 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

To sum it all up, the selling functionality in Flow Retail is so easy to use that you should not be needing to read this guide.

However, while you now are here, lets go trough it all :thumbsup:

## Touch mode vs Keyboard mode

Flow Retail has two 'modes' for selling: Touch mode and Keyboard mode.

Although you typically decide on either of them, you can quickly switch between the two modes, even on an active order!

### Touch mode

This is the most used mode, and is optimized for touch devices such as iPad and similar.

Many stores also use the Touch mode on non-touch-based devices, such as regular Windows or Mac computers, as it is so easy to use.

### Keyboard mode

This mode is built for speed, and is for the most used by stores with a continuous queue of customers coming to pay.

Keyboard mode lets you use all sales features with just the keyboard.

In an optimized flow with just one product, it can take as low as 2-3 seconds to fulfill a sale.

## The interface

### Touch mode

The interface in Touch mode is super-intuitive, and most people would be able to start selling with this mode enabled in just a few minutes of training.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.flowretail.com/docs/day-to-day-operations/selling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.