All Locations
Overview
All Locations is where you build the physical and organisational map of your inventory world. Every stock position, movement, and transaction is tied to a specific location in this tree — so the accuracy of your inventory data depends directly on how well your location hierarchy reflects the real world.
Locations are arranged in a parent-child hierarchy. At the top sits your company (the root), and below it you nest progressively more specific places: countries, cities, warehouses, zones, bins, vehicles, and anything else that holds or moves stock.
The page is found at Inventory Management → Location Management → All Locations.
The Location Tree
The left panel shows the entire location hierarchy as an expandable tree.
Summary badges
Two badges at the top of the tree give a quick count:
| Badge | Meaning |
|---|---|
| Active: N | Total number of active locations |
| Root locations: N | Number of top-level locations (no parent) |
Navigating the tree
- Select ▶ next to a location to expand it and reveal its children.
- Select ▼ to collapse a branch.
- Select any location name to open its details in the right panel.
Searching
Use the search bar at the top of the tree to find locations by name or code. The tree filters as you type.
Location Detail
Selecting a location in the tree opens its full record on the right. The record is divided into four collapsible sections.
Header fields
| Field | Description |
|---|---|
| Code | The unique identifier for this location (e.g. LYON-SCENT, MAIN-WH). Set at creation and cannot be changed. |
| Name | The human-readable display name shown in lists and transaction forms. |
Basic Information
| Field | Description |
|---|---|
| Description | Optional free-text note about what this location is or where it is. |
| Parent location | The location directly above this one in the hierarchy. Empty for root locations. |
| Location type | The structural category of this location (e.g. Warehouse, Zone, Storage Location, Mobile). See Location Properties. |
| Location purpose | The intended activity at this location (e.g. Receiving, Shipping, Storage). See Location Properties. |
| Owner (responsible worker) | The employee responsible for this location. Optional — drawn from HR records. |
Address
| Field | Description |
|---|---|
| Street | Street address of this location. |
| City | City. |
| Country | Country. |
Addresses are most useful for top-level locations (company, warehouse). Use Clear address to remove all address fields at once.
Operational Flags
| Flag | Description |
|---|---|
| Operational | When on, this location is considered active and ready for stock operations. When off, the location exists in the hierarchy but is not used for transactions. |
Additional Information
| Field | Description |
|---|---|
| Parent location | Repeated here for quick reference, with a No parent label for root locations. |
| Sub-locations | A count of direct child locations (e.g. 3 Sub-locations). Select it to jump to the children. |
| Created date | When this location record was first saved. |
| Modified date | When this location record was last edited. |
Related Inventory Data
The INVENTORY tab at the top of the page exposes three quick links to inventory data scoped to the selected location:
| Link | What it shows |
|---|---|
| On-hand | Current stock quantities held at this location |
| Inventory transactions | All transaction types that involved this location (purchases, sales, assemblies, adjustments) |
| Movements | Movement operations where this location was the source or destination |
Creating a Location
Quick method — from the tree: Select an existing location in the tree, then select + New. The create form opens with that location already set as the Parent location. You can change it if needed.
From scratch: Select + New without selecting anything in the tree first. The parent field will be empty (creating a root location).
Steps:
- Select + New (with or without a location selected in the tree).
- Fill in the header fields:
- Code (required) — a unique identifier. Use a clear, consistent format (e.g.
WAREHOUSE_A1,ZONE_B,VAN-03). Cannot be changed after saving. - Name (required) — the display name.
- Code (required) — a unique identifier. Use a clear, consistent format (e.g.
- In Basic information:
- Description (optional) — add context about this location's role.
- Parent location (optional) — pre-filled if you started from a selected node; leave empty for a root location. Can be changed from the dropdown.
- Location type (optional) — classify the location (Warehouse, Zone, Storage Location, Mobile Location, etc.).
- Location purpose (optional) — assign its intended function (Receiving, Shipping, Storage, etc.).
- Owner (optional) — assign a responsible worker.
- In Address — fill in address details if relevant (most useful for top-level company or warehouse locations).
- In Operational flags — set Operational on if this location is immediately ready for stock activity.
- Select Save.
Always create parent locations before their children. You cannot assign a parent that doesn't exist yet.
Al Baraka's structure was built in this order:
- ACME (Company) — root, no parent
- Main Warehouse (Warehouse) — child of ACME
- Zone A, Zone B (Zone) — children of Main Warehouse
- Shelf A1, Shelf A2 (Storage Location) — children of Zone A
- Sales Van 01, Sales Van 02 (Mobile Location) — children of ACME
Al Baraka adds a dedicated receiving dock inside their main warehouse:
| Field | Value |
|---|---|
| Code | DOCK-RECV-01 |
| Name | Receiving Dock 01 |
| Description | Primary inbound goods receiving area |
| Parent location | Main Warehouse |
| Location type | Storage Location |
| Location purpose | Receiving |
| Owner | Ahmed Al Mansouri |
| Operational | On |
Editing a Location
- Select the location in the tree.
- Select Edit in the toolbar.
- Update any field except Code.
- Select Save.
The Code is permanent and cannot be changed after creation. If you need to correct a code, archive the location and recreate it — but only if it has no active inventory or sub-locations.
Archiving a Location
Archiving removes a location from selection dropdowns while preserving all its history.
- Select the location in the tree.
- Select Archive in the toolbar.
- Confirm.
To view and restore archived locations, select Archived items in the toolbar.
A location cannot be archived if it currently holds stock or has active sub-locations. Drain the stock (move it elsewhere) and archive or reassign all child locations first.
Planning Your Location Hierarchy
A well-designed hierarchy makes stock queries fast and movement tracking accurate. The key principle: only locations at the bottom of the tree hold actual stock. Higher-level locations (company, warehouse, zone) are organisational containers.
| Level | Location type | Holds stock? | Purpose |
|---|---|---|---|
| 1 | Company | No | Ownership root for all inventory reporting |
| 2 | Warehouse | No | Physical building; groups zones for filtering |
| 3 | Zone | No | Area within a warehouse (cold storage, bulk area) |
| 4 | Storage Location | Yes | Specific shelf, bin, or pallet position |
| — | Mobile Location | Yes | Vehicle or trolley that moves between sites |