Move from an approved outbound or commerce commitment into reservation, picklist creation, exact-item verification, packing, documents, dispatch, handover, return receipt, condition review and restoration—while preserving ownership, shortages, exceptions and every physical custody change.
Operate and Fulfil begins when an approved request or committed transaction requires physical action against controlled inventory. The fulfilment owner can be Vault, the client or a hybrid model. The workflow ends only when the applicable outbound or return lifecycle reaches its correct terminal state.
The physical operator can differ by client or item. What should remain explicit is who owns the fulfilment decision, who performs the physical work, where stock is reserved and what evidence confirms each handover.
Vault teams reserve, pick, verify, pack, dispatch and process approved returns within the selected managed service scope.
The client controls physical fulfilment while Seller Central retains the approved request, reservation and relevant status history.
Vault and the client divide fulfilment by item, site, channel, workflow stage or approved exception.
The workflow connects approved demand to physical inventory without allowing commercial or system status to get ahead of what has actually happened on the warehouse floor or at handover.
Confirm the requested items, timing and fulfilment ownership, reserve eligible stock and create a picklist tied to current physical locations.
Verify exact identity and quantity during picking, resolve shortages and pack the approved inventory with required QC evidence.
Complete applicable documents, labels and loading evidence, then record dispatch, delivery, pickup or collection handover.
For returnable inventory, reconcile what came back, inspect condition, complete required care and restore stock only after final approval.
Start with the complete fulfilment architecture, then move through item-level request scope, reservation, picklists, scan verification, shortages, packing/QC, documents, dispatch, handover, return receipt and approved restoration.
The request should show exactly which items, quantities or lines are required—not only the number of items. The operator needs the client/project context, requested date or slot, destination and any return expectation before physical work starts.
Reservation should protect the selected stock from conflicting commitments while remaining separate from the actual pick. A reserved item can still fail later verification if it is missing, damaged or otherwise unavailable.
Show the operator the actual inventory requested.
Reserve only stock currently eligible for the commitment.
Connect the commitment to the current physical storage record.
Release work only when the request, responsibility and inventory state are ready.
Picking should be optimised for repeated warehouse work: show the exact requested item, current location and scan field prominently, then confirm successful picks quickly without forcing unnecessary page navigation.
If the expected inventory cannot be found or is unsuitable, the workflow should create a shortage or exception rather than allowing a different item to be substituted silently.
Give the picker the minimum information needed to act quickly.
Confirm the physical item before marking it picked.
Handle missing or pre-packed inventory without corrupting the pick record.
Confirm that picked inventory is suitable for dispatch.
Documents and labels can be required before dispatch, but generating them does not prove the goods left the facility. The dispatch stage should record the actual physical handover and any required carrier, driver, vehicle, loaded-material or recipient evidence.
For client pickup, courier delivery or event movement, the exact fields can differ. The workflow should record the handover mode that actually occurred rather than forcing every fulfilment into one logistics pattern.
Generate the documents required for the selected movement.
Confirm the packed material and required documents are complete before release.
Record the moment custody leaves the storage/dispatch team.
Use actual delivery, collection or recipient evidence where available.
Returnable inventory remains part of the active lifecycle after delivery. The system should know what is expected back, when it is due and which custody items or components must return.
When the material comes back, receiving should verify identity, quantity and condition. Laundry, repair, restoration or QC may be required before the item can be put away and made available again.
Keep returnable inventory visibly outstanding after the outward handover.
Verify what physically returned.
Route the returned inventory according to its physical state.
Make a deliberate availability decision after all required return work is complete.
The outward workflow can finish at delivery for non-returnable inventory, while rental, project and other returnable movements continue through return receipt, inspection, care and restoration.
Confirm request scope, availability, fulfilment ownership and reserve eligible stock.
Build item/quantity rows against current locations and release approved work to the picker.
Scan the exact inventory, resolve shortages and complete packing/QC.
Complete applicable documents and record the physical dispatch and transit state.
Record the actual handover and move returnable inventory into return-pending rather than completed.
Reconcile identity/quantity, inspect condition, complete care and approve put-away/availability.
This How It Works page connects those operational stages into one lifecycle. The Services pages explain the managed physical service components in greater depth.
The item must pass identity, quantity/component, condition, care and final reinspection requirements before approved restock or availability.
The client or connected commerce source creates the approved demand. Seller Central coordinates reservation and workflow state. The assigned physical operator performs the pick, pack, dispatch and return work.
Each status represents a different physical or operational reality. Keeping them separate makes shortages, custody and returns easier to understand and audit.
The exact workflow depends on fulfilment ownership, inventory type, delivery method, commercial model and whether the inventory is expected to return.
They should. The fulfilment view should show the requested item/line list, not only an aggregate item count, so the operator knows exactly what must be reserved, located and picked.
No. Reservation protects eligible inventory from conflicting commitments. Picking is the later physical act of locating and verifying the item.
Yes. Phone camera, hardware scanner/gun and manual entry can be used to verify the custody QR or other accepted code against the picklist.
The picker should be able to mark a shortage or location exception. The workflow can then investigate, approve a permitted substitute or take another approved action without silently completing the row.
Where the approved workflow supports it, a pre-packed override can be used before packing. Sensitive post-pack overrides should require stronger supervisor control.
No. Documents and labels are preparation states. Dispatch should be recorded only when the physical handover actually occurs.
Yes. Fulfilment ownership can be Vault-managed, client-managed or hybrid according to the approved model, with product-level exceptions where supported.
The lifecycle continues in return-pending. The inventory remains committed until it is physically returned and passes the required reconciliation, condition and restoration process.
No. Identity, quantity/components, condition, care/restoration, final reinspection and the approved availability decision must complete first.
The next How It Works stage is Publish and Scale, where approved inventory, content and operating readiness can be connected to selected commerce destinations and scaled across channels, sites and clients.
Use item-level request visibility, reservation, location-aware picking, scan verification, packing/QC, accountable dispatch and controlled return restoration so the physical inventory state never falls behind the commercial promise.
Login