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

# Big Divisions

Big divisions are the larger categories that are used for reporting purposes. Big divisions must exist before smaller divisions are created, as they will regroup those smaller divisions.

#### Examples :

* Food
* Beverages
* Alcohol
* Modifiers

Since big divisions will later be sub-divided in divisions, it is important to keep them as generic as possible, as in the examples above. In a standard menu, it is rare to see more than 4 or 5 big divisions.

### How to create Big divisions

1. Login to the Veloce Back-Office.

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

2. Start the Point of Sale Control module.

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

3. Click on the Sales menu and select the Big Divisions... option.

![Menu - Sales](https://documentation.payfacto.com/POS/Veloce/assets/images/Chap05_PointOfSaleCtrl/Divisions-BigDivisions/Sales-BigDivisions.png)

4. The list of Big Divisions appears. Click on an existing Big Division to modify it, or click on an empty space to create a new one.

![Big Division List](https://documentation.payfacto.com/POS/Veloce/assets/images/Chap05_PointOfSaleCtrl/Divisions-BigDivisions/BigDivisionList.png)

5. Configure the Big Division parameters:

![Big Division Parameters](https://documentation.payfacto.com/POS/Veloce/assets/images/Chap05_PointOfSaleCtrl/Divisions-BigDivisions/BigDivConfig.png)

#### Description

Type a meaningful description for this Big Division

#### 2nd Name

Type a secondary description for this Big Division. This is generally used as an alternate description in a different language for multi-language setups.

#### On operation assessment report

Enable this option to include this big division on the Operation Assessment report.

![Button - Delete](https://documentation.payfacto.com/POS/Veloce/assets/images/VeloceCommon/Buttons/Button-Delete.png)

Click the Delete button to remove this Big Division.

![Button - Save](https://documentation.payfacto.com/POS/Veloce/assets/images/VeloceCommon/Buttons/Button-Save.png)

Click the Save button to save changes and exit.

![Button - Exit](https://documentation.payfacto.com/POS/Veloce/assets/images/VeloceCommon/Buttons/Button-Exit.png)

Click the Exit button to close this window without saving changes.


---

# 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/big-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.