Make the decision with evidence
From inventory arrival to the first shippable order
Delivered inventory is not automatically available to ship. Receipt, identity, quantity, condition, system availability and order rules must align before the first live order is released.
Prepared for Fulfillment Hub USA with AI assistance. Source and release checks completed on .
Track status without confusing delivery with availability
| Status | Evidence to request | Buyer decision |
|---|---|---|
| Arrived | Carrier delivery record and receipt reference | Confirm arrival without assuming stock is released |
| Received | SKU/count record against the expected inbound inventory | Resolve shortages, overages or unidentified stock |
| Available or held | Sellable quantity and documented hold reasons | Confirm which products can safely be promised |
| Order-ready | Channel mapping, packaging and handling rules checked | Approve the representative test set |
| Released and confirmed | Order status, inventory change and shipment feedback | Reconcile the first live transactions |
Make the expected receipt understandable
Provide the expected SKUs, quantities, identifiers, carton or pallet breakdown, and any relevant lot or expiry information before delivery. Confirm which details the selected workflow supports instead of assuming a document alone creates that capability.
Explain substitutions, bundles and reused barcodes. A receiving team should not have to guess which store listing matches an unrecognized item. Agree how unidentified or damaged inventory will be held and who can authorize a disposition.
Give discrepancies an owner
Compare the expected receipt with the observed count using a common unit. Cartons, inner packs and individual units can produce apparently large variances when the conversion is not explicit. Retain the reference and timestamp behind each count.
For a shortage, overage or condition concern, record the affected SKU, the evidence available, the decision owner and the next check. A delivery signature does not resolve a quantity disagreement, and an unexplained adjustment should not be described as a reconciliation.
Check sellable availability and store mapping
Confirm that inventory approved for release appears against the correct product and location in the connected system. Keep damaged, unidentified, reserved or otherwise held inventory distinguishable from available units.
Check how availability is synchronized to the store and how delays or failures are surfaced. Before a campaign launch, establish which system is authoritative and who can pause sales if availability is uncertain. Do not independently adjust both systems to hide a mismatch.
Prove the first order through the entire path
Use a representative test to verify the product, quantity, packaging, permitted service and expected confirmation. Include an exception that matters to the actual catalog, such as a held SKU or a cancellation, rather than only a straightforward single-item order.
For the first approved live orders, retain the order reference, inventory movement and shipment confirmation. Check the feedback in the customer-facing channel. A fulfilled status in one system does not prove the other system received the update.
Prepare the onboarding conversation
Bring your catalog, store/channel list, inbound plan, order profile, packaging instructions, return rules and desired start window. If the warehouse is not yet chosen, state the inventory origin and customer destinations instead of guessing a facility assignment.
Request guided help when the receiving or integration requirements are unclear. Start direct onboarding when you can provide the business and store information, while keeping operational release subject to the agreed readiness checks.
Method and supporting references
The decision framework is original FHU educational analysis. References explain platform-specific concepts, not FHU capabilities or service commitments. The worked quote example uses fictional inputs and reproducible arithmetic, not market pricing.