Library · 03.03 · Fulfillment & Inventory

How to record and resolve warehouse receiving discrepancies

Physical Goods Editorial · Last reviewed October 9, 2026

Learn to document warehouse receiving shortages, overages, damage and count uncertainty, and control affected stock until reconciliation and release.

A warehouse receiving discrepancy is a documented difference between the expected inbound shipment and what the warehouse can verify physically or identify correctly—such as shortage, overage, damage, wrong SKU, or an incomplete or inconsistent record. Document the original expectation and counted reality, contain affected stock, and assign the next decision before changing available inventory. A signed carrier delivery receipt does not prove case contents or automatically authorize release for customer orders.

This chapter provides a receiving-control method for merchants, 3PLs and operating partners. It applies to general merchandise under an agreed receiving procedure; regulated product handling, worker safety, carrier claims, legal acceptance and transfer of title may require separate specialist or contractual decisions. The method is not a substitute for warehouse-specific SOPs or an inspection of a live facility.

A receipt discrepancy is provisional if the physical verification was carton-level or sampled rather than a complete agreed unit count. Record the count method alongside the shortage, not in a distant note. Warehouse-posted stock may still require independent merchant approval before becoming saleable; actual claims deadlines depend on contract and relevant law.

First decision: what status is the shipment actually in?

A received shipment can therefore have completed physical handling while leaving an open supplier shortage, insurance question, quality hold or inventory synchronization issue. Never force those different matters into one status called “received.”

Practical first action: Request the shipment notice/PO revision, unit conversion, carrier handoff record, warehouse count by SKU, evidence of damage or unknown stock, the current WMS hold/available transaction, and the named person authorized to approve correction or release. If one of those facts is unknown, record the gap and keep the affected units unavailable pending an approved decision.

1. Use the procedure at the right boundary

This method covers planned inbound stock arriving at a warehouse, a supplier replenishment, an inter-warehouse transfer or a return-to-stock delivery that is treated as a controlled inbound movement. It is appropriate for routine consumer products where handling and release can be decided through the company's authorized operating procedure.

It does not establish food, medical, pharmaceutical, hazardous-material, temperature-controlled, dangerous-goods, recalled-product or other specialist receipt protocols. It cannot authorize the release of goods held by customs or a regulator. Such products require the specific facility, product, transportation and professional procedures that apply to them. Warehouse-worker safety remains governed by applicable requirements and site procedures, not by a public editorial checklist. OSHA identifies materials-handling and powered-industrial-truck risks in receiving environments.[3]

For a provider-selection decision, consult the existing How to evaluate a U.S. 3PL. For the advance operating requirements, see Define distribution requirements before choosing a 3PL. This chapter owns the receipt and discrepancy process after the scope is established.

2. Establish the unit of account before freight is booked

A good receiving instruction specifies what “one” means. Consider a pallet containing 20 cartons, with 12 units per carton. One pallet, 20 cartons and 240 eaches are not interchangeable stock quantities. A warehouse may count pallets at the dock and cartons at the breakdown station, while the merchant sells eaches. If the conversion is not defined and controlled, the warehouse can be physically right and the stock ledger wrong.

The product master and shipment notice should state, as applicable:

The shipment notification is commonly called an advance shipping notice (ASN). It is a data artifact, not proof of shipment contents. Attach the version and time it was issued, and identify how subsequent changes will be acknowledged. “See packing list” is not enough if the packing list cannot be matched to the physical labels.

Where a shipment uses GS1 logistics labeling, the Serial Shipping Container Code (SSCC) identifies the logistics unit; a Global Trade Item Number (GTIN) identifies a trade-item type. They serve different purposes. GS1's logistic-label guidance describes scanning the SSCC to associate a physical unit with electronic despatch information; the SSCC is the required identifier within the GS1 Logistic Label standard, not a universal regulatory label requirement on every shipment.[1][2] Use the actual identifier scheme agreed with the warehouse and receiving parties.

3. Define each receiving event, not one ambiguous status

Use the six stages summarized above as the acceptance and evidence sequence, even when software compresses them into fewer display labels:

1. Expected. A shipment record exists with SKU, quantity, pack conversion, reference and intended destination. No physical stock has been counted.
2. Arrived. A freight unit or parcel is present at the dock; carrier handoff and visible external condition are recorded as required by the agreement. This does not establish SKU-level contents.
3. Counted. The agreed inspection/count scope has been performed. Variances, unidentified items and physical damage are recorded at the right unit of measure.
4. Accepted or held. Conforming goods are accepted according to the agreed policy; suspect, nonconforming or unidentified goods remain segregated or blocked from sale. A hold needs both a physical location/control and appropriate system status.
5. Posted. The warehouse's authoritative inbound transactions reflect accepted units and held/unresolved units distinctly. Duplicate postings and conversions are checked.
6. Released for sale/use. The approved availability decision has propagated to the required order/commerce systems, after any other applicable restrictions have been satisfied. Posting a physical receipt does not necessarily authorize sale.

For each event capture actor, timestamp, source record, quantity, unit and the next decision. If Shopify receives a purchase-order or transfer receipt, its product inventory may become Available by default under the relevant flow; configure and verify the merchant-specific hold/release process rather than assuming physical arrival remains non-saleable in every application.[4] State whether the warehouse may partially accept a shipment or whether everything must remain pending; the correct rule varies with the product and agreement. When a warehouse-management system automatically posts from an ASN or pallet scan, validate the configured controls rather than relying on an idealized diagram.

4. Determine the count and inspection level intentionally

Inspection is a matter of risk, economics, provider capability and product requirements. Possible contracted methods include:

• Logistic-unit confirmation: Match labeled pallets/cartons to notice references. Efficient for an agreed trusted flow, but by itself may not detect hidden missing or damaged eaches.
• Case-level count: Confirm carton identity and case quantities, with selected openings where the approved procedure requires them. A sealed carton count still depends on pack accuracy.
• Each-level verification: Open and count each sellable unit in scope; may be appropriate for high-value, irregularly packed, disputed or sample shipments, but carries labor/handling costs and potential repack impacts.
• Sampling: Inspect a documented subset under a company-approved sampling rule. Define population, sample selection, defects, threshold and escalation; do not advertise an invented “industry standard” sampling percentage.
• Traceability controls: Record lot, serial, expiry or other identifying information where the product, customer or applicable rule actually requires it. Validate how exceptions affect traceability.

Use the same acceptance vocabulary for operators and systems. “100% received” might mean cartons physically present, lines posted or every unit inspected; require the record to name which. Capture the agreed deadline for the receiving report and how any missed appointment or incomplete documentation changes the sequence—do not insert a generic 24-hour service promise.

5. Design the discrepancy report so an outside party can investigate

A usable exception is not “short 2 / damaged 3.” It links the expectation to the observed physical event:

Photos should demonstrate what was seen, not assert causation. Keep original files, note their capture time, and associate images with carton/lot or unit identifiers where practicable. Carrier claims, contractual shortage windows and insurance evidence are case-specific; check actual contracts and specialist instructions before promising a claim result.

Count scope and physical-unit evidence are part of the result

A line quantity without which carton/pallet/handling unit and how it was counted can conceal a mix-carton shortage. Set the agreed method before the receipt: full each-level scan, confirmed sealed-case count using a verified pack ratio, or sampled inspection with population and sample size. Sampling can support a risk decision but cannot be described as a full each-level count. Record carton or pallet IDs when feasible, seal/condition, photographs, scan device/transcript, recount actor and time, WMS transaction and receipt acceptance versus hold. The physical evidence standard is shaped by the product, supplier, agreement and claims rules, not one universal audit percentage.

Track at least three separate clocks: warehouse discrepancy correction, carrier damage/loss notice, and supplier short/quality or contractual notice. For each, write owner, starting trigger, actual rule/source, deadline, preservation request and recipient acknowledgment. Stock acceptance or sale release does not close a separate financial claim.

6. Worked receiving reconciliation (hypothetical)

A brand advises the warehouse that one inbound shipment contains 20 cartons × 12 eaches = 240 units of the same SKU. A carrier delivery record shows 20 cartons handed over. The agreed each-level verification establishes 228 units across 19 cartons plus 10 units in the remaining opened carton. This is a demonstration of an each-level count, not an assumption that unopened cartons necessarily contain the declared quantity. Of the 238 units physically observed, three fail the agreed condition check and enter hold.

This is an arithmetic teaching example, not company data. The checked physical count satisfies 228 + 10 = 238, and the disposition satisfies 235 accepted + 3 held = 238 counted; the separately identified shortage is 240 expected - 238 counted = 2. Do not post 240 as available merely because 20 cartons were signed for; do not post 238 as available while three units remain on hold. A reconciled entry should make the two missing units and three held units independently visible. The company may later accept a correction or approve a disposition, but a commercial write-off is not the same event as a physical count.

A completed discrepancy line should preserve the investigation

For the fictional shipment, the discrepancy record would identify the expected document revision, SKU and each-level count, two unlocated units, three physically held units, the WMS transaction or pending transaction, the reason those held units cannot be allocated, photograph or scan references, and two separate next actions: investigate the shortage and approve disposition of the damaged units. The warehouse may establish what it saw; a designated company authority decides commercial acceptance or stock release. A working discrepancy register should preserve this same evidence and decision history for independent inspection.

The exception must have a next owner

The receiving party can report the physical facts. The supplier/shipper or carrier may need to provide packing and custody evidence. The company assigns someone to decide whether a purchase-order short-shipment claim, inventory correction, rework or other commercial action is appropriate. The operations coordinator follows the open issue to documented resolution but does not invent authority to settle it. If a specialist product-safety assessment is necessary, the held units remain held pending that decision.

7. Classify the issue before trying to resolve it

Do not confuse commercial/legal acceptance or title passage with warehouse acceptance. Those are governed by the applicable sale, shipping, logistics and other agreements and law, not by a generic receiving checklist. A warehouse's stock flag cannot answer who legally owns goods.

Resolution paths

After classifying the discrepancy, the documented resolution may be:

• Data correction: The ASN or product conversion was wrong; source documents and affected system records are corrected with change history.
• Physical recount: A verified second count replaces the first observation; explain the difference, not simply the new total.
• Found stock / mislocation: Units are recovered; location and available/held status are reconciled.
• Supplier shortage or overage: Commercial acceptance or rejection is decided by an authorized party; the warehouse records the stock it actually possesses.
• Damage disposition: Units stay held, are reworked, returned, destroyed or released as permitted by the proper authority, with supporting record.
• Unresolved claim: The operational receipt can be reconciled to known physical stock while a financial or carrier/vendor claim stays open in its own record. Do not fabricate stock to force a zero variance.

Before changing quantities, preserve original observation, approving authority, reason, entry operator and transaction ID. Silent correction is dangerous because it may remove the only evidence needed to investigate an earlier claim.

8. Allocate responsibilities and define the hold rule

Use the cross-functional responsibility matrix from 08.01 (planned) for the full contract-by-contract allocation. At the receiving desk, the minimum decision chain is:

A warehouse should be able to isolate an apparent safety or damage risk immediately under its site procedures without waiting for someone to approve a saleability decision. Subsequent release or destruction is a different authority. If no responsible approver is reachable, continue the safe hold rather than deeming a suspect unit approved.

9. Verify the system instead of trusting dashboard labels

Before first replenishment or when changing a provider, run one controlled receipt through its actual data flows. The acceptance test should attempt:

1. Correct ASN, matching physical inbound and normal release.
2. Short counted quantity despite a matching carton count.
3. Damaged units entered in a physical quarantine location and a non-saleable system state.
4. Unknown SKU, duplicated notice or repeated barcode scan; verify it does not create duplicate stock.
5. Partial acceptance with a later approved adjustment; confirm audit trail and changed downstream availability.
6. Interrupted sync between warehouse and storefront or enterprise system; verify backlog detection and replay without doubling stock.

Record expected result, observed result, evidence link, owner, corrective action and retest decision. Test completion is not a compliance certificate, inventory accuracy guarantee or a substitute for a site audit. It proves that a specified path behaved a specified way under the conditions tested.

10. Close the receipt only with a reproducible record

Use an agreed receiving and discrepancy register. A receipt is complete for operational purposes only if the company can answer:

• What was expected, at which document revision and unit of measure?
• What physically arrived and what count/inspection was performed?
• What was accepted, what is held, what remains unresolved and where are those units?
• Which authoritative transactions and downstream availability changes occurred?
• Which discrepancies remain open under separate investigation, claims or compliance holds?
• Who approved the inventory disposition, and which person takes the next exception action?

Do not confuse closure categories. A physical receipt may be completed while a supplier shortage claim remains unresolved. A claim may be settled while the warehouse inventory still needs an adjustment. The completed record should preserve both states, not pretend they are one event.

Related reading and technical sources

A working receiving and discrepancy register should preserve the shipment header, SKU-level expected/counted/held/released ledger, discrepancy evidence and closeout approval. To define the inbound requirement, see Distribution Requirements. The existing 3PL evaluation guide addresses provider selection rather than receiving-desk control.

References (primary sources, checked October 8, 2026):

1. GS1, GS1 Logistic Label Guideline. Supports the distinction between logistic-unit SSCC and trade-item identity, the match between electronic despatch advice and logistics units, and configurable receipt checking. GS1 label prescriptions apply when this standard is used.
2. GS1, What is a logistics unit and how is it identified?. Confirms the SSCC identifies a logistic unit such as a pallet, case or parcel; does not establish any warehouse's ability to scan it.
3. OSHA, Warehousing — Hazards and Solutions. Provides examples of material-handling hazards in U.S. warehousing; not an assessment of any named site or a complete safety procedure.
4. Shopify Help Center, Understanding inventory states. Explains platform on-hand, incoming, unavailable and available states and notes the stock-state outcomes of specific receiving flows. Shopify is a platform example, not a universal WMS rule.

Method status: The acceptance sequence, discrepancy taxonomy and instrument are Physical Goods editorial recommendations. Supplier notices, service levels, claim deadlines, sampling methods, stock adjustments and release authority are client-, provider- and product-specific. Specialist compliance, contractual and safety review may be required. Revalidate references if GS1 standards, warehouse systems or the physical/contractual operation materially change. No particular warehouse capability or client outcome is represented.