PPPick Path Notes
Issue 21  dock to promise · eight sequences2026-11-20
RECEIVE  /  Note 01

The receiving appointment is a capacity instrument, not a calendar entry

A dock door is a machine with an hourly rate. The booking window, the ASN fields, the pallet label and the SKU master data are the four things that decide whether a delivery becomes sellable stock today or sits in staging until someone answers an email.

LaneReceive
Sections10
Checks12
Filed2026-11-20
A dock door is a machine with an hourly rate. The booking window, the ASN fields, the pa
A dock door is a machine with an hourly rate. The booking window, the ASN fields, the pallet label and the SKU master data are the four things that decide whether a delivery becomes sellable stock today or sits in staging until someone answers an email.

Why the appointment window is the real capacity limit

A warehouse with six dock doors does not have six doors worth of receiving capacity. It has six doors multiplied by the time a trailer occupies each one, minus the changeover between them. If a forty foot trailer takes ninety minutes to unload, inspect and sign, one door turns roughly five trailers in an eight hour shift, and that is before any pallet has been put away. The appointment window is the only tool that keeps arrivals inside that number.

When a carrier shows up outside its window, the cost does not disappear. It moves. The crew either stops unloading another trailer, which pushes that one late, or it works the drop in parallel and leaves two half unloaded trailers on the floor. Both outcomes end with the same symptom three days later: a purchase order that looks received in the system and a pick face that is still empty.

This is why a receiving calendar that is maintained by the supplier rather than the warehouse fails. A supplier books the slot that suits its production line. The warehouse needs the slot that suits its labour curve. Those two curves only agree when capacity is published as a number of slots per hour and the booking system refuses the slot that would exceed it.

The practical test is simple. Ask the receiving lead how many trailers the dock can turn between ten and twelve on a Monday. If the answer is a number, the window is being used as capacity. If the answer is a description of how busy Mondays are, the window is decoration.

ASN is not an arrival estimate

An advance shipping notice earns its name only when it carries what the dock needs to plan: carton count, pallet count, gross weight, carrier, trailer number and the PO lines with quantities. An email that says the goods left the factory on Tuesday and should arrive Thursday is not an ASN. It is a rumour with a date on it.

The difference matters because a real ASN lets the warehouse pre-build the receipt. The lines can be loaded into the scanner before the trailer backs in, so the receiving clerk is confirming counts rather than typing part numbers off a paper packing list in a dim trailer. Confirmations are fast and accurate. Typing is neither.

The pallet count is the field most often omitted and the one that hurts most. A trailer declared as twenty six pallets that actually holds thirty one pallets has to be re worked on the spot, because the staging lane was sized for twenty six. The five extra pallets end up in the aisle, and the aisle is where the next trailer was supposed to go.

Weight is the second omission. Gross weight per pallet decides whether a pallet can be handled by a walkie or needs a forklift, and it decides which storage level the putaway task should target. A pallet declared at three hundred kilos that weighs six hundred will be sent to a shelf that cannot hold it, and the resulting damage claim is a receiving problem that was created upstream.

The four fields a pallet label cannot omit

A pallet label has to answer four questions without any human interpretation. Which shipment is this, which purchase order does it belong to, how many cartons should be on it, and where is it going inside the building. In GS1 terms that is an SSCC, a PO reference, a count, and a destination, and the label is only compliant when all four are machine readable.

SSCC matters because it is the identity of the physical handling unit rather than the identity of the product. Two pallets of the same SKU on the same trailer must have different SSCCs, otherwise the scanner will merge them into one receipt and the second pallet will appear to have never arrived.

The destination field is the one that saves labour. If the label states the storage zone or the staging lane, the putaway task can be generated at the door. If the label only states the product, someone has to look up where that product lives, and that lookup is repeated for every pallet on every trailer for the life of the contract.

Count matters for the short shipment conversation. A pallet label that says one of four lets the clerk close the receipt cleanly when pallet four is missing, and it lets the supplier's claim be argued with a document instead of a memory. Without the count the conversation becomes a comparison of two recollections.

How carton labels stack

Carton labels sit one level below the pallet label and answer a narrower question: this box is number three of six on this pallet. The sequence is what makes a short shipment locatable. Without it, a missing carton is an absence with no address, and the search starts by opening every box on the pallet.

The second field on a carton label is the SKU as it exists in the warehouse system, not as it exists in the supplier's catalogue. Those two identifiers diverge more often than anyone expects, usually because the supplier adds a colour or a size suffix that the buyer never mapped. When they diverge, the scanner rejects the label and the carton goes to the problem lane.

Quantity per carton belongs on the label rather than only in the ASN, because the carton is the unit that gets counted at the door. A carton declared as twelve pieces that holds ten will pass a carton count and fail a piece count, and the only way to catch it without opening every box is to trust that the declared quantity is printed where the opener can see it.

Label placement is a real specification rather than a courtesy. One label per carton, on the outside, on a flat face, not wrapped around a corner and not under tape. A label that spans an edge will be misread by a fixed scanner about a third of the time, and every misread is a manual key entry that reintroduces the typing error the label was meant to remove.

SKU master data has to arrive before the goods

The single most expensive delay in receiving is not a late trailer. It is a trailer that arrives before the product exists in the system. Until the SKU has a record, nothing downstream can happen: no putaway location, no dimension for the shipping calculation, no duty code, no shelf life rule, no hazmat flag.

Dimensions and weight are not paperwork. They are the inputs to the dimensional weight calculation that decides what the customer is charged for shipping, and they are the inputs to the cartonisation logic that decides which box a multi unit order will use. A SKU created without them will ship in a default box at a default rate until someone notices the margin.

The hazmat flag is the field that carries legal weight. A product containing a lithium cell and a product containing a aerosol can both need to be known before the goods are put away, because the storage location and the transport documentation depend on it. Discovering the flag at the packing table means the item has been stored incorrectly for however long it sat.

Shelf life rules decide rotation. A SKU without a shelf life attribute will be put away without a lot code and without a rotation rule, which means the oldest stock is picked last. That is not a warehouse error, it is a master data gap, and it surfaces as a write off two quarters later.

The scan order at the door

The order of scans at the door is a procedure, not a preference. Pallet first, carton second, piece count third, and the sequence exists because each scan narrows the container the next one is expected inside. Scanning cartons before the pallet means the system cannot tell whether a carton belongs to the pallet in front of the clerk or to the one behind it.

The pallet scan also starts the clock. From that moment the receipt is open, the appointment is being consumed, and any variance has a timestamp. A receipt opened at the end of the unload instead of the start cannot distinguish a short shipment from a slow unload, and that ambiguity is what makes supplier conversations unresolvable.

Piece counting is the step most often skipped under time pressure, and it is the step that generates the claims. Carton counts are cheap and piece counts are expensive, so the temptation is to count cartons and trust the declared quantity. The correct compromise is to count pieces on a sample of cartons per pallet and treat a failing sample as a trigger to count the whole pallet.

Closing the receipt is its own action with its own discipline. A receipt left open because three cartons are unresolved will block putaway for the whole pallet, and the pallet will sit in staging while the three cartons are argued about. The better practice is to close the receipt with the variance recorded and let the claim run separately from the stock.

Short and over shipments are different claims

A short shipment is a supplier or carrier failure and it is argued with the receipt, the pallet label and the carton sequence. An over shipment is almost never generosity. It is usually a master data problem, a case pack that changed without notice, or a duplicate ASN, and treating it as a bonus is how phantom inventory begins.

The short shipment claim has a deadline that most operations miss. Carriers typically require notification within a window measured in days, and suppliers require it before the invoice is approved. A claim raised three weeks later, after the stock has been reconciled and the invoice paid, is a claim that will not be honoured no matter how well documented.

Over shipments should trigger a master data audit rather than a putaway. If the case pack is twelve and thirty six arrived, either three cases were sent or the pack is now thirty six. Putting the goods away without resolving that question guarantees that the next order will be mispriced, because the buying unit and the selling unit no longer agree.

Both cases share one requirement: the variance has to be recorded against the line, not against the shipment. A shipment level note saying six cartons short does not say which SKU is missing, and the SKU is the only unit that can be sold, reordered or claimed.

Damage is booked to the leg that caused it

Freight damage has three candidate origins: the factory, the main leg, and the final delivery. Each carries a different claimant, a different evidence standard and a different recovery rate. Booking damage to the wrong leg is how a recoverable claim becomes a cost of goods sold.

Factory damage is visible before the trailer is opened, which is why the seal and the trailer condition are inspected first. A shifted load with crushed cartons at the nose is a loading problem, and photographing it before unloading is the only evidence that survives. After unloading, the same damage looks like it happened on the road.

Main leg damage is the carrier's liability and it is proved with exception notations on the delivery receipt. A clean signature followed by a damage discovery in the warehouse is a claim the carrier will decline, correctly, because the signature was the inspection. The clerk who signs without walking the load has signed away the claim.

Inbound damage discovered at putaway is the hardest to recover because it happened after the receipt closed. The practical response is to record it as an internal variance and use it as evidence in the next contract negotiation. The theoretical response, recovering from the carrier, requires evidence that was available at the door and not collected.

Where the quality sample sits

Incoming inspection belongs between receipt and putaway. It does not belong at the packing table, because by then the defective unit has been sold, picked, packed and shipped, and the cost of the failure has multiplied by the cost of the return.

The sample size should follow the accepted quality limit rather than a fixed habit. A supplier with a history of passing inspection earns a smaller sample. A new supplier, a new SKU, or a SKU returning from a stockout earns a full one. Fixed samples are administratively simple and economically wrong in both directions.

What gets inspected is a shorter list than most checklists suggest. Function, cosmetic grade, measurement against the declared dimension, labelling correctness and packaging integrity. Everything else is a supplier conversation rather than a receiving task.

The inspection result has to be a gate rather than a note. If a failing sample does not block putaway, the stock will be picked while the supplier is being contacted, and the defect will reach customers during the exact window when the replacement is not yet available.

Writing receiving into the service agreement

A receiving service level needs three numbers and one definition. Hours from arrival to sellable, receipt accuracy as a percentage of lines, and rejection rate. The definition that must accompany them is when the clock starts, and the honest answer is at the appointment, not at the unload.

Arrival to sellable is the number a merchant actually cares about, because it is the number that decides whether a restock reaches the listing before the stockout. Dock to receipt is an internal measure that can look excellent while the pallet sits in staging for two days waiting for a putaway slot.

Receipt accuracy is usually measured as the share of lines received without a correction after the fact. That definition hides the important failure, which is a line received correctly but with the wrong lot or the wrong expiry, because those corrections happen later in the cycle and are booked as inventory adjustments rather than receipt errors.

Rejection rate needs a reason code structure to be useful. Rejected for labelling, for damage, for quantity, for documentation and for hazmat are five different problems with five different owners, and a single aggregate percentage tells the merchant nothing about which one to fix.

The procedural version of this note, written as a line by line receipt, is the inbound receiving checklist built on the appointment and the SKU label, and the appointment field is what turns it from a wish into a schedule.

Checklist12 lines
  • 01Publish dock capacity as slots per hour, and let the booking system refuse the slot that exceeds it.
  • 02Require carton count, pallet count, gross weight and trailer number on every ASN.
  • 03Verify SSCC uniqueness per pallet, not per shipment.
  • 04Print carton sequence, warehouse SKU and quantity per carton on every label.
  • 05Create the SKU record with dimensions, weight, duty code, hazmat flag and shelf life before the PO ships.
  • 06Scan pallet, then carton, then piece count, and open the receipt at the first scan.
  • 07Close the receipt with the variance recorded, and run the claim separately from the stock.
  • 08Record variance against the line rather than against the shipment.
  • 09Inspect the seal and photograph the load before unloading.
  • 10Walk the load before signing the delivery receipt.
  • 11Set the incoming sample size from the supplier history rather than from a fixed percentage.
  • 12Make a failing sample block putaway rather than annotate it.