Move digitised inventory into the correct warehouse, zone, rack, shelf, bin, rail, floor slot, container or approved client-managed area—then maintain location history, movement controls, holds, counts, discrepancies, occupancy and retrieval readiness.
Store and Control begins after the required custody identity and digital record exist. It establishes where the inventory physically lives and who controls movement from that point forward. Storage responsibility can be Vault-managed, client-managed or hybrid according to the approved operating model.
The level of day-to-day control can differ by client. Some clients need Vault teams to manage every put-away and retrieval; others may control inventory inside an allocated space while the platform maintains visibility at the appropriate location level.
Vault teams control put-away, location changes, retrieval, counts and custody activity within the selected managed service scope.
The client controls inventory within an approved allocated space while Seller Central records the storage relationship and agreed visibility.
Vault and the client divide movement or storage responsibility by site, zone, category, workflow or inventory group.
Storage control is more than saving a location field. The system should know the storage hierarchy, the current physical position, how the item got there, who moved it and whether the location record still matches reality.
Select the correct storage type and exact location, then verify the item has physically reached that position.
Track internal moves, temporary areas, transfers, retrievals and custody changes with responsible user and time history.
Understand allocated areas, usable space, occupancy and where dedicated or shared storage responsibilities begin and end.
Use physical verification, holds and reconciliation to keep the location and quantity record trustworthy over time.
Start with the complete storage-control architecture, then move through repack/container linking, location allocation, scan-verified put-away, movement history, client areas, occupancy, cycle counts, holds, discrepancies and approved reconciliation.
After digitisation, an item may be repacked or grouped into a box, peti, crate, trunk, rail or another container before final storage. The container relationship should remain linked to the individual custody identities where item-level tracking is required.
Put-away should record the exact physical location appropriate to the operation—such as warehouse, zone, aisle, rack, shelf, bin, rail, floor slot or another approved location type—and confirm that the physical movement actually happened.
Group items physically without losing individual custody identity.
Use the depth required by the site rather than forcing the same structure everywhere.
Choose a physical position appropriate to the inventory.
Confirm the system location matches the physical position.
An inventory item can leave its storage position for photography, QC, care, picking, client inspection, transfer or another authorised purpose. The movement record should change the current location while retaining where the item came from.
Temporary operational areas should be treated as real locations where useful so an item does not appear “missing” merely because it is between shelf and final destination.
Move inventory from one valid storage position to another without rewriting history.
Keep items visible while they are away from normal storage.
Control handover when inventory crosses a meaningful responsibility boundary.
Keep the current state explainable through prior activity.
Capacity can be represented differently across garments, shelving, bins and bulky inventory. Square feet can matter for floor allocation, while cubic capacity or location counts can be more useful for certain storage types.
A client can be assigned a full zone, part of a zone or another approved area. Where the client manages the interior arrangement, the platform can preserve the allocated-space boundary without requiring Vault to control every internal move.
Allocate an approved area to one client where that model is selected.
Use granular item/location control where several clients share the same physical structure.
Measure available space with the dimensions meaningful to the site.
Keep system visibility aligned with who actually controls the physical area.
Location accuracy degrades if moves, handovers or quantity changes occur outside the recorded workflow. Counts and reconciliation provide a controlled way to detect and resolve those differences.
A discrepancy should not be “fixed” by editing the record without evidence. The count result, expected state, physical finding, approval and adjustment should remain attributable.
Verify selected physical locations without stopping the entire operation.
Identify why physical and system state do not match.
Prevent uncertain inventory from being treated as freely available.
Correct the record through an attributable adjustment rather than silent editing.
The journey establishes the trusted current location, then keeps that location accurate as the inventory is used and moved.
Confirm storage type, repack/container relationships and the site or client-area destination.
Select the exact rack, shelf, bin, rail, slot, zone or other approved location.
Move the inventory physically, scan/confirm the location and record who completed the put-away.
Track internal moves, temporary locations, transfers, retrievals and responsibility handovers.
Run cycle counts or spot checks and identify inventory/location discrepancies.
Resolve holds, approve adjustments, update occupancy and keep the inventory retrieval-ready for the next stage.
This How It Works page explains where Store and Control fits in the end-to-end journey. The Services page covers the specialist managed operational workflow in greater depth.
An item may be physically stored while still under a condition hold, reserved for another commitment, awaiting catalogue approval or not enabled for any marketplace.
The platform can represent exact item-level location or a broader client-controlled area according to the approved storage model. The recorded level of detail should match who genuinely controls the physical inventory.
The platform can represent both granular managed storage and broader client-controlled areas without forcing every facility into the same map.
The exact storage structure depends on inventory type, facility design, client responsibility, required visibility and the selected storage model.
Not always. Vault-managed shared storage may require granular item-level location, while an approved client-managed dedicated area may only need visibility to the assigned zone or space boundary.
Yes. A warehouse may use building, floor, zone, aisle, rack and bin while another site uses rails, floor slots or client areas. The hierarchy should reflect the actual facility.
Yes. Containers can have their own identity and be linked to contained items where that improves physical handling, while individual item custody identities remain available when required.
Yes, where that operating model is approved. The platform can record the assigned client area while the client manages the interior arrangement according to the agreed visibility and movement rules.
The temporary operational area can be recorded as the current location so the item remains visible until it returns to storage or moves onward.
A transfer can record the origin, destination, released-by, received-by and an in-transit state where used, with discrepancies preserved if the receiving site does not match the transfer record.
Yes, where the facility and locations are configured with useful capacity data. This may include square feet, cubic capacity, location counts or occupancy depending on the storage type.
The difference should become a discrepancy for investigation. Any final quantity or location adjustment should retain the evidence, reason, approving user and before/after history.
No. Stored is a physical location/custody state. Commercial availability can still depend on catalogue approval, condition, reservations, holds, client intent and destination publication.
The next How It Works stage is Operate and Fulfil, where approved demand drives reservation, picking, packing, dispatch, delivery, returns and restoration workflows.
Use the appropriate storage hierarchy, client-area model, container structure, movement workflow, capacity view and count process so inventory remains visible and retrieval-ready for future operations.
Login