> 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/divisions.md).

# Divisions

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

<details>

<summary>Definition</summary>

Divisions are sub-categories of Big Divisions and are are also used for reporting purposes. Divisions must be created before sales items can be created.

#### Examples :

* Starters
* Soups
* Salads
* Pasta
* Steaks
* Burgers
* Sandwiches
* Desserts
* Beverages
* Beers
* Wine
* Cocktails
* etc...

![Note Icon](https://documentation.payfacto.com/POS/Veloce/assets/images/CompanyArtwork/NoteIconGold48x48.png)

NOTE: Since Division are sub-categories within Big Divisions, these are more precise and numerous. It is common to see menus with 50 divisions or more. Up to 100 divisions can be created in Veloce.

</details>

[Back to top](#definition)

<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>Divisions - Configuration</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-configuration.md">Divisions - Configuration</a></td><td></td></tr><tr><td></td><td>Divisions - Price per Quantity</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-price-per-quantity.md">Divisions - Price per Quantity</a></td><td></td></tr><tr><td></td><td>Divisions - Discounts</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-discounts.md">Divisions - Discounts</a></td><td></td></tr><tr><td></td><td>Divisions - Redistributed Tips</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-redistributed-tips.md">Divisions - Redistributed Tips</a></td><td></td></tr><tr><td></td><td>Divisions - Links</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-links.md">Divisions - Links</a></td><td></td></tr><tr><td></td><td>Divisions - General Ledger</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-general-ledger.md">Divisions - General Ledger</a></td><td></td></tr><tr><td></td><td>Divisions - Taxes</td><td></td><td><a href="/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/divisions/divisions-taxes.md">Divisions - Taxes </a></td><td></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/divisions.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.