Start with the physical units, not an average pallet
A shipment input register connects the objects being shipped with the values used in a calculation. It answers which measurement belongs to which loaded unit, what was counted, and which equipment record was used. This is useful when a later review finds a different pallet count or quotation dimension: the register allows the reader to locate the changed assumption. The register is your own operational document. The website does not provide a shipment database, customer account or identifier field that should be used to store that information.
Consider a fictional order of 110 packed cases with a selected capacity of 48 cases per pallet. The plan contains two full pallets and one fourteen-case tail. Assume each packed case weighs 6 kg, each pallet has measured tare of 25 kg, and each loaded unit receives 3 kg of protection. These inputs describe an arithmetic exercise, not a supplier specification. An actual register would retain measurements for all three finished loads rather than infer that the tail has the same height as a full pallet.
Give each measurement an object and a definition
Record outside length, width and total loaded height for each completed unit, with units and a measured date. State whether the measurement was taken before or after wrapping and whether a protruding top cap was included. Keep carton dimensions in separate fields. A carton height of 250 mm and a pallet base height of 144 mm are not alternative readings of the same object. Five complete layers would have a nominal loaded height of 1394 mm before any additional height components; a measured result can differ.
Mass needs equally clear definitions. Packed-case mass includes whatever was on the case scale, while empty-pallet tare and separately weighed protection are other components. A completed loaded-pallet scale reading includes those components already. Give the register separate columns for calculated gross and measured gross. Preserve the measurement method and its stated resolution where available. A blank measurement means unknown; entering zero to complete the sheet would create a different and misleading input record.
| Record item | Value or interpretation |
|---|---|
| Case quantity | 48, 48 and 14; total 110 |
| Calculated gross | 316, 316 and 112 kg; total 744 kg |
| Finished dimensions | Measure each unit; do not copy a full-pallet height to the tail |
| Mass definition | Packed cases + empty pallet + separate protection |
| Equipment evidence | Assigned unit dimensions and source date in the local record |
| Public calculation | Only supported numeric inputs and modes, without shipment identity |
Separate assigned equipment from the comparison preset
A container preset is a convenient starting example. The assigned equipment is a specific object or accepted specification supplied for your shipment. Save both records when comparing them: the preset identifier and values, and the assigned unit's confirmed inside dimensions, door opening and payload information. Do not overwrite the historical preset name with a different measurement and then describe the result as unchanged. The assigned-equipment guide explains this distinction for the floor calculation.
Published product dimensions can provide a useful reference, but their scope belongs in the register. The EPAL Euro pallet specification concerns that product; it does not measure a wrapped load at your site. Likewise, a carrier fleet table is an example of equipment rather than a promise about the delivered unit. Save the specific source row and review date so a later change can be assessed without silently combining dimensions from different records.
Use one calculation record for one defined question
For the fictional order, the capacity-based weight record produces three pallets and 744 kg total gross. It retains the full-plus-tail distribution. The calculator can also estimate an even distribution across a supplied pallet count; that is another record with another meaning. Write the active mode beside the result. A shared address does not explain why forty-eight was selected as capacity.
Use the cube calculator separately for each measured envelope or repeated group. A weight record does not carry carton dimensions, and a known-envelope cube record does not establish carton quantity. Attach the relevant result to the register by a local reference that your operation can understand. Keep count, units, selected mode, warnings and result status together. If the planning inputs change, create a revised record rather than retaining an old drawing beside a newly edited number.
A local record before sharing a numeric example
Private record: unit reference; destination; measured date; responsible measurement source; actual quantity; measured and calculated dimensions; mass basis; equipment assignment; outstanding checks. Public example: millimetres, kilograms, 110 cases, 48 cases per pallet, 6 kg per case, 25 kg tare and 3 kg protection. Preserve the connection inside your own record; do not append the private reference to the public calculator URL.
Review the register at the shipment boundary
Reconcile unit quantities back to the order and reconcile calculated component totals back to their group records. Check that a full pallet has not been omitted and that the tail has one tare allowance. If the shipment is divided between destinations, each destination may create its own tail and additional tare. A combined order total can conceal that difference. Confirm which finished units are actually moving before carrying the register total into a quotation or equipment discussion.
Leave unresolved handling, door passage and acceptance questions visible in their own columns. The register helps communicate evidence; it does not convert a geometric result into an approved movement. Its most useful final state identifies what was measured, what was calculated and what still needs confirmation. A colleague should be able to repeat the arithmetic without receiving confidential customer details through a public link.