Operational Locations

Operational Locations define where work happens. They help users classify stock, sales, service delivery, production, inspections, events, capacity bookings, field work, and reporting.

Operational locations are business-facing locations, not only legal branches. They can represent physical or practical work points used by day-to-day operations.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Operational Locations	Administration -> General Setup -> Operational Locations	Create shared physical and logical places used by operations.
Warehouses	Inventory -> Setup -> Warehouses	Use warehouse-type operational locations for stock holding and movement.
POS Registers And Stores	Point of Sale -> Setup	Attach registers and sales activity to the correct operating place where configured.
Production, Events, Inspections, And Resource Capacity	Service-specific operations workspaces	Select locations for work execution, scheduling, inspection, or reporting.

Examples

Operational locations can represent:

• Branches.
• Warehouses.
• Stores.
• Production areas.
• Field locations.
• Service centres.
• Collection points.
• Inspection sites.
• Classrooms, yards, or training spaces.
• Event venues.

What Locations Affect

Location setup affects:

• Stock movement and stock balances.
• POS store assignment and cashier activity.
• Production and shop-floor tracking.
• Event and inspection scheduling.
• Resource-capacity availability.
• Delivery, dispatch, and collection workflows.
• Operational reporting by site.

If a location is missing or unclear, users may post work to the wrong place, which can create stock, scheduling, and reporting errors.

Naming Guidance

Use names that are specific enough for users to distinguish one location from another. A good name usually includes the branch/site and the operational area, for example a store room, production line, service bay, training yard, or field collection point.

Avoid names such as “Main”, “Default”, or “Location 1” unless the tenant has only one unambiguous operating site.

Active And Inactive Locations

Keep inactive or retired locations out of active workflows. Inactivation should be used when the location should no longer be selected for new work, while historical records remain understandable.

Before deactivating a location, check whether it is still used by active stock, open sessions, scheduled work, pending inspections, or open production and dispatch records.

Common Mistakes

• Using business units and operational locations interchangeably.
• Creating several names for the same physical place.
• Posting stock movements to a broad branch when a warehouse or store room is required.
• Leaving retired locations active.
• Creating overly detailed locations that users cannot maintain consistently.

Good Practice

Design locations around how users actually work and report. Keep the list clear, avoid duplicates, and review location setup before activating inventory, POS, production, events, inspections, or resource-capacity workflows.