Receiving is the point where a supplier’s shipment becomes your inventory record. Speed matters, but releasing the wrong quantity or variant creates errors that are harder to unwind than a short receiving delay. A useful checklist separates arrival, count, inspection, discrepancy handling, putaway and release.
Before the truck or parcel arrives
Create an expected receipt from the purchase order, transfer or advance shipment notice. Record the facility, expected item identifiers, units of measure, quantities, lot or serial requirements, and appointment or parcel references. Decide whether the operation counts cases, inner packs or eaches; a case of 12 received as one unit can distort every downstream channel.
Assign tolerance and approval rules before the shipment arrives. The receiving team should know whether an overage, substitution, damaged carton or missing label can be accepted, quarantined or must be escalated. Link the inbound record to the supplier and carrier evidence, but keep credentials and personal data in approved systems.
Receive in controlled stages
- Identify the load. Match the appointment, carrier reference and sender to an expected inbound.
- Count what physically arrived. Record sealed-container counts first, then item-level counts at the required control point.
- Verify identity. Scan or compare SKU, barcode, variant, pack size and any lot/expiry fields. Do not substitute a similar-looking product.
- Inspect condition. Photograph or record damage according to policy and isolate affected goods.
- Post the receipt. Record accepted, short, over, damaged and unidentified quantities separately.
- Put away and confirm location. A receipt is not operationally complete when goods remain in an untracked staging area.
- Release eligible stock. Only accepted, located inventory that has passed required checks becomes sellable.
Example: a short and damaged receipt
Suppose an expected receipt contains 100 units. The dock finds 96 correct units, two damaged units and one carton labeled as a different variant. This is a hypothetical example, not a customer result. The operator records 96 accepted, two quarantined and the unexpected carton as an identity exception; two units remain short. Publishing 100 because the purchase order says 100 would hide all three decisions.
The discrepancy owner compares packing documents, requests supplier or transfer evidence, and decides whether to adjust the order, return goods or correct a labeling error. Finance should use the accepted and exception records when reconciling the invoice.
Failure and recovery controls
A scanner outage should trigger a documented offline record with unique receipt references, followed by controlled entry and duplicate checking. If the wrong SKU was released, stop further allocation where practical, identify affected orders and locations, correct the stock movement, and retain the adjustment reason. Never “fix” the balance with an unexplained quantity change.
Track dock-to-receipt time, receipt-to-putaway time, discrepancy rate and aged quarantine separately. Define denominators: discrepancy lines divided by inspected receipt lines tells a different story than discrepant units divided by received units.
Receiving also depends on availability logic. Read shared inventory without overselling and browse the inventory and fulfillment topic hub.
Put the checklist into operation
Run the steps against one representative inbound, including an exception. Keep the purchase/transfer reference, count evidence, discrepancy decision, putaway confirmation and release timestamp together. 1Commerce can connect inventory and fulfillment workflows across selected facilities and channels; exact integrations and operating responsibilities depend on the agreed configuration and service scope.
Explore fulfillment operations or review your receiving handoffs with 1Commerce.