01
Identity and packaging level
Capture the identifier that the team can reconcile, then state whether the record represents an each, inner pack, case, or pallet. A clean dimension on the wrong packaging level causes a different kind of error.
A scan at the dock is only valuable when the next person can find the item, understand its packaging level, trust the physical facts, and see what happened when the record did not pass a check.
This guide helps an operations team define the receiving record before evaluating a dimensioner, camera, scale, OCR step, or system handoff. Start with one difficult SKU, case, or pallet that regularly creates an exception.
The exact field names depend on the WMS and operating model. The important part is agreeing on the minimum record that lets receiving, inventory, billing, and support refer to the same physical item.
Capture the identifier that the team can reconcile, then state whether the record represents an each, inner pack, case, or pallet. A clean dimension on the wrong packaging level causes a different kind of error.
Keep dimensions, weight, units, and the capture timestamp together. If an item is remeasured, retain enough context to distinguish a correction from a second item.
Decide which photos, labels, operator notes, or checks help a supervisor review an exception later. Evidence should point to the record, not live in an unsearchable folder.
Define what happens when an identifier cannot be read, the measurement is outside the expected range, or the packaging does not match the item record. A field without an owner becomes dock-side memory.
Free planning tool
Choose the item level, capture point, and one exception. The brief below gives a supervisor a concrete starting point for a dock test.
Your receiving-record brief
Required fields: reconcilable identifier; packaging level; length, width, height and weight with units; capture timestamp; evidence link or review note.
Which exception must be routable?: Identity cannot be reconciled. Define an owner and whether this record blocks downstream work.
Why does this record need review now?: A supplier or package changed. Keep the observed change separate from the approved master-data update.
Handoff: map the approved record to its target WMS fields and retain its review status.
Pilot check: run one clean item and one exception through the capture point, then retrieve both records downstream.
This sequence keeps an equipment conversation attached to a record the warehouse can actually use.
Pick the point where the item is stable enough to identify and measure: unpack, putaway staging, a parcel bench, or a pallet lane. Do not begin with a generic equipment list.
List the identifier, packaging level, physical facts, evidence, exception state, and target WMS fields. Mark which entries are required to release work downstream.
Use damaged labels, nested packaging, a remeasure, or an unexpected pallet. The workflow is ready only when an operator knows where that record waits and who resolves it.
Retrieve the record after it reaches its target system. Check that a receiver, inventory planner, or billing reviewer can find the same facts without asking the dock to reconstruct them.
Run a cleaned-up master-data record through current carrier DIM divisors before it reaches billing.
Open DIM calculator →Choose the parcel, pallet, conveyor, or forklift-lane route that fits the item the master record describes.
Open workflow finder →See where master-data accuracy fits into a broader dimensioner evaluation before a vendor conversation.
Open buyer checklist →It is the work of connecting a physical item's dimensions and weight to an identifiable SKU, case, or pallet record that downstream teams can retrieve and use. The equipment is only one part of that record.
They can be related, but they should not be treated as interchangeable. The record needs to state its packaging level so a warehouse does not apply a case measurement to a pallet or an each measurement to a case.
No. A capture system can create physical facts at the dock, while the operation still needs field definitions, exception ownership, and a clear target-system handoff.
250+ installations · 99.5% accuracy
Book a Demo