> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control.md).

# Point of Sales Control

## Point of Sales Control Overview

![](https://documentation.payfacto.com/POS/Veloce/assets/images/VeloceCommon/Icons/Icon-PointOfSalesControl.png)

Point of Sales Control is a core module that is included with every Veloce license. It allows restaurants to manage day-to-day operations from one central location. This is also where most of the menu programming is done, from creating sales items to employee access.

![](https://documentation.payfacto.com/POS/Veloce/assets/images/VeloceCommon/POSControl/Screen-POSControl.png)

Here are a few tasks that will be carried out from the Point of Sales Control Module:

* Creating Sales Items
* Creating Big Divisions, Divisions and Item Screens
* Configuring taxes
* Creating and managing promotions and discounts
* Managing employees and employee functions
* Managing payment modes
* etc...

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td></td><td>Taxes</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/taxes.md">Taxes </a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/MQl7dE7I4GjVT5QiWz2x/IMG_PayFacto-Support%2001.png">IMG_PayFacto-Support 01.png</a></td></tr><tr><td></td><td>B.C. Soda Tax</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/b.c.-soda-tax.md">B.C. Soda Tax </a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/xUZwru5D8oTONdKWk0dN/IMG_PayFacto-Support%2002.png">IMG_PayFacto-Support 02.png</a></td></tr><tr><td></td><td>Divisions</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions.md">Divisions</a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/wcavhAZyban8JbyhAshQ/IMG_PayFacto-Support%2003.png">IMG_PayFacto-Support 03.png</a></td></tr><tr><td></td><td>Sales Items</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/sales-items.md">Sales Items</a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/6XBoPZX76rAZR8MgGifT/IMG_PayFacto-Support%2004.png">IMG_PayFacto-Support 04.png</a></td></tr><tr><td></td><td>Groups and Keys</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/groups-and-keys.md">Groups and Keys</a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/d67d0ftQ671UqK1bvtlI/IMG_PayFacto-Support%2005.png">IMG_PayFacto-Support 05.png</a></td></tr><tr><td></td><td>Payment Modes</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/payment-modes.md">Payment Modes </a></td><td><a href="https://content.gitbook.com/content/NjXj7M9eIjDUG86HsSCs/blobs/HfE2QqAkVXXZTRGl9lzs/IMG_PayFacto-Support%2006.png">IMG_PayFacto-Support 06.png</a></td></tr></tbody></table>


---

# 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.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control.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.