Dock-to-stock time: choose a consistent finish event

Partial putaways, quality holds, and unfinished receipts need separate treatment before you compare shifts or suppliers.

Kartik Deshpande··5 min read

Calculate dock-to-stock time from receipt of a supplier delivery to recorded putaway in inventory. Match those events at the same level, such as a receipt line or handling unit, before subtracting timestamps. A receipt completed in several batches needs either a last-completion clock or a stated weighting rule; substituting the first completed pallet makes the remaining work disappear.

Keep stock availability beside that clock. Goods can be recorded in a bin while a quality hold still prevents their use (the hold is a separate status, not a missing timestamp). Your receiving report should show what has finished putaway, what remains open, and which stored quantities still need release.

Choose the start and finish from the same receipt

APQC defines the supplier-delivery dock-to-stock clock from receipt to putaway after inventory recording. It includes waiting between activities. Keep that definition distinct from truck turnaround, unloading duration, or receipt-to-quality-release time; changing the final event changes the measure.

Write the event definition before comparing sites. Decide whether your receipt timestamp means arrival at the gate, acceptance at the dock, or the posted receipt. If your source only contains posting time, label that narrower clock. A receiving clerk who posts yesterday’s delivery this morning should not make the physical process appear shorter.

Capture the receipt identifier and line, item, base quantity, handling-unit or lot reference when available, and the source timestamps. Keep the original timezone alongside a normalized timestamp. Use elapsed hours for the full clock; subtracting nights or weekends creates a working-hours variant that needs its own label and calendar.

Your warehouse receiving checklist handles accepted, damaged, and short-delivered quantities at the dock. Start this measurement with the quantities that the declared receipt event covers. Units that the supplier never delivered belong in an open-order exception, not in a completed receiving-time denominator.

Keep partial putaways visible in the calculation

Assume a hypothetical receipt contains 100 identical units accepted at 08:00. Eighty are put away and recorded at 10:00; the remaining twenty finish at 20:00. No units are rejected, returned, or lost, and both timestamps come from the same day. These assumptions make the weighting choice visible without mixing product sizes or units.

MeasurementCalculationResult
First completed quantity10:00 minus 08:002 hours for 80 units
Remaining completed quantity20:00 minus 08:0012 hours for 20 units
Unit-weighted completed time(80 × 2 + 20 × 12) ÷ 1004 hours, unit-weighted mean
Whole receipt completionLast completion minus receipt12 hours for the receipt

Both four hours and twelve hours describe this example, but they answer different questions. Use the unit-weighted result to describe the experience of a unit of this item. Use whole-receipt completion to ask when every received unit finished. Do not average units, cases, kilograms, and pallets into a common unit-weighted figure without a justified conversion.

Declare the reporting cohort too. A receipt-date cohort asks what happened to deliveries accepted during a period, including later completions. A completion-date cohort asks which putaways finished during that period, including older receipts. Retain receipt dates in either view so an old backlog clearing this week remains identifiable.

Putaway and release answer separate questions
Putaway clock

Receipt to recorded storage

Availability status

Stored quantity still awaiting release

A completed location movement does not establish that a hold has been lifted.

Show unfinished stock beside completed times

At a noon cutoff in the example, the completed portion has a two-hour result and twenty units remain unfinished. Their current age is four hours. Keep that age in an open-receipt view; it is not their final cycle time. Excluding them without showing the backlog would make the shift look finished before it completed the job.

Match quantities before accepting a duration. For each receipt line, compare received quantity with completed putaway, open work, and documented disposition. Investigate over-completion, missing handling-unit links, and reversed work. A negative duration can indicate a timezone error or a late posting, so retain the raw events instead of replacing the value with zero.

The ERP workflow determines which events exist. Microsoft’s Business Central putaway documentation separates receipt posting from registered warehouse putaway in its advanced receiving method. It also supports partial work and split destination bins. Verify the configured workflow before treating an inventory receipt timestamp as a completed location movement.

Investigate the waiting stage before changing the target

Compare like receipts: the same handling method, inspection requirement, and product group over comparable shifts. A rise in time can come from more inspected lots, larger deliveries, or older work finishing. Keep the number of receipts and unfinished quantity with the result; a single difficult shipment can dominate a small sample.

Where event detail exists, split the clock into receipt-to-inspection, inspection-to-move, and move-to-confirmation. These intervals are an operating diagnostic, not a universal benchmark. Assign the exception to the owner of the missing next event. A completed inspection waiting for a bin decision needs a different response from an uninspected quality hold.

Check stock accuracy while reducing time. If a pallet is confirmed before it reaches its bin, the duration improves while pickers lose a reliable location. Use inventory accuracy as a companion check, and keep the evidence for the movement that produced the clock.

How Permute connects receipt and putaway evidence

Permute sells connected business data, custom applications, and governed analysis. We can scope a recurring receiving report from permitted NetSuite records and Excel logs, retaining the receipt references that connect arrival, movement, and recorded storage. Missing event links stay visible for review.

We apply your declared start, finish, cohort, and weighting rules to the connected records. A warehouse manager can inspect which unfinished receipt lines sit behind a completed-time summary and which quality statuses still block use. The answer depends on the fields and freshness of the sources you authorize.

Inspect the events behind one delivery

Connect a permitted receipt export and putaway log to compare their identifiers and timestamps.

Keep physical completion and release with warehouse owners

We do not observe physical movement, certify inspection, or infer an unrecorded completion event. Warehouse owners approve corrections and release held goods in the operating system. Confirm supported fields and refresh frequency before using the report for shift decisions; a daily export cannot establish a live queue.

Compare clocks that count the same work

Dock-to-stock time becomes comparable when receipt and recorded putaway share a clear scope. State how partial completions contribute and retain unfinished stock beside the completed result. Show quality-release status separately when stored goods remain unavailable. Investigate the delayed handoff using matched source events before changing a staffing or supplier target.

Review your receiving-time definitions

Bring a receipt report and the putaway events it should match to discuss the gaps in a repeatable measurement.

Questions about receiving time measurements

What if the warehouse does not record arrival time?

Use the earliest supported event and name it in the metric. A posted-receipt-to-putaway measure can still reveal delays after posting. It cannot establish the time goods spent waiting before anyone entered the receipt.

How should cross-docked deliveries be treated?

Keep them in a separately labeled flow if they bypass normal storage. Define their finish event with the warehouse owner, such as confirmed transfer to outbound staging. Mixing that clock with storage putaway can change the average when the work mix changes.

Should quality holds be excluded from the clock?

Preserve the full elapsed measure and label any narrower operating view. Record why a receipt is held and who can release it. Excluding held receipts without retaining their age and quantity hides work that can still delay production.