Inventory receiving checklist: the SOP that protects every number downstream

Short answer: a receiving process has five jobs — verify the shipment against the PO, count before anything goes on a shelf, record damage and shortages the day they're found, log every discrepancy in one place, and only then update Shopify and put stock away. Skip the order and the errors don't disappear; they travel downstream into your counts, your velocity data, and your reorder decisions wearing the costume of accurate numbers.

Receiving is the cheapest point in your whole operation to catch an error. A wrong quantity caught at the dock costs a phone call to the supplier; the same wrong quantity caught at a cycle count costs an investigation, a stock adjustment, and however many weeks your buying math ran on fiction. This page is the checklist itself, written to be printed.

Why receiving order matters

Two failure modes do most of the damage:

Shelve-first, receive-later. Boxes go straight to the shelf during a rush; someone updates Shopify at end of day from the PO, not the count. If the supplier shipped 90 against an invoice for 96, your system now claims six units that don't exist — phantom stock the storefront will happily sell, which is one of the quieter paths into overselling.

Count-never. The delivery is "checked" by matching box count to box count. Units are assumed, not counted. Shrinkage, packing errors, and wrong items all pass through invisible until a count finds them months later, when the trail is cold.

The discipline that fixes both is one sentence: nothing goes on a shelf until it has been counted and recorded.

The receiving checklist

Print this. Laminate it if your receiving bench is also the lunch table.

Before the shipment arrives

• Have the PO open (paper or screen) with per-line quantities and SKUs visible — not the supplier's invoice, the PO. The purchase order record is the agreement; the invoice is the bill.
• Clear a staging area. Receiving needs floor space; a delivery unpacked in an aisle gets counted twice or not at all.
• Know what "complete" looks like: expected cartons, expected weight if noted, any advance shipping notice.

At the dock — physical check

• Count cartons against the delivery note before signing. Note shortages or crushed cartons on the carrier's paperwork at delivery, not after the driver leaves — carrier claims depend on it.
• Photograph damage before opening: carton condition, labels, pallet state.

Unpacking and counting

• Open and verify carton by carton. Match SKU and variant — not just "the right product": the blue Medium that was ordered but blue Large that shipped is a discrepancy the product name alone won't catch.
• Count each line and write the counted number next to the PO quantity. A tally counter or a pencil tally beats memory on anything over 20 units.
• Pull quality samples as you go: obvious damage, wrong spec, missing components. (Deep pre-shipment inspection happens at the factory; this is the last line of defense.)

Discrepancy log (same day, no exceptions)

• For every line where counted ≠ PO: record date, PO number, SKU, ordered vs received, and one line on likely cause.
• Claim shorts and damages with the supplier while the evidence is fresh — the log entry is the claim. A pattern across three POs ("last three shipments short 6–10%") is a conversation backed by paper; see the supplier scorecard for where ongoing performance tracking goes next.

Update Shopify — after counting, before shelving

• Enter received quantities against the PO, or adjust stock in with the counted quantities — origin "Inventory addition," reason "Received" (Shopify Help Center, "Adjusting inventory quantities," accessed October 2026). Enter the counted number, never the PO number.
• Damaged units that arrived unusable: don't add them to Available. Add only sellable units and record the rest against the discrepancy log.

Put-away

• Stock goes to its bin before the next delivery arrives, with the SKU label facing out. Received-but-unshelved stock gets sold from the staging area and miscounted at the next count — the cycle count guide calls this drift, and receiving is where most of it is born.

Partial shipments: the case that breaks lazy processes

Suppliers ship partials — 60% now, the rest next container — and rush substitutions mid-order. The checklist holds with three additions:

• Receive what physically arrived, against the PO line, and leave the balance open. Never "close the PO" on a partial; the unreceived balance is the thing your next reorder review needs to see, or you'll double-order the shortfall.
• Annotate substitutions at the line level. If the supplier shipped 200 units of the pine version instead of the oak, that's not "short 200 oak, plus 200 mystery units" — it's a substitution you'll need when the customer emails asking why.
• Track the balance with a date. "200 units still owed" needs an expected date or it quietly becomes either forgotten (you under-stock) or assumed-lost-too-late (you reordered and the original arrives).

A worked example of receiving math

Illustrative numbers for a dog-gear store receiving HAR-TRC-M (trail harness, size M):

• PO quantity: 80 units at $16.10
• Cartons signed for: 3 of 3
• Counted: carton 1 = 30, carton 2 = 30, carton 3 = 20 — of which 8 units in carton 3 were water-damaged
• Sellable received: 72. Damaged: 8. Short of PO: 0 shipped short — the shortage is 8 damaged units.

Shopify entry: +72 to Available (reason: Received). Discrepancy log: "HAR-TRC-M — PO #1187 — 8 units water damage, carton 3 — photos taken — claim filed." Supplier claim: 8 × $16.10 = $128.80 credit requested.

What the sloppy version looks like: someone enters +80 from the PO because it's faster. Shopify now advertises 8 harnesses that are damaged garbage in the returns pile. The next cycle count finds 8 missing, logged as shrinkage — theft suspicion lands on your staff for a supplier's wet carton, and the $128.80 claim never gets filed because nobody recorded it.

Making it stick

The checklist fails when receiving depends on whoever happens to be standing nearest the door. Three things keep it alive:

1. One owner per delivery, named on the log. Shared responsibility is no responsibility.
2. The log lives in one place — same spreadsheet, same notebook, same shelf. The log only becomes useful (supplier patterns, shrinkage sources, carrier claims) because it's all in one series.
3. Receiving happens on schedule, not on arrival. If deliveries come Thursday, Thursday afternoon is receiving time, staffed and planned. Dock-surprise receiving is where shelve-first happens.

Where InventoryX fits, in one honest sentence: it watches what happens after receiving — days a SKU runs out and estimated lost sales per SKU — so when your bestsellers go dark because a shipment was mis-received, the pattern shows up in the leak report rather than three weeks later in a count. The receiving discipline itself is yours to keep.

Common questions

What is the correct inventory receiving process? Verify cartons against the delivery note before signing, unpack and count each line against the PO (SKU and variant level, not just product), log every discrepancy the same day, update Shopify with counted quantities, and put stock away before the next delivery. The order matters: count before shelving, record before counting again.

Should I receive stock in Shopify before or after counting? After counting, always. Entering PO quantities without counting creates phantom stock if the shipment is short or damaged — units the storefront can sell that don't exist. Enter the counted number; it takes five extra minutes and it's the difference between records and fiction.

How do I handle damaged or missing inventory at receiving? Photograph damage before opening cartons, note it on the carrier paperwork at delivery, don't add damaged units to available stock, and log ordered-vs-received per line the same day. File the supplier claim while the evidence is fresh — a dated discrepancy log turns "these always arrive short" into a claim with receipts.

How do I record partial shipments? Receive exactly what physically arrived against the PO line and leave the balance open with an expected date. Never close the PO on a partial — the unreceived balance is what prevents double-ordering the shortfall, and annotated substitutions keep variant-level confusion out of your counts.

What's the most common receiving mistake? Shelve-first, receive-later: boxes go to the shelf during a rush and Shopify gets updated from the PO at end of day. It produces phantom stock, oversells, and false shrinkage at the next count — all from one skipped count. The fix is the boring one: nothing on a shelf until it's counted and recorded.

Next step: print the checklist, run your next three deliveries through it exactly as written, and start the discrepancy log even if it's empty. By delivery four you'll know whether your supplier claims, your counts, and your Shopify numbers have been telling each other the truth.