> For the complete documentation index, see [llms.txt](https://guide.acumensystems.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.acumensystems.com.au/system-parts/master-files/sales-areas.md).

# Sales Areas

A sales area is a grouping of related customers. Sales areas can be grouped in a hierarchical manner producing the effect of a tree structure. The following example illustrates the effect of this hierarchical design:

![Hierarchical diagram of sales area tree structure](https://4292890076-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MIXjqwujolmdHaVH5d4%2F-MT9DCQ9ofW4DMr9Pp70%2F-MT9DGH_Oj9es1uv02D3%2FAcuGroupingDiagram.png?alt=media\&token=dab8ad3d-37a6-488b-ab05-80bfe6244319)

The above tree structure is derived by the relationship of the sales areas codes shown after the area names. As you can see each tier of the structure as you move from left to right has two extra characters in the area code. We call this the depth of the tree. A tree can be up to 5 tiers deep.

When you add a sales area to the system the sales area code dictates its position in the tree structure. You can only create a new sales area if it is either a branch (child) of an existing sales area or a first tier sales area (ie. a two character area code that designates the start of a new tier). While the above tree structure uses numeric area codes any two character alphanumeric combination can be used to define an area.

The importance of the tree structure is threefold when using Acumen:

* The structure is used visually as an aid in locating information
* The structure allows the level of detail shown in reports to be scaled
* Selection of a range of records is made easier


---

# 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://guide.acumensystems.com.au/system-parts/master-files/sales-areas.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.