Underweight and Overweight Exceptions: Operating Principles and Hub Boundaries

Underweight and overweight exceptions are among the most misleading alarms in a modern parcel hub. A parcel can be flagged as underweight because it is genuinely light, because the scale sampled a partially settled package, or because a calibration offset has drifted across the induction line. The same ambiguity applies to overweight flags, which may indicate a genuinely heavy item, a merged reading of two packages, or a sensor vibration artifact that exceeds the contact time threshold. This article describes how weight exceptions arise, why they matter at the hub, and how operations and maintenance teams can interpret them correctly while respecting the physical and system boundaries of the sortation equipment.

The Operating Context: Why Weight Is a Control Signal #

At the hub, weight is not merely a billing attribute. The sortation control system uses weight to assign parcels to destination chutes, to enforce conveyor load limits, to generate dispatch manifests, and to route items through secondary handling stations. Underweight parcels may be suspected of being empty, while overweight parcels may represent a safety hazard on powered conveyors or a load that exceeds the rated capacity of a tilt tray. Weight exceptions therefore trigger actions in multiple systems: the sortation controller, the warehouse management system, the revenue protection team, and the maintenance work order queue. Because each system applies a different tolerance, the same exception can be interpreted differently by different audiences. A single documented event therefore requires a single disciplined investigation.

The Weight Assessment Point: Where a Parcel Becomes a Number #

Most hubs measure weight at the induction area, just after singulation and immediately before the parcel is launched onto the main sortation conveyor. The measurement is usually performed by a dynamic scale, often integrated with a dimensioner and a barcode scanner in a single volume scan tunnel. The scale relies on several components: load cells or a weighing frame, an encoder or tachometer that supplies belt speed, a PLC that samples the analog signal, and a controller that correlates the weight sample with the barcode read. The interaction is time-sensitive. The controller expects the parcel to remain fully on the scale deck for a minimum dwell time. If a parcel is short, the leading edge may leave the deck before the trailing edge has fully arrived, and the scale records a partial or oscillating reading.

Component Interactions and Timing #

Three interactions dominate weight accuracy. First, the encoder must match the actual belt speed; if the belt is slower than the encoder reports, the controller may sample the wrong window. Second, the scale deck must be mechanically isolated from the upstream and downstream conveyors; any pinch point or transfer plate wear can transmit vibration into the weighing frame. Third, the barcode scanner must associate the correct parcel with the correct weight window. If the scanner reads a label from a neighbouring parcel, the system may assign an underweight or overweight reading to the wrong identity. These interactions mean a weight exception often reflects a system timing problem rather than a true parcel problem.

Underweight Exceptions: Why the Number Falls Below the Floor #

An underweight exception is raised when the measured weight falls below the minimum threshold for the parcel class, below the declared weight, or below the threshold configured for all parcels in a given product type. The most common genuine cause is an empty or nearly empty parcel, such as a returned item that contains only a printed label and a plastic bag. However, operational causes are frequently more significant. Underweight flags often come from:

• Parcel bouncing on the scale deck, especially when belt speed is high and the parcel slides or hops.
• A lightweight large parcel whose corners are still on the preceding conveyor when the sample is taken, so the scale sees only a portion of the item.
• A parcel that overlaps a previous parcel by a few centimetres, causing the controller to miss the full contact period.
• Scale calibration drift that shifts the zero point upward, making all light parcels read lower than their true mass.

From an operational viewpoint, underweight exceptions matter because they can prevent a parcel from being inducted, cause it to be diverted to a manual station, or generate a revenue protection query. The hub boundary is defined by the minimum weight threshold; anything below that threshold is considered suspect until a human confirms its contents.

Overweight Exceptions: When the Scale Sees Too Much #

Overweight exceptions are raised when the measured mass exceeds the maximum threshold for the parcel, the sortation chute, or the conveyor itself. Some thresholds are product-specific; others are hard limits set by the mechanical design of the sortation system. The cause may be a genuinely heavy parcel, but it can also be a measurement artifact. Common causes include two parcels travelling too closely together and being counted as one weight window, a parcel that absorbs moisture or carries residual debris from a previous handling stage, a mislabelled parcel whose declared weight is lower than the actual weight