Warehouse Management System Process Flow: Receiving to Shipping

A trailer is unloaded by 07:30, yet at noon the order desk still cannot allocate the stock. The cartons are sitting on the dock in a status nobody can explain, and the receiver who scanned them has gone to lunch. Most warehouses that call their WMS "slow" have this problem: nobody has written down which transaction moves stock from one status to the next, or who clears it when the move fails.

This guide walks the warehouse management system process flow from the advance ship notice to ship confirm, following the stock through inbound, storage, outbound and returns. For each step it gives the WMS transaction, the resulting inventory status, the document, the usual exception and who resolves it, then traces one pallet in dollars and rupees. Our WMS architecture guide explains the software components; this page covers the order in which floor work happens.

The four phases of a warehouse management system process flow

A warehouse management system process flow has four phases: inbound receipt, putaway and storage control, order fulfilment, and shipping with returns. Every step either changes where stock is or changes what it may be used for, and the WMS should record both before the next step can start.

The table below is the reference the rest of this article expands. Read it row by row: the "status after" column tells you what an order allocator can see, and the "resolved by" column tells you whose queue an exception lands in. When a status has no named owner, stock waits in it until somebody notices.

Two statuses deserve attention because they hide stock. "Received" stock is counted as on hand but cannot normally be allocated until putaway confirms a location. "Allocated" stock is still physically in its bin but is no longer free for other orders. Sites that report "available" without separating these two make promises the floor cannot keep.

Before the truck arrives: ASN, appointment and gate check-in

Inbound work starts before anything touches the dock: the WMS needs an expected receipt to receive against and an appointment to plan labour around. If either is missing, receiving falls back to manual counting and the dock clerk becomes the data entry point for the whole building.

The expected receipt usually comes from an EDI 856 ship notice. X12 describes the 856 as listing a shipment's contents together with order, packaging, carrier and loading details. Many suppliers send it at dispatch; some send nothing. Where no ASN arrives, the WMS can still create an expected receipt from open purchase order lines, but it will not know carton counts, pallet identities or lot numbers in advance.

• Expected receipt created: ASN or PO lines load into the WMS with item, quantity, unit of measure and, where supplied, SSCC and lot details for each pallet.
• Appointment confirmed: the dock schedule reserves a door and a time window sized to the pallet count, not just the truck, as our dock appointment guide explains in detail.
• Gate check-in recorded: the guard links trailer number, seal number and driver to the appointment; no inventory status changes at this point.
• Door assignment issued: the yard or dock supervisor calls the trailer to a door when receivers and staging space are free.

The common exception here is an ASN that disagrees with the purchase order, such as a substituted item or a split shipment. Do not let the receiver solve it on the dock. The inbound planner should accept or reject the ASN against the PO before the trailer is called to a door, so the receiver only has to compare cartons with an approved expectation.

Blind receipt or ASN-matched receipt at the receiving dock

Choose ASN-matched receiving when suppliers send accurate pallet-level ASNs, and blind receiving when they do not. The choice decides how a discrepancy is caught: an ASN receipt compares scans with an expectation, while a blind receipt forces a count that is compared afterwards.

In ASN-matched receiving the receiver scans the pallet's SSCC, the 18-digit GS1 serial shipping container code carried in a GS1-128 barcode under application identifier (00). The WMS looks up that SSCC in the ASN and can receive the whole pallet in one scan. The speed is real, but so is the risk: the scan proves which pallet arrived, not how many cartons are still on it.

A hybrid rule works for most sites: accept the one-scan receipt for intact, shrink-wrapped single-item pallets from suppliers with a good record, and force a carton count for mixed pallets, damaged wrap or new suppliers. The resulting goods receipt moves stock to "received" on a dock location and produces LPN labels for anything that did not arrive with its own SSCC.

ASN-matched receiving in a WMS compares each scanned GS1 SSCC, an 18-digit code under application identifier (00), against the X12 856 ship notice. A discrepancy rule that forces a carton count on mixed or rewrapped pallets catches shortages before putaway, when the receipt is still under 30 minutes old.

Over, short and damaged quantities need separate fields, not a single "received" number. Our guide to receiving short or damaged shipments covers how to keep the evidence. For the process flow the point is simpler: the receipt must close with every carton in one of three states (accepted, held or rejected), so that the purchase order shows what is still open.

The incident below shows what happens when a pallet scan is trusted on a pallet that had been rewrapped in transit. The times and document numbers are illustrative.

1. 06:40 Gate check-in: trailer TRL-4417 arrives against appointment APT-22918; ASN SHP-77310 lists 40 cartons on two pallets, 20 cartons each.
2. 07:05 Pallet scan receipt: the receiver scans both SSCCs; the WMS posts goods receipt GR-55102 for 40 cartons, although pallet two carries 19 and one carton is crushed.
3. 07:12 Putaway confirmed: putaway task PA-1180 moves pallet two to reserve bin R-14-03-B with 20 cartons shown as available.
4. 13:30 Short pick: wave W-1142 allocates 20 cartons from R-14-03-B; the picker finds 19 good and one damaged, and raises a short-pick exception.
5. 14:05 Late adjustment: inventory control posts a two-carton adjustment, but the trailer, seal record and driver signature are gone, so the supplier claim has no dock evidence.

The fix was a receiving rule, not more training: pallets flagged as rewrapped at the gate now force a carton count and a damage photo before GR posting. The discrepancy is then logged against the ASN while the driver is still on site, and the supplier claim starts with a signed delivery note instead of a pick-time surprise.

Inspection holds, putaway tasks and the confirmed bin location

Received stock should pass through inspection only when a rule says so, and it should never become available until a putaway scan confirms its location. Inspection decides whether stock can be used; putaway decides where it can be found.

Inspection rules usually key on item, supplier or lot. A pharmaceutical or food item may need every lot sampled, while a packaging material from a long-standing supplier may skip inspection entirely. When inspection applies, the WMS places the receipt on a quality hold with a reason code. Released stock becomes available; rejected stock moves to a return-to-vendor location with its own status, so it cannot be allocated by accident.

• Putaway task generated: the WMS suggests a target bin from slotting rules such as item velocity, cube, weight limits and lot mixing restrictions.
• Location scan confirmed: the operator scans the bin label; a mismatch blocks confirmation until a supervisor accepts the alternative bin.
• Status change posted: the LPN moves from "received" on the dock to "available" in reserve or a forward pick slot.
• Dock dwell monitored: any LPN still on a dock location after the site's target, often 60 to 120 minutes, appears on a supervisor exception list.

The common putaway exception is a full or blocked target bin. Allowing operators to "put anywhere and fix later" creates ghost stock. Instead, let the operator request a new suggestion, or scan an alternative bin that the WMS validates against the same capacity and mixing rules. Every override should carry the operator ID and a reason, because those overrides are where location accuracy drifts.

-- Status dwell check: LPNs stuck in a transitional status beyond the site target
SELECT l.lpn_id,
       l.item_id,
       l.status,
       l.location_id,
       l.status_changed_at
FROM   lpn l
WHERE  (l.status = 'RECEIVED'   AND l.status_changed_at < CURRENT_TIMESTAMP - INTERVAL '90' MINUTE)
   OR  (l.status = 'QC_HOLD'    AND l.status_changed_at < CURRENT_TIMESTAMP - INTERVAL '48' HOUR)
   OR  (l.status = 'PICKED'     AND l.status_changed_at < CURRENT_TIMESTAMP - INTERVAL '4' HOUR)
   OR  (l.status = 'COUNT_HOLD' AND l.status_changed_at < CURRENT_TIMESTAMP - INTERVAL '24' HOUR)
ORDER  BY l.status, l.status_changed_at;
-- Thresholds are illustrative; set them from your own shift pattern.

Keeping stock accurate between putaway and picking

Between putaway and picking, two flows keep the WMS honest: replenishment moves stock to where pickers need it, and cycle counting checks that the recorded quantity is still true. Both should run as WMS tasks with scans, never as paper moves keyed in later.

Replenishment refills a forward pick slot from reserve, either when the slot drops below a minimum or when released orders will need more than the slot holds. The inventory status stays "available" throughout, but the location changes, so the move must be confirmed by scanning both the source and destination. Our comparison of min-max and wave-demand replenishment explains how to choose the trigger.

• Count hold placed: cycle counting freezes the location for picks while the counter records the quantity found.
• Variance compared: variances inside tolerance post automatically; larger ones go to inventory control for a recount.
• Value approved: finance approves adjustments above the site value threshold before they post.
• Depositor informed: a 3PL reports each approved adjustment to its client, often as an X12 947 warehouse inventory adjustment advice.

India's CGST Rule 56(2) requires a stock account showing opening balance, receipts, supplies, goods lost, stolen, destroyed or written off, and closing balance. A WMS cycle-count adjustment therefore needs a reason code mapping to those categories, and Rule 56(8) requires a log of every electronic entry edited or deleted.

Two further Indian rules shape how count adjustments are booked. Section 17(5)(h) of the CGST Act blocks input tax credit on goods lost, stolen, destroyed or written off, so a "lost" reason code should prompt a credit reversal. For third-party warehouses, Rule 58(5) requires goods to be stored so they can be identified item-wise and owner-wise, which rules out mixing two clients' identical SKUs in one bin without owner tracking.

In the US, ASC 330-10-35-1B requires inventory measured on FIFO or average cost to be carried at the lower of cost and net realizable value, with any loss from damage recognised in the period it occurs. A damaged-in-storage reason code is the WMS event that tells finance a write-down may be due. The same count discipline is described in our guide to cycle counting while the warehouse keeps shipping.

Order release, wave building and choosing a picking method

Outbound work starts when the WMS allocates stock to an order and releases the pick work in a sequence the floor can finish before the carrier cutoff. Allocation reserves inventory; release creates tasks. Treating them as one step is the most common cause of late trucks.

Orders arrive from an order management system, an ERP or, for a 3PL, a client's X12 940 warehouse shipping order. Allocation picks specific locations and lots, applying rules such as FEFO for dated goods or full-pallet picks from reserve. The stock status becomes "allocated", which is still physical inventory but no longer promisable to anyone else.

Waves group orders by carrier, cutoff or zone and release them together. Waveless release drips work to pickers continuously as capacity frees up. Either way, release should check packing and loading capacity, not just pick labour, a point developed in our article on releasing waves against the carrier cutoff. The pick-confirm scan then moves stock to "picked" in a tote or cart.

The usual exception is a short pick: the bin holds less than the WMS says. A good flow sends the picker to an alternative location if one exists, puts the empty bin on count hold immediately and lets the order continue short only with the outbound planner's approval. Never let a picker simply skip the line, because the missing quantity then disappears without a count.

Packing, staging, loading and the ship-confirm transaction

The last outbound steps turn picked items into identified shipping units and remove them from inventory only when they leave the building. Ship confirm should be the final transaction, triggered by closing the trailer, not by printing a label.

At packing, the WMS checks picked items against the order, suggests a carton size and prints a label carrying a new SSCC for each carton or pallet. Some sites add a check-weigh: if the carton weight falls outside the expected range for its contents, it goes to an audit station. The status becomes "packed", and the SSCC now links every item to the carton that holds it.

• Staging lane assigned: packed cartons move to a lane matched to the carrier and door, scanned so the WMS knows they are staged.
• Load scan enforced: each SSCC is scanned onto the trailer; a carton for a different route or door is rejected at the scan.
• Documents generated: the bill of lading and packing list print from the loaded SSCCs, not from the original order lines.
• Trailer closed: the shipping lead records the seal number and closes the load, which triggers ship confirm.

Ship confirm removes stock from on-hand and sends the outbound messages: an outbound 856 to the customer, a 945 warehouse shipping advice to a 3PL client, and the signal for the ERP to invoice. Sending ship confirm early, before the last carton is loaded, is a frequent fault; when a carton is then left behind, the customer is invoiced for goods still in the building.

India's CGST Rule 138(1) requires an e-way bill before goods move when the consignment value exceeds ₹50,000. A WMS ship-confirm flow for Indian sites should block trailer release until the e-way bill number is recorded against the load, while US sites send the X12 945 shipping advice after the trailer is sealed.

Loading exceptions are usually physical: a carton is missing at the load scan, or the trailer is full before the lane is clear. The shipping lead decides whether to hold the trailer, split the load or move the carton to the next departure. The WMS should record that decision against the order so customer service can see why a carton shipped late.

Returns re-entering the flow through a separate receipt

Returns use a receiving flow of their own because the goods arrive in unknown condition and often without an ASN. Returned stock should land in a return-hold status and only become available after a person grades it.

The return receipt is matched to a return authorisation number where one exists. Without one, the returns team creates a receipt against the original order or customer and flags it for review. Grading then decides the disposition: back to stock, refurbish, return to vendor or scrap. Each outcome is a separate transaction, so the stock account can show what happened to every unit.

Returns are where Rule 56(2)'s categories matter most in India, because "destroyed" and "written off" units must be visible in the stock account. In the US, units graded as damaged but kept for resale at a lower price are the case where ASC 330-10-35-1B can require a write-down to net realizable value. Either way, the grade must be recorded in the WMS, not on a spreadsheet beside it.

Record owners, sign-offs and the checks the WMS should enforce

Each record in the flow needs one owner who can correct it and one approver for exceptions. Put the hard checks inside the WMS, and use software suggestions only where a person still makes the final call.

The ownership table below works as a starting point for a RACI. The WMS holds the location and status of stock; the ERP, as the financial ledger, holds cost and ownership. Where the two disagree, the owner named here investigates, and the approver signs off the correction.

Software that suggests, predicts or reads images can speed several steps, but it should not post status changes on its own. The second table names the task, the fixed WMS rule and the place where a suggestion helps a person decide.

A worked pallet trace in dollars and rupees, and a mapping checklist

A short receipt that is caught at the dock costs a claim form; the same shortage found at picking costs a write-off and a late order. The worked example below uses illustrative figures for the 40-carton receipt from the incident trace, handled correctly.

The US column assumes a unit cost of $62.50 per carton. The India column assumes ₹4,800 per carton plus GST at an illustrative 18%, with the damaged carton written off. Your rates, costs and tax treatment will differ; the point is how each WMS status maps to an accounting outcome.

Before configuring or replacing a WMS, walk one real order and one real receipt through your building and fill in the step table for your site. Then score the flow against the checklist below. Any "no" is a place where stock will wait without an owner.

For more warehouse and transport process guides, browse the logistics and supply chain hub. If you are preparing a WMS selection and want vendors to demonstrate your own step table, including the exceptions, you can send us your requirements and we will help shape the demo script.