Ecommerce Receiving Process: Step-by-Step Warehouse SOP

Your receiving dock is where inventory accuracy starts or falls apart. According to the Warehousing Education and Research Council (WERC), warehouses that enforce structured receiving SOPs achieve 99%+ inventory accuracy, while those without standardized processes typically sit between 85% and 95%. That gap compounds into mis-picks, stockouts, and unreliable reorder signals.

If wrong quantities enter the system, every pick and reorder decision downstream is wrong too. A tight ecommerce receiving process prevents that from happening, and small business warehouse management software with PO-matched receiving catches discrepancies before they reach your shelves.

PO matching before unloading

Every inbound shipment should be tied to an open purchase order before a single box is opened. PO matching catches supplier errors at the earliest possible point, when they are cheapest to resolve.

The pre-arrival checklist:

• Confirm the PO number exists and is in “open” or “expected” status.
• Verify expected SKU count and total unit quantity on the PO.
• Check the supplier’s advance shipping notice (ASN) if available; roughly 60% of mid-market ecommerce warehouses now receive ASNs electronically.
• Stage a landing zone on the dock separated by PO so mixed-supplier pallets do not get cross-counted.

Without PO matching, your team is counting blind. A solid purchase order management workflow upstream makes this step fast instead of frustrating.

Scan verification at the dock

Barcode scanning cuts receiving mistakes by 67% versus clipboard-only workflows

Manual counting alone misses errors. Barcode scanning at the dock adds a second verification layer that cuts receiving mistakes by an estimated 67% compared to clipboard-only workflows.

Run this scan-and-count flow for every inbound shipment, no exceptions:

1. Scan the PO barcode (or enter the PO number) to pull up expected lines.
2. Scan each SKU using a GS1 barcode on the product or case. The system should auto-match the scanned SKU to the PO line.
3. Count units per SKU and enter the received quantity. For case-pack items, scan the case barcode and confirm the inner count.
4. Flag mismatches immediately: if the scanned SKU is not on the PO, quarantine that item rather than force-receiving it.

Teams that scan every unit at the dock typically see receiving accuracy above 99.5%, while teams relying on visual checks alone average closer to 95%. Scanning also creates a timestamped digital record, which is critical for supplier disputes. Upzone supports both dedicated barcode scanners and mobile device cameras for dock verification.

Condition inspection and exception handling

After scan verification, every unit needs a condition check before it moves to storage. This is where you catch damage, expiry problems, and labeling issues.

Inspect for:

• Physical damage: crushed cartons, wet packaging, broken seals.
• Expiry dates: for perishable or date-sensitive SKUs, reject anything arriving with less than 75% of shelf life remaining (a common FEFO rule).
• Missing or unreadable labels: items without scannable barcodes cannot be picked accurately later.
• Wrong items: product that does not match the PO line description, even if the barcode scans correctly.

When exceptions occur, follow a structured resolution path:

Exception type	Immediate action	Resolution owner	SLA
Quantity shortage (under 5%)	Log variance, receive partial, notify procurement	Procurement lead	24 hours
Quantity shortage (5%+)	Hold receipt, escalate to supplier	Procurement lead	48 hours
Damaged goods	Quarantine, photograph, log damage code	Receiving supervisor	Same shift
Wrong SKU received	Quarantine, do not receive into inventory	Procurement lead	24 hours
Missing labels	Re-label from master data before putaway	Receiving team	Same shift

Never resolve an exception by adjusting inventory without a reason code. Unresolved variances quietly vanish into daily noise, and you only find them weeks later during a cycle count. Following warehouse receiving best practices for exception logging prevents that drift. An online store inventory management platform with reason-code tracking makes these variances visible in real time instead of burying them.

Putaway procedures

34% of ecommerce warehouses lose 2+ hours per day from improper putaway

Receiving is not complete until every unit is in its assigned bin and confirmed in the system. A 2023 Logiwa survey found that 34% of ecommerce warehouses lose more than 2 hours per day searching for stock that was received but not properly put away.

Putaway rules to enforce:

• No putaway before the count is done. Moving stock to shelves before verification creates phantom inventory.
• System-directed putaway: the WMS or inventory system should suggest the target bin based on product velocity, size, or zone logic. Do not let receivers choose locations ad hoc.
• Scan the bin barcode on arrival to confirm the unit went to the right place. This closes the loop between receiving and storage.
• Confirm putaway in the system same day. Stock that is physically shelved but not system-confirmed is invisible to pickers.

If your warehouse uses multiple storage areas, your ecommerce warehouse setup determines how bins are organized and how putaway routing works. Getting that foundation right makes directed putaway possible.

Once putaway is confirmed, the received inventory becomes available for allocation. From this point, the units enter the pick, pack, and ship workflow and any errors introduced during receiving will surface as picking discrepancies or customer complaints.

Receiving KPIs to track weekly

What is a good dock-to-stock time for ecommerce?

You cannot improve a process you do not measure. Track these 5 metrics weekly and review trends monthly:

KPI	What it measures	Baseline floor	Strong target
Dock-to-stock time	Hours from truck arrival to putaway confirmation	4 hours	Under 2 hours
Receiving accuracy	% of lines received matching PO exactly	95%	99%+
Receiving variance rate	% of receipts with any quantity discrepancy	8%	Under 3%
Putaway confirmation compliance	% of putaways confirmed in system same day	85%	98%+
Exception closure rate	% of exceptions resolved within SLA	70%	95%+

Best-practice warehouses benchmark dock-to-stock time under 2 hours for parcel-size shipments and under 4 hours for full pallets. If your dock-to-stock time exceeds 6 hours consistently, the bottleneck is usually in PO lookup or putaway routing, not physical labor.

Fold these into your regular warehouse KPIs review and tie them back to overall inventory accuracy targets. A receiving accuracy rate below 97% almost always drags inventory accuracy below the 95% floor.

Minimum receiving record fields

Every receiving record should capture these 10 fields at minimum:

• Date and time of receipt
• PO number
• Supplier name
• SKU (scanned, not typed)
• Expected quantity
• Received quantity
• Variance amount and reason code
• Condition notes (damage, expiry flags)
• Receiver name or ID
• Putaway bin location

Without these fields, you cannot trace where a discrepancy started. The receiving checklist template has this format ready to use.

Quick Reference

The ecommerce receiving process follows 6 stages: PO match, scan verification, condition inspection, exception handling, putaway, and KPI tracking. Warehouses that enforce all 6 stages consistently achieve 99%+ receiving accuracy and dock-to-stock times under 2 hours.

Stage	Key action	Target metric
PO matching	Verify PO status and expected lines before unloading	100% of shipments matched
Scan verification	Scan every SKU barcode against PO	99.5%+ scan accuracy
Condition inspection	Check damage, expiry, labels	Same-shift completion
Exception handling	Log variance with reason code, route to owner	95%+ closed within SLA
Putaway	System-directed bin assignment, scan to confirm	98%+ confirmed same day
KPI review	Track 5 receiving metrics weekly	Dock-to-stock under 2 hours