Locations

Locations are physical places or storage areas within your organization's infrastructure where inventory items can be stored or managed. They provide a hierarchical and organized way to track where your assets, products, or inventory items are situated.

• Locations can be organized in a parent-child relationship
• Create a tree-like structure (e.g., Warehouse → Zone → Shelf → Bin)
• Each location can have multiple sub-locations
• Track the complete path from top to bottom

• Every location is associated with a physical address
• Includes standard address components like street, city, state/province, postal code
• Supports geographic coordinates (latitude and longitude)
• Links to countries and regions

• Flag to specify if a location can store inventory items
• Track what inventory is currently stored at each location
• Prevents deletion of locations that contain inventory items

• Add custom properties to locations using the flexible properties field
• Attach custom forms to collect and store additional information
• Respond to forms with specific data relevant to the location

• Generate and manage barcodes for locations
• Scan locations for quick identification and inventory operations
• Link multiple barcode formats to the same location if needed

• Permissions-based access to locations
• Different user roles can view, create, update, or delete locations based on permissions
• Locations are tied to specific clients and stores for multi-tenant security

1. Provide a name and description for the location
2. Specify the physical address
3. Set whether it can store inventory
4. Optionally, assign it to a parent location
5. Add any custom properties or form responses
6. Generate barcodes if needed

• Create top-level locations (e.g., warehouses, stores)
• Add sub-locations underneath (e.g., zones, aisles, shelves)
• Track the full path from top to bottom
• View locations as a tree structure with configurable depth

• Assign inventory to locations marked as "can store inventory"
• Track inventory movements between locations
• Search for inventory by location
• Use barcodes for quick location identification during operations

• Locations can be soft-deleted (archived) instead of permanently removed
• Archived locations can be restored if needed
• View a list of archived locations separately from active ones

• A location cannot be deleted if it contains inventory items
• A location cannot be deleted if it has child locations
• Locations are always associated with a specific store and client
• A location must have a name and address

1. Create a logical hierarchy that matches your physical space
2. Use descriptive names and paths for easy identification
3. Utilize custom properties and forms for location-specific attributes
4. Implement barcodes for faster operations
5. Archive rather than delete locations to maintain historical data