Vault-Managed Operations
Vault controls receiving handover, location allocation, movement, retrieval and reconciliation.
- Vault assigns and updates locations
- Scan-controlled movements
- Vault activity history
- Managed reconciliation and exceptions
Services · Storage Operations and Location Control
Map Every Storage Location, Allocate Inventory and Control Every Movement
Build the complete warehouse hierarchy, assign client capacity, allocate items and containers, measure square-foot and cubic-foot usage, control transfers and retain a complete operational history.
This is a managed operational service. Clients who only need storage capacity without Vault-managed location work should begin with the separate Storage page.
From warehouse map to accountable inventory movement
Design + allocate + move + reconcile
Design + allocate + move + reconcile
01
Design the Location Hierarchy
Create warehouse, building, floor, zone, aisle, rack, shelf, bin, rail and floor-slot structures.
Design the Location Hierarchy
Create warehouse, building, floor, zone, aisle, rack, shelf, bin, rail and floor-slot structures.
→
02
Assign Capacity
Allocate full or partial zones, shared capacity and client-managed areas.
Assign Capacity
Allocate full or partial zones, shared capacity and client-managed areas.
03
Place and Move Inventory
Use scan, search or drag-and-drop to allocate items, containers and rails.
Place and Move Inventory
Use scan, search or drag-and-drop to allocate items, containers and rails.
04
Measure and Reconcile
Track utilisation, recurring value, movement, exceptions and physical reconciliation.
Measure and Reconcile
Track utilisation, recurring value, movement, exceptions and physical reconciliation.
A storage location is useful only when capacity, custody and movement remain connected.
Space truth + inventory truth
Space truth + inventory truth
Choose the operating responsibility
Use Vault-Managed, Client-Managed or Shared Storage Operations
The same warehouse can support different operating models by client, zone or inventory group. Responsibility and access must remain explicit.
↔ Swipe through the storage operating models
Client-Managed Storage
The client operates its own merchandise inside the approved storage allocation.
- Dedicated or approved shared space
- Client users and permissions
- Optional QR and location visibility
- Vault records agreed control points
Shared or Hybrid Control
Client and Vault divide responsibility by zone, movement type, task or inventory group.
- Shared responsibility matrix
- Per-zone or per-item control
- Approval for sensitive movements
- One connected history
Four connected storage-operation components
Control the Map, Capacity, Movements and Reconciliation
Each component remains visible so storage can be managed as an accountable operating system rather than a collection of unconnected racks and spreadsheets.
↔ Swipe through the storage-operation components
Location Hierarchy and Designer
Build the physical structure and visual map from warehouse to the smallest controlled location.
WarehouseZoneRackBin or rail
Allocation and Capacity
Assign clients, items, containers and capacity with square-foot and cubic-foot visibility.
Client assignmentSq ftCubic ftRecurring value
Client-Managed and Shared Control
Define access, responsibility and approval where clients operate all or part of the space.
Dedicated zoneShared zonePermissionsApproval
Movement and Reconciliation
Move, transfer, retrieve and reconcile inventory while retaining location history and exceptions.
ScanTransferReconcileHistory
See storage operations in action
Follow the Facility from Location Design to Reconciliation
Start with the complete storage-operations architecture, then move through hierarchy design, zone setup, client allocation, item placement, visual mapping, client-managed permissions, movement, utilisation and reconciliation.
↔ Swipe through the Storage Operations and Location Control walkthrough
01
Model the physical facility
Model the physical facility
Full Location Hierarchy and Visual Designer
The hierarchy should describe the actual facility from country and city through warehouse, floor, zone, aisle, rack and the final controlled storage location.
The designer should support full-screen use, drag-and-drop structure, client assignment and visual understanding without forcing every facility into one rigid template.
Flexible hierarchy
Full-screen designer
Visual location map
Full-screen designer
Visual location map
↔ Swipe through location hierarchy and designer controls
Facility Hierarchy
Create the required levels for each site and storage type.
- Country, state, city and warehouse
- Building, shed, floor and area
- Zone, aisle or lane
- Rack, shelf, bin, rail or floor slot
Operational Locations
Include non-storage locations used during movement and handling.
- Dispatch and receiving bays
- QC, photography and care areas
- Security or exception hold
- Client site, vehicle or transit location
Visual Designer
Build and edit the structure through an operational map.
- Drag-and-drop hierarchy
- Full-screen working mode
- Search and expand/collapse
- Client and capacity overlays
Location Governance
Prevent uncontrolled deletion or modification of locations containing inventory.
- Active and inactive status
- Parent-child validation
- Inventory and task dependency check
- Approved archive or replacement route
02
Assign space and inventory accurately
Assign space and inventory accurately
Client Allocation, Capacity and Utilisation
Capacity can be allocated as a full zone, a partial zone or shared controlled space. The system should support practical allocations such as one-and-a-half zones where the commercial and physical model allows it.
Square-foot, cubic-foot and recurring-value fields remain connected so space usage can be reviewed operationally and commercially.
Full or partial zones
Sq ft and cubic ft
Recurring-value validation
Sq ft and cubic ft
Recurring-value validation
↔ Swipe through allocation and capacity controls
Client Space Assignment
Assign a complete zone, partial zone or approved shared capacity.
- Entire zone to one client
- Partial-zone allocation
- Shared capacity with clear boundaries
- Start, end and review dates
Item and Container Allocation
Place items, boxes, trunks, crates and rails into the selected location.
- Scan or search inventory
- Drag and drop allocation
- Container-to-location relationship
- Bulk placement where approved
Capacity Measurement
Measure available, assigned and occupied space in the units relevant to the facility.
- Square-foot capacity
- Cubic-foot capacity
- Item, container and rail counts
- Available and occupied balance
Recurring Value and Validation
Keep the recurring commercial value connected to the allocation.
- Rate and recurring value
- Billing start and review date
- Zero-value warning where inappropriate
- Approval for free or exceptional allocation
03
Support clients who operate their own space
Support clients who operate their own space
Client-Managed Zones and Shared Operational Control
Some clients rent storage capacity and manage their own merchandise, staff and day-to-day movements. Vault should not force managed-service workflows onto those clients.
The system can still provide agreed visibility, access control, location structure, QR identity and boundary-level movement history.
Client users
Zone-level permissions
Optional Vault support
Zone-level permissions
Optional Vault support
↔ Swipe through client-managed and shared controls
Client-Managed Zone
Give the client approved operational control inside the assigned space.
- Named client users
- Zone or location permissions
- Client-created movements where approved
- Client responsibility history
Boundary Controls
Record the actions that cross from client-managed space into Vault control.
- Inbound and outbound handover
- Vault service request
- Cross-zone movement
- Security or exception escalation
Shared Responsibility
Divide control by location, movement type or inventory group.
- Vault-managed receiving
- Client-managed internal movement
- Vault-managed retrieval or dispatch
- Approval for sensitive inventory
Optional Visibility and Identification
Add only the controls useful to the client’s operating model.
- Location visibility
- Optional package or item QR
- Movement and access reports
- Periodic reconciliation service
04
Control every movement and discrepancy
Control every movement and discrepancy
Transfers, Retrieval, Reconciliation and Exceptions
Every movement should record the source, destination, item or container, responsible user, date, time and operating reason.
Physical reconciliation compares the system location with the actual location and routes missing, duplicate or unexpected inventory into an accountable exception workflow.
Scan-controlled movement
Multi-site transfer
Physical reconciliation
Multi-site transfer
Physical reconciliation
↔ Swipe through movement and reconciliation controls
Internal Movement
Move inventory between controlled locations inside the same facility.
- Source and destination scan
- Item or container selection
- Movement reason
- Immediate location update
Multi-Site Transfer
Move inventory between warehouses, client sites or transit locations.
- Transfer-out location
- Transit state and vehicle
- Transfer-in verification
- Chain of custody
Physical Reconciliation
Compare what the system expects with what the team physically finds.
- Location-by-location scan
- Expected versus found
- Unlisted or misplaced inventory
- Reconciliation completion report
Exception and Hold
Prevent uncertain inventory from silently returning to normal availability.
- Missing or duplicate item
- Wrong location or client
- Damaged container or restricted access
- Assigned owner and resolution history
Storage operations workflow
Design, Assign, Allocate, Move, Measure and Reconcile
The sequence keeps facility structure, client responsibility, physical placement and commercial capacity connected.
↔ Swipe through the storage-operations workflow
Design the Map
Create the facility hierarchy, operational areas and smallest controlled locations.
Assign Responsibility
Define Vault-managed, client-managed or shared control by zone and workflow.
Allocate Capacity
Assign full, partial or shared space with square-foot, cubic-foot and recurring values.
Place Inventory
Scan, search or drag items, containers and rails into the approved location.
Move and Measure
Control movements and monitor occupied, available and reserved capacity.
Reconcile
Verify the physical facility, resolve discrepancies and retain the full history.
The Level 1 Storage page sells capacity
It explains storage-only, client-managed and optional-support propositions.
This page explains managed operational control
It covers location design, allocation, movement, utilisation and reconciliation services.
Storage-operation responsibility
Keep Capacity Ownership, Physical Movement and System Updates Aligned
The approved operating model should show who can assign space, move inventory, change locations, reconcile the facility and resolve exceptions.
Responsibility
Client or Seller
Vault Operations
Manager or Facility Owner
Approve capacity and operating model
Responsible
Assess operational requirement
Approve facility allocation
Build and govern location hierarchy
Provide client requirements
Configure where scoped
Approve structural changes
Allocate items and containers
Client-managed where approved
Responsible where scoped
Review sensitive areas
Internal and multi-site movement
Move within approved permissions
Execute where scoped
Approve restricted movement
Capacity and recurring-value review
Approve commercial terms
Maintain operational values
Approve exceptions
Reconciliation and exception resolution
Clarify client-controlled activity
Record and investigate
Approve final resolution
↔ Swipe through the storage-operation responsibility views
Client or Seller
- Operating model Approve
- Client-managed movements Responsible where approved
- Commercial terms Approve
- Client activity Clarify
Vault Operations
- Location configuration Responsible where scoped
- Allocation and movement Responsible where scoped
- Utilisation records Maintain
- Reconciliation Record and investigate
Manager or Facility Owner
- Facility structure Approve
- Restricted areas Control
- Exceptional values Approve
- Final resolution Approve
Different storage-operation requirements
Configure the Map and Controls Around the Facility
The hierarchy, capacity unit, movement process and responsibility model should reflect the actual inventory and site.
↔ Swipe through the storage-operation use cases
Storage Operations and Location Control FAQs
Common Questions Before the Facility Is Mapped
The final scope depends on the site structure, storage units, operating responsibility, capacity model, movement volume and reconciliation requirements.
How is this different from the Level 1 Storage page?
The Storage page explains storage capacity and commercial operating models. This page explains the managed operational work used to map locations, allocate inventory, control movements and reconcile the facility.
Can an entire zone be assigned to one client?
Yes. A complete zone can be dedicated to one client, subject to facility approval and the selected operating model.
Can a client use part of a zone?
Yes. Partial-zone and shared-capacity allocations can be supported when the physical boundaries, permissions and commercial values are clear.
Can one-and-a-half zones be allocated?
Yes, where the facility structure and commercial model support it. The allocation should show the exact capacity and boundaries rather than forcing whole-zone quantities.
Are square feet and cubic feet both supported?
Yes. Square-foot and cubic-foot capacity can both be recorded, together with item, container or rail counts where useful.
Can the client manage its own space?
Yes. Client-managed zones can use named users, permissions and optional visibility while Vault records the agreed handover and boundary events.
Can items be allocated through drag and drop?
Yes. The designer can support drag-and-drop allocation together with scan and search workflows.
What happens when an allocation has no recurring value?
The system should warn when a recurring commercial value is expected. Free or exceptional allocations should require an approved reason.
How are multi-site transfers controlled?
The item moves from the source location into transit and is verified into the destination location, preserving chain of custody and timestamps.
What happens when physical inventory is not in the expected location?
The discrepancy moves into an exception workflow for investigation, correction and approved resolution rather than being silently overwritten.
Begin with the real facility and operating responsibility
Tell Us How the Space Is Structured, Assigned and Used
We will map the hierarchy, capacity units, client assignments, location controls, movement workflows, recurring values and reconciliation requirements.