Dock-to-Stock Time: Measuring and Cutting Receipt Lead Time
For supply chain analysts, dc managers and logistics finance controllers · Understand the problem

Dock-to-Stock Time: Measuring and Cutting Receipt Lead Time: Illustrative warehouse rack aisle with segregated tote bin, handheld terminal, and clipboard check sheet; not a client facility.
Quick answer: dock to stock time
Dock-to-stock time is the elapsed time from the start of unloading an inbound trailer to the moment each pallet is putaway-confirmed and available to allocate in the WMS. Measure it per pallet or licence plate, report the median and 90th percentile rather than the mean, and count quality holds inside the clock unless they are reported separately.
TL;DR — what you’ll learn
- Start the clock at unload start or receipt open and stop it at available-to-allocate status; a gate check-in start mixes yard wait into a warehouse metric.
- Report median and 90th percentile hours per pallet; in the worked receipt the median is 1.71 hours while one QA-held pallet takes 4.5 hours.
- An ASN with SSCC labels lets receivers scan a pallet in about 2 minutes instead of counting cartons for about 12, in our illustrative timing.
- By Little's law, cutting 6 hours off dock-to-stock at 55 pallets per hour frees about 330 staging positions in the US example.
Topics: dock to stock time · dock to stock cycle time · receiving timestamps wms · asn receiving · putaway lead time
All quantities, amounts, product codes and events are illustrative teaching examples.
At 10:05 the order wave for a fast-moving SKU short-allocates and fourteen store orders go to backorder, while forty cartons of that SKU sit on a pallet in staging lane 3, received three hours earlier. The receiving dashboard shows a healthy average dock-to-stock time for the day. Both facts are true, and that is the problem with how most warehouses measure receipt lead time: one average across all pallets hides the few that matter.
A dock-to-stock number becomes useful once it is defined by two fixed WMS events, calculated per pallet, and reported as a median and a 90th percentile with quality holds shown separately. Measured that way, it points straight at the step that is slow, whether that is unloading, counting, inspection or the wait for a putaway driver, and it can be priced in staging space and inventory carrying cost.
- What this guide covers: start and stop events, the timestamps to capture, the calculation with a query, a worked six-pallet receipt, the edge cases that distort the number and the effect of an accurate advance ship notice.
- What it adds: a cost model in dollars and rupees based on Little's law, the receipt dates that US food traceability and Indian GST rules rely on, and a rollout checklist.
Pick the start and stop events before measuring anything
Dock-to-stock time should run from unload start, or the moment the receipt is opened at the door, to the moment the pallet is available to allocate. Any other pair of events measures something else. Gate check-in adds yard wait, which belongs to dock scheduling, and putaway confirmation alone can miss stock that is shelved but still on hold.
Benchmarks only compare like with like. WERC's annual DC Measures survey lists "Dock to Stock Cycle Time, in Hours" next to related receiving measures such as lines received and put away per hour, and practitioners fill it from their own systems with whatever events those systems record. Before comparing with any peer figure, write down your start and stop events and confirm the peer used the same ones.
- Start options: gate check-in, door assignment, unload start, first receipt scan; prefer unload start or receipt open.
- Stop options: putaway confirmation, quality release, available-to-allocate status; prefer the last of these to happen.
- Not dock-to-stock: time from purchase order to arrival, yard dwell before the door, and time from available to first pick.
Dock-to-stock time in a warehouse management system runs per pallet from unload start or receipt open to available-to-allocate status, so a pallet received at 06:52 and released for allocation at 08:40 on a receipt opened at 06:40 scores 2.0 hours, regardless of how long the trailer waited in the yard.
Yard time still matters, just not in this metric. If trucks queue for hours before getting a door, that is an appointment and door-capacity problem, covered in our guide to dock appointments the warehouse can service. Keeping the two clocks separate stops a receiving team being blamed for a scheduling decision, and stops a scheduling fix being credited to the receiving crew.
Six timestamps a WMS should stamp on every inbound pallet
The calculation is only as good as the events behind it, and most warehouses already record them without storing them together. Six timestamps per pallet or licence plate are enough to compute dock-to-stock and to split it into its stages. Each one should come from a system transaction, not a manual entry typed at shift end.
Scroll horizontally to see all columns.
| Timestamp | Creating transaction | System | Data owner | Signs off the definition |
|---|---|---|---|---|
| Unload start or receipt open | Receipt opened on handheld at the door | WMS | Receiving lead | DC manager |
| Pallet received | SSCC scan against the ASN, or count confirmed | WMS | Receiving clerk | DC manager |
| Quality hold placed | Status change by item or supplier inspection rule | WMS or quality system | Quality lead | Quality manager |
| Quality release | Inspection result posted, status changed | Quality system | Quality technician | Quality manager |
| Putaway confirmed | Location scan at the destination slot | WMS | Putaway driver | Inventory control lead |
| Available to allocate | Status set to available after all holds clear | WMS and ERP inventory | Inventory control lead | Supply chain analyst who owns the KPI |
Two of these events often live outside the WMS. Quality holds may sit in a separate quality system, and available-to-allocate status may only exist in the ERP after an interface runs. Where an interface batches every 15 minutes, add a field for the batch time, or the metric will show a saw-tooth pattern that reflects integration timing rather than warehouse work.
Per pallet, per receipt or per line: the unit and the statistic
Calculate dock-to-stock per pallet or licence plate, then summarise with the median and the 90th percentile. A per-receipt figure, measured to the last pallet, is useful for carriers and suppliers but hides early pallets that were fast. A plain mean is pulled by a few held pallets and tells a manager nothing about the typical one.
Working hours versus calendar hours is the second choice. A DC that receives on two shifts will show a 10-hour dock-to-stock for any pallet received at 21:50 and put away at 06:10 the next morning, though only 20 minutes of work happened. Report calendar hours as the headline, because that is what customers feel, and working hours as a diagnostic beside it.
-- Dock-to-stock per pallet, then median and P90 per day (PostgreSQL)
-- d2s_hours = (available_ts - receipt_open_ts) / 3600
-- held = pallet had any quality hold between the two events
WITH pallet AS (
SELECT r.receipt_id,
l.lpn,
r.receipt_open_ts,
l.available_ts,
(l.qa_hold_ts IS NOT NULL) AS held,
EXTRACT(EPOCH FROM (l.available_ts - r.receipt_open_ts)) / 3600.0 AS d2s_hours
FROM inbound_receipt r
JOIN inbound_lpn l ON l.receipt_id = r.receipt_id
WHERE l.available_ts IS NOT NULL
AND r.receipt_type = 'PO' -- returns and transfers reported separately
)
SELECT DATE(receipt_open_ts) AS receipt_day,
COUNT(*) AS pallets,
PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY d2s_hours) AS median_h,
PERCENTILE_CONT(0.9) WITHIN GROUP (ORDER BY d2s_hours) AS p90_h,
AVG(d2s_hours) FILTER (WHERE held) AS held_mean_h,
COUNT(*) FILTER (WHERE held) AS held_pallets
FROM pallet
GROUP BY 1
ORDER BY 1;
Worked receipt: six pallets, one quality hold and a 4.5-hour tail
One small receipt shows why the statistic matters. Receipt R-30418 was opened at door 5 at 06:40 against an advance ship notice. Five pallets went straight to putaway; one carried an item on the supplier inspection list and waited for a quality sample. The figures are illustrative but typical of a single-shift receiving crew.
Scroll horizontally to see all columns.
| Pallet | Received | Putaway confirmed | Available | Dock-to-stock hours |
|---|---|---|---|---|
| LPN 1 | 06:52 | 07:20 | 07:20 | 0.67 |
| LPN 2 | 06:55 | 07:31 | 07:31 | 0.85 |
| LPN 3 | 06:58 | 08:05 | 08:05 | 1.42 |
| LPN 4 | 07:03 | 08:40 | 08:40 | 2.00 |
| LPN 5, quality hold | 07:06 | 07:50 to a hold location | 11:10 | 4.50 |
| LPN 6 | 07:10 | 09:55 | 09:55 | 3.25 |
| Summary | Median 1.71 h | Mean 2.12 h | P90 4.50 h | Receipt complete 4.50 h |
The median of 1.71 hours says the dock crew and putaway drivers are working well. The 90th percentile of 4.50 hours, driven by one held pallet, says quality sampling is the bottleneck. The mean of 2.12 hours says neither, which is why it should not be the headline. LPN 6, at 3.25 hours without any hold, is the second signal: it waited in staging because no putaway task was assigned.
The same receipt can be traced minute by minute to show the cost of that held pallet. The steps below are illustrative, with the WMS transaction named at each step, and show how stock that has physically arrived still causes a backorder when its release depends on a person who is busy elsewhere.
- 06:40, door 5: receipt R-30418 opened against ASN 0812345000771206, seal 2290417 intact; WMS transaction RCV-OPEN.
- 07:06, receiving: LPN 5 with SKU 44120 scanned; the supplier inspection rule sets status QA-HOLD and creates a sample task.
- 09:30, quality bench: the only technician is still sampling a 22-pallet receipt from another supplier; the task for LPN 5 is fourth in her queue.
- 10:05, order release: the wave short-allocates 36 units of SKU 44120 and fourteen store orders backorder, with forty cartons on LPN 5 in the hold location.
- 11:10, release: sample passes, status changes to AVAILABLE, replenishment fills the pick face; the backorders ship a day late.
The controlled version ranks sample tasks by open demand, so LPN 5's sample jumps the queue because SKU 44120 has orders waiting. The pallet is released by about 07:40, the wave allocates in full, and the receipt's 90th percentile drops below two hours with the same staff.
Edge cases that quietly distort the dock-to-stock number
Most dock-to-stock reports are wrong in the same few ways, because some pallets follow paths the formula was not designed for. Decide each case once, write it into the KPI definition, and apply it in the query rather than by editing results. A definition that changes month to month cannot show a trend.
- Cross-dock pallets: never go to stock; exclude them and measure dock-to-dock time instead.
- Partial receipts: a trailer split across two receipts should keep one receipt-open time for all its pallets, or the second half looks faster than it was.
- Receipts closed at shift end: clerks who open one receipt per trailer but scan pallets in batches create false received times; use pallet scan times, not receipt close times.
- Overnight staging: pallets received late and put away next morning inflate calendar hours; report them and keep them in, since customers feel the delay.
- Returns and transfers: follow different inspection paths and should be reported apart from supplier receipts.
- Missing available status: pallets with no available timestamp are not fast, they are unfinished; report them as open, never drop them.
How an accurate ASN shortens the receiving step
The receiving step shrinks most when the supplier sends a correct X12 856 ship notice and labels each pallet with a serial shipping container code. The receiver scans one label, the WMS accepts the pre-loaded contents, and the pallet is ready for putaway. Without that, someone counts cartons against the purchase order line by line.
In our illustrative timing, scanning an SSCC on a pallet whose ASN is correct takes about 2 minutes, while a blind count of a mixed pallet takes about 12. On a 26-pallet trailer that is 52 minutes against 312 minutes of receiving work, and every minute of it sits inside dock-to-stock because putaway cannot start on a pallet that is not received.
ASN-based receiving pairs an X12 856 Ship Notice/Manifest with a GS1 SSCC encoded under application identifier 00 on each pallet label, so a receiver scans one 18-digit code instead of counting cartons; in the illustrative 26-pallet trailer, receiving work falls from 312 to 52 minutes.
The ASN only helps if it is right. A notice with wrong quantities forces a recount and teaches receivers to ignore it. Measure ASN accuracy per supplier as the share of pallets accepted on scan without adjustment, and send the result back through an 861 receiving advice or a supplier scorecard. Our guide to recording short or damaged receipts covers how to hold the exception evidence when a scanned pallet does not match.
- Scan-accept rate: pallets accepted on SSCC scan divided by pallets received from that supplier.
- ASN timeliness: share of notices received before the truck reaches the door.
- Label readability: share of pallets where the SSCC scanned at the first attempt.
What slow dock-to-stock costs in staging space and carrying cost
Slow dock-to-stock costs money in three places: staging floor, inventory carrying cost and lost or late sales. The first two can be priced with simple arithmetic. Little's law says the average number of pallets waiting equals the arrival rate times the average wait, so hours cut from dock-to-stock translate directly into staging positions freed.
The table applies that to an illustrative US DC and an Indian DC, with assumed pallet values and carrying rates. Neither includes the cost of backorders, which is usually larger but depends on margin and customer terms. Use the staging figure to decide whether a dock expansion is needed at all before approving one.
Scroll horizontally to see all columns.
| Input or result | US DC (USD) | Indian DC (INR) |
|---|---|---|
| Supplier pallets received per day | 880 (40 receipts × 22 pallets) | 216 (12 receipts × 18 pallets) |
| Receiving hours per day | 16 | 16 |
| Arrival rate per hour | 55 pallets | 13.5 pallets |
| Dock-to-stock now and target | 9 hours to 3 hours | 10 hours to 4 hours |
| Staging positions freed (rate × 6 hours) | 330 | 81 |
| Average value per pallet | $3,200 | ₹2,40,000 |
| Annual carrying rate assumed | 20% | 14% |
| Carrying cost saved per day | 880 × $3,200 × 6 h × 20% ÷ 8,760 h = $385.75 | 216 × ₹2,40,000 × 6 h × 14% ÷ 8,760 h = ₹4,970.96 |
| Carrying cost saved over 250 operating days | about $96,400 | about ₹12,42,700 |
The carrying saving is modest next to the staging figure. Freeing 330 positions in the US example is the difference between leasing overflow space and not, and in many buildings it also clears the aisles that putaway drivers need. Present both numbers together; finance teams often reject the carrying saving as too small and miss the space effect.
Receipt dates that food traceability and GST rules rely on
Dock-to-stock is an internal metric, but the timestamps behind it feed records that regulators and tax rules use. The receipt date must reflect when goods arrived, not when they were put away or when a clerk closed the receipt. A receipt that sits open overnight can put the wrong date on a legal record.
In the US, the FDA Food Traceability Rule requires anyone receiving a food on the Food Traceability List to keep receiving key data elements under 21 CFR 1.1345(a), including the date the food was received, the receiving location and the reference document type and number. FDA says it will not enforce the rule before 20 July 2028, following a Congressional directive, but receivers building systems now should take the receipt date from the receipt-open or pallet-scan event.
Food receiving records under 21 CFR 1.1345(a) must hold the date the food was received and the reference document number, so a WMS should take the receipt date from the pallet scan event; FDA will not enforce the Food Traceability Rule before 20 July 2028 under a Congressional directive.
India has no comparable dock-to-stock rule, but GST makes the receipt event matter for cash. Section 16(2)(b) of the CGST Act allows input tax credit only once the goods have been received, and its proviso says that where one invoice arrives in lots, credit waits for the last lot. A buyer whose ERP releases credit only on a posted goods receipt note will push the claim into a later return if the final truck's receipt is posted late.
Which receiving checks run as fixed rules and which need judgement
Most of the work that shortens dock-to-stock is rule-based: status changes, task release and prioritisation. Software can help a supervisor see where pallets are waiting and why, but release from quality hold and overriding a putaway rule stay with named people. The table names the task in each case.
Scroll horizontally to see all columns.
| Task | Fixed WMS rule | Where software assists a person | Who decides |
|---|---|---|---|
| Accepting a pallet on SSCC scan | Accept when the SSCC is on the open ASN and the PO line is open | None needed | WMS rule |
| Placing a quality hold | Hold when item or supplier is on the inspection list | None needed | Quality manager owns the list |
| Ordering the sample queue | Rank by open demand on the held SKU, then by arrival time | Showing the backorder value waiting on each held pallet | Quality technician follows the queue |
| Releasing putaway tasks | Release on receipt, never batch by trailer | Forecasting staging congestion an hour ahead | Shift supervisor reassigns drivers |
| Choosing the storage slot | Directed putaway rules for weight, size and zone | Suggesting a slot when rules find none | Inventory control lead approves |
| Spotting an unusual receipt | Flag pallets open beyond the 90th percentile | Reading a photo of a damaged label to propose the SSCC | Receiving lead confirms |
Slot choice affects the last leg of the clock. Our guide to directed putaway rules explains how the WMS picks a location, and how a missing weight on the item master can stall a pallet in staging. For the full inbound sequence the timestamps sit in, see the warehouse management system process flow.
Rolling out a dock-to-stock measure across one building
Roll out the measure on one building and one receipt type first, and agree the definition before publishing any number. A first month of data usually finds missing timestamps and batch scanning, which need fixing before the figure is shown to suppliers or carriers. The checklist below sets the order.
Scroll horizontally to see all columns.
| Step | Pass condition | Owner | Week |
|---|---|---|---|
| Write the definition | Start, stop, unit, exclusions and statistic signed off | DC manager and KPI owner | 1 |
| Confirm timestamps exist | All six events stored per pallet for 95% of receipts | WMS analyst | 2 |
| Stop batch scanning | Pallet scan times spread across the unload, not bunched at close | Receiving lead | 3 |
| Split held and unheld pallets | Report shows both, with the hold reason | Quality manager | 4 |
| Add ASN accuracy by supplier | Scan-accept rate per supplier published monthly | Supplier compliance lead | 6 |
| Price the gap | Staging positions and carrying cost agreed with finance | Logistics finance controller | 8 |
| Set targets | Median and P90 targets per receipt type, reviewed quarterly | DC manager | 12 |
More warehouse measurement guides are on the Logistics and Supply Chain hub. If you want receiving timestamps, ASN scoring and a dock-to-stock report built into your WMS or data platform, send us a request for proposal and we will start from the definition your team signs.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Common operational questions
Practical answers for operations, engineering, and finance teams working on dock to stock time in logistics & supply chain.
What is a good dock-to-stock time for a distribution centre?
Should quality inspection time count in dock-to-stock?
How does an advance ship notice shorten dock-to-stock time?
Is dock-to-stock the same as putaway time?
References
Sources checked 13 November 2026. US and India statutory authorities and vendor documentation support platform facts; the worked examples and diagrams are original.
- WERC - DC Measures Survey 2025 (metric list including Dock to Stock Cycle Time, in Hours)Used for the metric names only; WERC benchmark values are not quoted. Accessed 13 November 2026.
- X12 - Transaction set list: 856 Ship Notice/Manifest and 861 Receiving Advice/Acceptance CertificateOfficial transaction set names. Accessed 13 November 2026.
- GS1 - Application Identifiers reference, AI (00) Serial Shipping Container CodeAI 00 format N2+N18, read from the GS1 machine-readable AI dataset. Accessed 13 November 2026.
- Cornell LII - 21 CFR 1.1345, Records of receiving (Food Traceability Rule)Receiving key data elements, including the date the food was received and the reference document. eCFR blocks automated access; text read on the LII copy. Accessed 13 November 2026.
- US FDA - FSMA Final Rule on Requirements for Additional Traceability Records for Certain FoodsFDA states it will not enforce the rule before 20 July 2028, following a Congressional directive in the 2026 continuing appropriations act. Accessed 13 November 2026.
- CBIC - Central Goods and Services Tax Act, 2017, Section 16(2)(b) and its proviso on goods received in lotsCredit only after receipt of goods, and after the last lot where one invoice arrives in instalments. Accessed 13 November 2026.
- FMCSA — 49 CFR Part 395 Hours of Service & Electronic Logging Devices (ELD)US federal motor carrier dispatch and driver duty-status compliance mandate.
- ULIP & NIC GST E-Way Bill Portal — Unified Logistics & Rule 138 ComplianceIndian statutory goods-in-transit and multi-modal logistics verification framework.