What are Locations?
Locations represent physical places in your operation:- Warehouses: Main storage facilities
- Sections: Areas within a warehouse (e.g., North Wing, South Wing)
- Aisles: Rows within sections
- Bays or Bins: Specific storage spots
- Retail Locations: Storefronts or distribution points
Location Hierarchy
Parent-Child Relationships
Locations can be organized in a tree structure with Customer at the root:Benefits of Hierarchy
- Logical Organization: Mirror your physical layout
- Easy Navigation: Find locations quickly
- Grouped Operations: Perform actions on parent locations
- Scalability: Add new locations under existing parents
The location hierarchy is flexible. You can create as many levels as needed to accurately represent your facility structure.
Required Hierarchy Structure
Your location system must follow these structural requirements: Customer Location (Root)- Every system requires exactly one Customer location
- The Customer location is the root of your entire location hierarchy
- Cannot have a parent location
- All other locations must connect to the Customer location
- Site locations represent physical facilities
- Must be under the Customer location (automatic if no parent specified)
- Other location types (Warehouse, House, Section, etc.) must have a path leading to a Site
- Warehouse, House, Section, Bay, Aisle, Bin, Ship To, and Unknown types
- Must have a parent chain that eventually leads to a Site location
- The system validates this requirement during location creation
Location Properties
Basic Information
Each location includes:- Name: Descriptive name (e.g., “Main Warehouse - Aisle 3”)
- Code: Unique identifier or short code (e.g., “MW-A3”)
- Description: Additional details about the location
- Type: Location category (warehouse, retail, distribution, etc.)
Address Information
Locations can have full address details:- Street address
- City, state, zip code
- Country
- Used for shipping/delivery planning
Status
Locations have active/inactive status:- Active: Location is in use and available
- Inactive: Location is disabled (not available for new inventory)
Organizational Fields
Additional fields help organize locations:- Parent Location: Which location this is under in the hierarchy
- Path: Auto-generated path showing hierarchy (e.g., “Main/North/AisleA”)
Creating and Managing Locations
Adding a New Location
To create a location:- Navigate to Locations in the Fulfill menu
- Click Add Location or Add Child Location (if adding under a parent)
- Fill in the location details:
- Name and code (required)
- Type and description
- Parent location (if applicable)
- Address information
- Save the location
Editing Locations
To modify an existing location:- Find the location in the location list
- Click to open the location details
- Click Edit
- Update the information
- Save your changes
Bulk Import via CSV
For setting up many locations at once:- Import locations in bulk using CSV files
- Include addresses and hierarchical relationships
- Automatically create parent locations if they don’t exist (as Site type)
- Update status of existing locations (other fields require manual updates)
Bulk Import Locations
Learn how to bulk import locations using CSV files for faster warehouse setup.
Location Tree View
The location list displays as a hierarchical tree:- Expand/collapse parent locations to see children
- Visual indentation shows hierarchy levels
- Drag-and-drop may be available to reorganize (check your configuration)
Location-Based Inventory
Inventory Tracking by Location
Each inventory count is tied to a specific location:- Track which items are at which locations
- See quantity breakdowns by location
- Allocate orders from specific locations
- Move inventory between locations
Availability Sessions
When recording inventory in availability sessions:- Select the location where the inventory is stored
- Each item can have different quantities at different locations
- Location is required for all inventory counts
Order Allocation
When allocating orders:- Choose which location(s) to fulfill from
- System shows available quantity at each location
- Allocate from multiple locations if needed
- Fulfillment team uses location info for picking
Accurate location tracking is essential for efficient order fulfillment. Make sure your team records inventory at the correct locations.
Location Types
Available Location Types
The system supports these location types, each serving different purposes: Customer- Root of your location hierarchy
- Only one Customer location allowed per system
- Cannot have a parent location
- All other locations must connect to the Customer location
- Physical facilities or main locations
- Directly under Customer in hierarchy
- Required for organizing other location types
- Warehouses and other types must be under a Site
- Main storage facilities
- Large inventory capacity
- Must be under a Site location
- Greenhouse or growing facilities
- Specialized agricultural structures
- Areas within a warehouse or facility
- Helps organize larger spaces
- Rows within sections
- Guides picking and organization
- Storage areas within aisles
- More specific storage organization
- Individual storage spots
- Most specific storage location
- Shipping destinations
- Delivery endpoints
- Locations without a specific type
- Use sparingly for flexibility
Important Hierarchy Rule: All non-Customer, non-Site location types (Warehouse, House, Section, Bay, Aisle, Bin, Ship To, Unknown) must have a parent chain that eventually leads to a Site location. The system validates this during creation.
Location Codes
Purpose of Location Codes
Location codes provide:- Short, memorable identifiers
- Easy reference for staff
- Integration with external systems
- Barcode/label generation
Best Practices for Codes
Location Code Guidelines
- Keep codes short (3-10 characters)
- Use consistent format across all locations
- Include hierarchy hints (e.g., “MW-N-A1” for Main Warehouse, North, Aisle 1)
- Avoid special characters that may cause issues
- Document your code system for team reference
Using Locations in Operations
Recording Inventory
When adding or adjusting inventory:- Select the item
- Choose the location where inventory is stored
- Specify the grade/quality
- Enter the quantity
- System tracks inventory by item/location/grade
Creating Orders
Locations affect order creation:- Customer locations determine delivery addresses
- Warehouse locations show where items can be fulfilled from
- Available inventory shown by location
Fulfilling Orders
During fulfillment:- Allocated locations tell staff where to pick items
- Location-based pick lists optimize picking routes
- Staff navigate to specific locations to gather items
Location Settings and Configuration
Location-Specific Settings
Locations can have their own settings:- Default price groups
- Payment terms
- Operational flags
- Integration settings
Tenant vs. Location Hierarchy
Understanding the system structure: Tenant (Login Site)- Your overall organization account
- Selected at login (sometimes called “site selection”)
- Determines which data you see across the application
- One tenant can have many locations
- Specific places within your tenant for inventory tracking
- Starts with Customer location (root)
- Organized under Site locations (facilities)
- Many location types available (Warehouse, Section, Aisle, Bin, etc.)
- A type of location in the hierarchy (not the same as tenant/login site)
- Represents a physical facility or main location
- Always under the Customer location in the hierarchy
- Required parent for Warehouse, House, and other storage location types
Don’t confuse tenant selection (your login account/organization) with Site location type (a physical facility in your location hierarchy) or with location management in general.
Best Practices
Location Structure Design
When planning your location hierarchy:- Start Simple: Begin with main areas, add detail as needed
- Match Physical Layout: Structure should reflect how your facility is organized
- Consider Picking Routes: Organize to optimize fulfillment paths
- Plan for Growth: Leave room to add new locations as you expand
- Be Consistent: Use same principles across all facilities
Location Maintenance
Keep your location data clean:- Regularly review and remove unused locations
- Update location information when layout changes
- Ensure staff use correct locations when recording inventory
- Audit location assignments periodically
- Train new staff on location system
Location Naming
Effective location names:- Descriptive: Clearly indicates what/where the location is
- Unique: No duplicate or confusing names
- Hierarchical: Include parent info if helpful (e.g., “Warehouse A - Section 2”)
- Scannable: Easy to read at a glance
Reporting and Analysis
Location-Based Reports
Use locations for reporting:- Inventory by location
- Orders fulfilled from each location
- Location utilization rates
- Picking efficiency by location
Location Performance
Track key metrics:- How much inventory stored at each location
- How quickly items move from each location
- Order fulfillment times by location
- Accuracy rates by location
Troubleshooting
Can’t Find a Location
If you can’t locate a location:- Use the search function in the location list
- Check if location is inactive (filter may be hiding it)
- Verify you have permission to view the location
- Check if location was deleted or renamed
Inventory Shows Wrong Location
If inventory appears at the wrong location:- Review availability log to see where counts were recorded
- Check if items were moved but not updated in system
- Verify staff recorded inventory at correct location
- Perform physical count and adjust as needed
Location Hierarchy Issues
If the hierarchy isn’t displaying correctly:- Check that parent locations are set correctly
- Verify no circular references (location can’t be its own parent)
- Refresh the page to reload the tree
- Contact your administrator if issues persist
Next Steps
- Manage Availability - Track inventory by location
- Allocate Inventory - Assign items from specific locations
- View Products - Manage your item catalog
- Create Orders - Create orders using location-based inventory