Receive a short or damaged inbound shipment without losing the evidence

The ASN expects seventy-two cartons. The receiving team finds seventy, including six with visible damage. A hurried receipt of seventy-two makes the purchase order look complete but creates stock that nobody has seen. Receiving only the sixty-four apparently sound cartons hides goods already in the warehouse's custody.

Record the observed seventy, classify their condition and hold the six pending the authorised decision. Keep the two missing cartons as a shortage against expectation. Availability, commercial acceptance and supplier settlement can then proceed from the same physical facts.

Decide what each quantity means

An advance shipping notice describes an expected shipment. A receiving observation describes what the team counted. Inspection and disposition determine whether those units are usable under the applicable specification and procedure. Finance may require further commercial evidence before accepting an invoice.

Define a unit of measure for each. If one carton contains twelve pieces, the conversion belongs to the item and packaging version. A damaged carton may still contain a complete quantity of goods; visible packaging damage alone does not establish the quantity lost or the disposition.

Microsoft documents both available and unavailable inventory statuses for inbound work. The site must configure and test the receiving path so a condition label produces the intended availability. Microsoft Dynamics 365 — Inventory statuses

Use the receiving location, owner, item, lot where applicable, handling-unit identifier and status as part of the record. The word “received” without those dimensions leaves later teams guessing which stock they may allocate.

Reconcile a receipt without losing the exception

This illustrative case has no other receipts or issues for the shipment. All quantities are cartons; the scenario does not prescribe a product-specific inspection or release decision.

The custody balance is 64 + 6 = seventy. The expectation bridge is seventy received + two missing = seventy-two. The held six are a subset of received stock, so adding them to seventy would double count them.

Later, the authorised reviewer releases four held cartons and approves two for return. Before the return physically leaves, custody remains seventy: sixty-eight available and two awaiting return. On confirmed return dispatch, custody falls to sixty-eight. Keep the two returned cartons separate from the two that never arrived.

This distinction matters to the supplier conversation. Four cartons remain commercially unresolved relative to the original seventy-two if the two missing and two returned cartons both require replacement or credit. The specific financial treatment depends on the accepted contract and disposition evidence.

Capture the evidence before changing the packaging

At the receiving station, link the shipment and package identities to counts, observed condition, photographs where useful and any carrier acknowledgement. Record who observed the condition and when. Preserve a qualified acknowledgement exactly: a signature for pallet count is not necessarily agreement to the carton count inside.

If a safe inspection requires moving or opening packaging, document the before and after observations under the site's procedure. Do not ask staff to preserve a scene in a way that obstructs a safe receiving operation.

Use an exception code that states the fact: short count, damaged outer packaging, unidentified item or conflicting unit. Avoid assigning liability through the first dropdown choice. Operations may establish what arrived while the commercial team later decides responsibility.

Make the hold effective across the workflow

A hold should affect allocation, picking and any availability sent to the client system. A colour on a dashboard is insufficient if the outbound task can still consume the goods.

The interface also needs an explicit receipt boundary. Microsoft's external-ERP integration guidance distinguishes warehouse receipt processes and messages; choose the event your receiving and accounting teams intend to consume. Microsoft Dynamics 365 — Integrating warehouse management with an external ERP

If a receipt message fails, reconcile the actual warehouse record before resending. The warehouse should not receive the same seventy cartons again simply because the ERP did not acknowledge them. Use a persistent receipt reference and record the destination outcome.

Review the first exception from end to end

A spreadsheet exception register can be adequate when receiving transactions remain controlled in the WMS. It needs stable links to the receipt and a clear owner for each open action. A native quality or hold workflow becomes preferable when partial releases and returns are frequent.

Test the complete sequence: short arrival, held stock, partial release, return dispatch and a late missing carton. Confirm whether that late carton is a new receipt against the still-open shortage or an authorised correction, rather than editing the initial count to erase the discrepancy.

Measure time awaiting disposition separately from time awaiting supplier response. Count wrongly available held units as a control failure, even if the total receipt quantity is correct. A high receiving completion rate is not useful when unresolved goods become pickable.

Preserve custody while the commercial decision develops

Receiving does not need to pretend that the shipment was perfect to keep work moving. A complete physical record gives every later decision a stable starting point.

Next actions

1. Define expected, observed, available, held and missing quantities in the receiving procedure.
2. Review one exception using package-level evidence and consistent units.
3. Test that held goods cannot enter the normal outbound path.
4. Follow partial release and return through both the WMS and client ERP.