Know what is available by location
On-hand counts roll up to the workspace but stay broken out by location. A sales rep can check whether the item is in the right warehouse before promising a date.
Feature
Multi-location tracking
Multi-location tracking means you can answer 'where is it' without calling someone. One workspace holds stock across warehouses, retail shops, trucks, jobsites, stockrooms, zones, and bins. Each keeps its own balance. Transfers between locations are first-class events, not adjustments hidden inside a global total.
What you get
Three outcomes operators can see
Transfer stock with a clean paper trail
Transfers track each step: requested, in transit, received, with quantities and timestamps. Discrepancies surface at receipt instead of disappearing into a black hole.
Stop duplicate emergency purchases
When one location runs short while another sits on safety stock, the system shows it. Teams transfer instead of placing a rush order at full price.
How it works
From action to record
- 01
Build your location hierarchy
Create top-level locations (warehouse, store, truck, jobsite) and nest sub-locations (zone, aisle, bin) where useful. Hierarchy is optional but pays off for larger sites.
- 02
Assign items and reorder rules
Stock an item in any number of locations. Reorder thresholds can be global or set per location. A shop in Phoenix probably needs different safety stock than a truck in Vermont.
- 03
Move stock with a transfer record
Initiate a transfer from one location to another. Quantities show as in-transit until the receiving location confirms. The loop closes on receipt.
- 04
Review availability and aging stock
Reports show availability by location, aging stock by location, cross-location coverage. The view rolls up or drills down on demand.
How it works
How multi-location works
Each location is a real record with its own on-hand counts, reorder rules, and movement history. An item can exist in many locations; the workspace tracks each balance independently. Aggregate views (total on-hand, total available, total value) derive from per-location balances rather than getting stored separately, which keeps the numbers consistent. Transfers are events, not edits. They reduce the source location, mark the quantity as in-transit, and only credit the destination on receipt. That model gives you accountable counts even when stock spends two days on a truck. No phantom inventory, no mystery adjustments at month-end.
In your day
Where it fits in your day
Construction and electrical contractors track stock across a shop, multiple trucks, and active jobsites; nesting trucks under a region keeps the picture readable. Retail operators track store stock plus a shared backroom or distribution location, often syncing the sellable view to ecommerce. 3PL operators separate inventory by customer at the top level and use sub-locations for bins. Field service teams track per-technician truck stock so replenishment is driven by what each tech actually used, not a regional average. The hierarchy adapts to the operation. The underlying ledger stays the same.
Controls
What you keep in control
Permissions can scope to specific locations. A store manager sees their store. A truck owner sees their truck. Only managers see the workspace-wide view. Transfers can require receiving confirmation before quantities count at the destination. Reorder rules per location prevent a single global threshold from triggering noisy alerts in places that don't need them. Every transfer, count, and adjustment writes to the activity log with the location it touched. Audit questions like 'which truck did this case go to' get answered from the log instead of from memory.
Multi-location tracking FAQ
How many locations can I create?
There is no fixed cap planned at launch. SMB operators currently run anywhere from 2 to a few hundred locations once trucks, bins, and stockrooms are counted. Plans and pricing are still being finalized. If your operation needs hundreds of nested locations from day one, talk to us so we can confirm the workspace shape before you import. The model is designed for distributed inventory, not for one warehouse with a single shelf.
Can I restrict users to specific locations?
Yes. Users can be scoped to one or more locations, with separate permissions for read, count, transfer, and approve. A retail store manager can be limited to their store. A roving operations lead can have broader access. Workspace admins always see the full hierarchy. Enforcement is consistent across web and mobile, so a scoped user does not see a different picture depending on which app they are in.
How do reorder rules work across locations?
Reorder rules can be set at the workspace level, the location level, or both. A workspace-level rule acts as a default; a location-level rule overrides it for that location. This matters because a slow store and a busy store need different thresholds. The purchasing agent reads location-level rules first when drafting reorders, so suggested quantities reflect real demand at each site rather than a workspace average.
Are transfers tracked while stock is in transit?
Yes. When a transfer is initiated, the quantity leaves the source location and is marked as in-transit. It does not arrive at the destination until a receiver confirms it. If quantities differ at receipt, the discrepancy is captured as a separate event so you can see whether it was lost in transit, miscounted at origin, or miscounted at receipt. This is the part most spreadsheet-based setups skip, and it is where most cross-location accuracy is lost.
Can locations roll up by region or business unit?
Yes. Locations support a parent-child hierarchy, so you can group trucks under a region, stores under a brand, or warehouses under a 3PL customer. Reports and balances roll up cleanly. The hierarchy can be reorganized later without losing history, which matters when SMBs reshape their operation more often than enterprise systems expect.
Try Multi-location tracking in Order3.
Start with one recurring inventory problem. Add the SKUs, locations, and counts that matter first, then bring in expert help when the rollout gets complex.