The order lifecycle: receiving → putaway → picking → packing → shipping → proof of delivery
The Order Lifecycle: Receiving → Putaway → Picking → Packing → Shipping → Proof of Delivery
The order lifecycle in fulfillment runs from the moment stock arrives at the warehouse dock to the moment a customer receives their order with proof of delivery. Each step generates evidence. Each gap in that evidence becomes a cost center.
The sequence is not complicated. What’s complicated is maintaining control at every handoff — because the errors that surface at dispatch were usually created two or three steps earlier.
Receiving: The First Quality Gate
An order correct order should be boring. That principle starts at receiving, not at pick.
When a shipment arrives at the 3PL dock, the floor has a choice: move quickly and accept what came, or verify and record before anything goes to active inventory. The difference between these two approaches is the difference between a supply chain that catches discrepancies in minutes and one that discovers them in customer complaints weeks later.
Controlled receiving means comparing what arrived against what was expected — an ASN or a packing list — before a single unit is assigned a location. Count verification, condition check, barcode scan. If a carton arrives with 14 units instead of 16, that discrepancy is logged now, the supplier is notified, and the stock that enters the system reflects reality. If it’s not caught here, the inventory count starts wrong and everything built on top of it inherits that error.
ASN (Advance Shipping Notice): A document sent by the supplier before a shipment departs, specifying expected SKUs, quantities per carton, total carton count, and carrier details. An ASN converts receiving from investigation to verification — the team checks against a known expectation rather than building the count from scratch.
The most common receiving failure isn’t theft or supplier fraud — it’s optimism. The receiving team is under time pressure. The supplier has always sent the right quantities before. The packing list looks right. So the units are counted quickly, or not counted at all, and the stock goes into active inventory. Three weeks later, a stockout appears for a SKU that shows plenty of inventory on paper. The investigation goes backward and finds the receiving gap, but by then several orders have been affected.
Evidence at receiving: inbound confirmation with received quantities, logged discrepancies, condition notes for damaged units, quarantine records for non-conforming goods. These are the documents that resolve supplier disputes, carrier damage claims, and inventory audits. Without them, every dispute becomes a word-against-word situation.
Putaway: Turning a Received Unit into Findable Stock
Once stock passes receiving, it needs a home — and that home needs to be recorded. Putaway is not “put it somewhere.” It is the assignment of a specific unit to a specific location, confirmed by scan, so that the system knows exactly where every unit is.
The location logic behind putaway varies by operation: velocity-based (fast movers near the primary pick face, slow movers in reserve), product-based (fragile items in padded zones, heavy items on lower shelves), or purely sequential (next available space). The specific logic matters less than the consistency. What breaks inventory accuracy is not the logic chosen — it’s the departure from it. A unit put in the wrong location because the assigned spot was occupied and nobody updated the record creates a phantom in the system: inventory shows a location that contains something else.
Putaway confirmation: The scan step at the end of putaway that records the actual location where a unit was placed. Without scan confirmation, the putaway plan and the physical location may diverge. The WMS records where the unit was supposed to go, not where it actually went.
A common scenario: a product line expands quickly and several new SKUs arrive before their locations are set up in the WMS. The floor team puts them in available space. The system doesn’t know where they are. When a pick task is generated, the picker goes to the system location (which doesn’t exist yet or shows something else) and returns empty-handed. This is called a zero pick — and it’s not a picking problem. It’s a putaway problem that surfaced at pick.
Picking: Accuracy Before Speed
The question isn’t whether the floor can pick fast. It’s whether it can pick correctly — consistently, across different operators, under volume pressure.
Pick accuracy is a system property, not a person property. The most reliable picker on the team will still make errors if the pick task sends them to the wrong location, if the barcode scan doesn’t confirm the right unit, or if two similar SKUs share a pick face without a clear visual or scan distinction. Conversely, a new hire following a scan-confirmed pick process will outperform an experienced picker working from memory.
The pick task tells the picker which location to visit and what to retrieve. Scan confirmation at the location and at the unit closes the loop: the right place was visited, the right item was picked. A mismatch — when the scan doesn’t match the expected unit — is a signal to investigate before the pick moves forward, not after the order is packed.
What you see when picking isn’t working is a pattern of “customer received wrong item” support tickets that can’t be explained by individual error. The root is usually a combination of inadequate scan confirmation, similar-looking SKUs without distinction, or pick paths that cross in ways that create confusion under pressure. These are floor design and process problems. They don’t resolve by telling people to be more careful.
Pick verification: The scan step that confirms the picked unit matches the order line. A verified pick means the WMS has a record that the correct item was retrieved from the correct location. An unverified pick means the system records a completion but not a confirmation — and any error between the task generation and the pack becomes invisible until the customer reports it.
Packing: Protection and Consistency
Packing converts a verified pick into a shippable unit. It has two jobs that are in tension with each other: protect the product, and control the dimensional weight of the package.
Under-protection leads to damage claims, returns, and negative reviews. Overpacking — a product in a box three times its size, filled with void fill — leads to dimensional weight charges that erode margin on every shipment. The balance is set by packing rules: defined box sizes for defined product profiles, specified void fill standards, documented insert requirements, and consistent weight ranges for each package type.
Dimensional weight (DIM weight): A carrier pricing method that charges based on the volume of a package rather than its actual weight, when the volume-based calculation produces a higher rate. A box that is too large relative to its contents may be charged as if it were heavier than it is.
When packing rules aren’t written, the packing decision is made on the floor, individually, by each packer. Some will over-protect and inflate costs. Some will under-protect and generate damage. The variation between packers means the output is inconsistent, and the cost and damage rates are unpredictable. Packing rules are not bureaucracy — they are the mechanism that makes packing output a controllable variable.
The check at pack-out confirms that the right items are in the right box before the box is sealed. A scan of each pick against the order confirms no item was missed and no wrong item was included. A missing step here means the first quality check happens when the customer opens the box.
Shipping: Handoff with Proof
The package leaves the floor with a label, a tracking number, and a carrier scan. The label is generated from the order record — carrier service, dimensions, weight, recipient address, and any required documentation. The carrier scan at pickup is the moment when fulfillment ends and carrier responsibility begins.
What can go wrong at this step is narrower than at receiving or picking, but the failures are highly visible to the customer. A label generated from wrong address data goes to the wrong address. A carrier service level mismatch (standard when the customer paid for express) generates a complaint before delivery. A package that closes without a carrier scan is “shipped” in the system but has no physical confirmation that it left the building — which means a missing parcel investigation starts with no evidence trail.
Carrier handoff: The physical transfer of a packaged order to a carrier representative, confirmed by carrier scan. The handoff creates a chain of custody record — the package existed at the 3PL, in that condition, at that time, and was accepted by the carrier. Without the scan, the handoff is a claim.
Cut-off compliance is the operational discipline that makes shipping predictable. The cut-off time is the deadline after which orders wait for the next carrier pickup. If the floor processes orders past cut-off and the carrier has already left, same-day orders ship next day — which breaks any SLA committed to the customer. Monitoring cut-off compliance on a daily basis is what reveals whether the floor is absorbing volume correctly or creating a backlog that will express itself as late shipments.
Proof of Delivery: Closing the Loop
The lifecycle doesn’t end at dispatch. It ends when the customer receives the order and the record shows it. Proof of delivery is the carrier’s confirmation that the package arrived — a scan at the customer’s address, a photo, a signature depending on the service level.
For the brand, proof of delivery is the evidence that resolves “I didn’t receive my order” disputes. A claim submitted with a tracking number showing delivery confirmation is resolved differently than one submitted against a shipment that shows “out for delivery” and nothing after.
For the 3PL, proof of delivery closes the order record. Fulfillment’s job is done when the carrier confirms delivery. Any dispute after that point — address issues, theft after delivery, damage not consistent with condition at dispatch — moves into a different workflow: insurance claims, carrier claims, or customer service decisions that belong to the brand.
The lifecycle as a chain of controls produces a complete evidence trail: inbound confirmation → location record → pick verification → pack confirmation → dispatch with carrier scan → delivery proof. Each step that lacks a record creates a gap that will surface as a cost during a dispute, an audit, or an investigation.
Frequently Asked Questions
Q: What are the steps in the order fulfillment lifecycle? A: The standard lifecycle runs: receiving (stock verified against expected shipment), putaway (units assigned to tracked locations by scan), picking (order items retrieved and scan-confirmed), packing (items packaged per rules and verified), shipping (label generated, carrier handoff with scan), and proof of delivery (carrier confirms arrival). Each step produces evidence that resolves the disputes the next step can generate.
Q: Where do most order errors actually originate? A: Most errors originate at receiving or putaway, but surface at pick or delivery. A receiving discrepancy not caught at inbound creates a phantom inventory count that produces a stockout weeks later. A putaway unit in the wrong location creates a zero-pick situation when the order arrives. The step that generates the error and the step where it surfaces are often different — which makes root cause analysis harder without complete evidence at every step.
Q: What is proof of delivery in fulfillment? A: Proof of delivery is the carrier’s confirmation that a shipment reached the recipient — typically a delivery scan at the destination address, sometimes a photo or signature depending on service level. It is what resolves “I didn’t receive my order” disputes. Without it, a missing parcel investigation relies on carrier records that the 3PL cannot control or produce.
Q: What happens when a pick results in a zero (item not found at location)? A: A controlled operation generates a zero-pick exception — the pick task is flagged, the investigation starts immediately (is the unit mislocated? is the inventory count wrong? was the putaway incomplete?), and the order is held until resolved. An uncontrolled operation substitutes a similar item or ships the order short. The difference is whether the exception is visible in the system or resolved informally on the floor.
Q: What is cut-off compliance in fulfillment? A: Cut-off compliance is the daily measure of whether orders that should have shipped same-day actually shipped before carrier pickup. A 3PL that misses cut-off regularly is telling you that its floor is not absorbing volume at the promised rate — which will surface as late deliveries during peaks, even if everything appears fine on normal days.
If you want to walk through your current order flow and identify which steps have evidence gaps — and what those gaps cost in returns, disputes, or investigation time — share a description of your channel setup and order volumes.