# Reconcile Shipment Quantities Without Mixing Units Canonical: https://usdotdata.com/blog/reconcile-shipment-quantity-records Author: John Hauler Published: 2026-10-06T07:17:37.306Z Updated: 2026-10-06T07:17:37.306Z --- To reconcile shipment quantities, compare the same shipment, item, stage and unit of measure across the order, tender, loading record and receiving record. Preserve each document's original count before calculating a difference. Ten pallets and 240 cartons describe different packaging levels; a change in pallet count does not, by itself, establish missing cartons or products. This guide helps shipper and broker operations teams decide whether a mismatch is comparable, needs clarification or records a difference requiring follow-up. The output is a quantity comparison with an evidence owner. It does not determine fault, claim validity or payment entitlement. ## Give every number a unit and a shipment stage A quantity without a defined unit is not ready for subtraction. Record whether the number describes individual products, inner packs, cartons, pallets or another handling unit. Retain the source's wording even when your team uses a different preferred label. The distinction is visible in original carrier instructions. [FedEx Freight's bill-of-lading guide](https://www.fedexfreight.com/en-us/rate-ship/shipping/forms) provides separate entries for handling-unit count, handling-unit package type and pieces. Its examples distinguish pallets from the boxes or items on them. Those definitions describe that form; check the instructions for the document actually used on your shipment. A bill of lading, often shortened to BOL, can carry several quantities at once. “10 pallets / 240 cartons” is not two competing answers. It records 10 outer handling units and 240 cartons within the shipment. Do not add them to make “250 pieces,” and do not assume every pallet contains the same number of cartons. Keep the stage explicit: - **Ordered:** the buyer's requested quantity, including the item and order revision. - **Tendered:** the quantity described in the transportation request. - **Loaded:** the quantity recorded at origin, with who counted what and any stated limitation. - **Received:** the quantity recorded at the destination, with the receiving scope and exceptions. Use “recorded as loaded” when the evidence is a document entry. Use “counted at loading” only when the record supports that observation. A planned quantity copied into three systems is still one planned quantity, not three independent counts. Commercial scope belongs in the [carrier quote comparison](https://usdotdata.com/blog/compare-carrier-quote-scope). Here, the question is narrower: do the quantity records describe the same physical units at comparable points? ## Establish what can actually be compared Start with the shipment reference, origin, destination and relevant delivery or split-shipment identifier. A purchase order can cover multiple loads. Matching its number alone does not establish that two documents describe the same quantity movement. Then identify the item or stock-keeping unit, packaging level and count basis. A stock-keeping unit, or SKU, identifies the particular inventory item. When relevant, retain lot or batch references: equal totals for different products do not establish an item-level match. The [International Trade Administration's packing-list guidance](https://www.trade.gov/packing-list) describes a packing list as an itemization of the contents of each package, with weights and measurements. That makes the actual shipment's packing detail a useful place to investigate how an outer package relates to its contents. A generic catalog pack size is weaker evidence than a packing record applicable to the item and shipment being compared. Before converting cartons to individual products, ask: 1. Which source defines the number of products per carton for this item and version? 2. Does that definition cover every carton, including partial or mixed cartons? 3. Is the recorded quantity a planned packing arrangement or an observed count? 4. Did either location open or count the contents, or only count the outer packages? Keep a calculated equivalent in a separate field. Preserve “50 cartons” beside “600 products expected under packing specification PS-2”; do not replace the first with “600 products counted” when nobody counted the products. For weight comparisons, retain pounds versus kilograms and the stated weight basis. Product-only weight, weight including packaging and an unexplained weight field need clarification before comparison. A weight difference cannot be converted into missing cartons without evidence about what each measurement includes. ## Example 1: carton counts agree, pallet counts differ **Both worked examples below are fictional. All shipments, documents, observations and confirmations are invented for teaching; they do not describe the cited organizations.** Shipment Q-310 concerns one product, SKU A, moving from the same origin to one receiver. There are no split deliveries in the example. The record contains: - **Order O-310, revision 1, October 1, 2026:** 240 cartons of SKU A ordered. No pallet quantity is specified. - **Tender T-310, revision 1, October 2:** 240 cartons on 10 pallets requested for transportation. - **Loading record L-310, revision 1, October 3:** the origin checker records counting 240 outer cartons and 10 loaded pallets. Individual products inside cartons were not counted. - **Receiving record R-310, revision 1, October 4:** the receiver records counting 240 outer cartons and 9 pallets. Individual products inside cartons were not counted. The record contains no explanation of the pallet difference. The reviewer compares each unit separately: ```text Cartons ordered: 240 Cartons tendered: 240 Cartons counted at loading: 240 Cartons counted at receiving: 240 Receiving minus loading: 0 cartons Pallets tendered: 10 Pallets counted at loading: 10 Pallets counted at receiving: 9 Receiving minus loading: -1 pallet ``` The defensible disposition is **carton counts agree; pallet-count difference requires explanation**. Do not write “24 cartons missing” by dividing the origin quantity by ten and assigning that average to the unmatched pallet. Both locations recorded 240 cartons, and an average is not evidence of the contents of any particular pallet. The operations reviewer asks the origin, transportation and receiving record owners for the applicable handling and count records. Repacking or consolidation is one possible explanation to investigate, not a fact to insert into the file. If a later record explains the change, add its reference, source and date; preserve the original observations. This comparison also leaves product contents and condition unconfirmed. An agreement at carton level does not show that every carton held the right contents, nor does it establish that the goods were undamaged. The reviewer closes only the carton-count comparison, leaving the pallet explanation with its named owner. ## Example 2: an ambiguous package count stays unresolved Shipment Q-411 concerns SKU B, with one origin and one receiver and no split deliveries. Its packing specification PS-2 states 12 products per full carton. The supplied packing list describes 50 full cartons, so the **planned** contents equal 50 × 12 = 600 products. The complete comparison record is: - **Order O-411, revision 2, October 1, 2026:** 600 individual products ordered. Revision 1 was superseded before tender and remains in the file. - **Tender T-411, revision 1, October 2:** 50 full cartons on 5 pallets, linked to packing list P-411 revision 1 and PS-2. - **Loading record L-411, revision 1, October 3:** the origin checker records counting 50 sealed outer cartons on 5 pallets. Contents were not opened or counted. - **Receiving record R-411, revision 1, October 4:** the receiver records “48 packages / 5 pallets.” The record does not define “packages,” describe partial cartons or state whether the contents were counted. The five-pallet counts agree. The origin's 50-carton count and the receiver's 48-package notation are **not yet comparable**. The reviewer records the original notation and asks the receiving record owner what was counted and whether the entry covers the entire shipment. Do not report two cartons or 24 products missing at this point. The arithmetic 50 − 48 = 2 is valid only for the same defined unit and scope. Multiplying by 12 adds another assumption about the contents of those units. If the receiver later supplies a traceable clarification that it counted 48 full cartons for the entire shipment, the worksheet can record a **documented difference of two outer cartons** against the origin count. The expected contents associated with two full cartons would be 24 products under PS-2; label that a calculated quantity, not an observed product count or a liability finding. That clarification is a conditional next step, not part of the fictional evidence already supplied. Until it arrives, Q-411 remains **receiving unit clarification pending**. The receiving supervisor owns the answer; the operations reviewer owns the comparison. Neither a matching pallet count nor a matching invoice total resolves the ambiguous notation. ## Keep quantity, condition and disposition separate Avoid one field called “good quantity” that mixes physical count with acceptance. A receiver may observe 100 cartons present, flag three cartons with visible exterior damage, and set those three aside for review. That does not mean only 97 cartons arrived, and it does not establish how many individual products are damaged. Record the total present, the subset with a stated condition, and its disposition separately. Make explicit whether a damaged or quarantined subset is included in the received total. Do not subtract the subset twice when someone later reconciles available inventory. An invoice is another evidence type. The [International Trade Administration's export-document guidance](https://www.trade.gov/common-export-documents) distinguishes the commercial invoice, which describes goods sold and payment, from the packing list's package detail. Our operational recommendation is to use an invoice to reconcile the commercial description, then seek loading or receiving evidence for a physical-count question. An invoiced quantity is not a substitute for a count at either location. Preserve document versions and contradictions. If the shipper revises a loading quantity after delivery, retain both versions, who made the revision, the stated reason and the evidence supporting it. A newer file is not automatically a more reliable observation. Have the responsible reviewer resolve the specific conflict rather than overwriting the earlier count. ## Copy this shipment-quantity worksheet Repeat the evidence block for every stage and unit. Short fields make the record usable in an existing document or spreadsheet without a new system. ```text SHIPMENT Shipment / order / delivery reference: Origin / destination / split-shipment scope: Item or SKU / relevant lot: Comparison owner: EVIDENCE BLOCK Stage: ordered / tendered / loaded / received Document reference / revision / source date: Record supplied by / observed at: Original quantity / exact unit wording: Packaging level / item scope: Counted by / method / count limitations: Packing or conversion source / version: Calculated equivalent / assumptions, if any: Condition subset / included in total? / disposition: Original record or permitted capture reference: COMPARISON Evidence references being compared: Same shipment / item / scope / unit confirmed? Original quantities / comparable unit: Difference, if supportable: Unknown / conflict / exception: Clarification question / owner / next review: Outcome / evidence supporting closure: Reviewer / review time / version retained: ``` Before marking the comparison complete, check that: 1. Every number has a unit, packaging level, stage and source. 2. Split loads and different items have not been combined by accident. 3. Conversions retain their basis and do not turn planned contents into counted contents. 4. Condition exceptions state whether they are included in the quantity total. 5. Revised records remain traceable, and any conflict has an owner. 6. The outcome closes only the comparison supported by the evidence. ## Frequently asked questions ### Are pallets and packages interchangeable units? Only if the relevant record explicitly defines “package” as that pallet-level handling unit. A different form may use the word for cartons or other units. Preserve the exact notation and obtain its definition before comparing it with another record. ### Can the invoice quantity prove how much was loaded? An invoice records a commercial quantity. For the loading question, identify the applicable loading record and what its source actually observed. Agreement between invoice and tender quantities can still reflect the same planned amount copied between documents. ### What if a shipping document was revised? Save both versions, the reason for the change, its source and the evidence it relies on. State which version supports the current comparison and why. If a revision conflicts with an original observation, leave the conflict visible until the responsible reviewer resolves it. ### How should damaged items be counted? Record physical quantity and condition separately, using a consistent unit. State whether the damaged subset is included in the received total and whether the observation concerns packaging or products. A carton with exterior damage is not automatically a carton of damaged products. ### Who should confirm an ambiguous receiving notation? Ask the receiving record owner or the person responsible for the count to explain the unit, scope and method, through your established shipment process. Keep the answer tied to the original document. The comparison reviewer should not choose a convenient meaning for “pieces” or “packages.” ### Does a quantity discrepancy establish fault or a valid claim? No. This process identifies what the records support and what needs follow-up. It does not decide contractual responsibility, liability, claim requirements or the outcome of a dispute. Preserve the evidence for the person authorized to handle the specific matter. ## Resolve one unanswered count before closing the file Choose the first pair of records that cannot be compared, identify the missing unit or scope definition, and assign a precise clarification. Keep physical-quantity reconciliation connected to the shipment while using the separate [contracting and performing carrier checklist](https://usdotdata.com/blog/shipper-contracting-performing-carrier) for entity and assignment questions. The [carrier-verification evidence guide](https://usdotdata.com/blog/carrier-verification-evidence-record) supports those checks; a carrier lookup does not establish what was loaded or received. *Sources reviewed October 6, 2026. John Hauler is USDOTData's editorial persona. The workflow and worksheet are editorial recommendations; both worked shipments are fictional. Original carrier instructions apply to their stated forms, and the cited International Trade Administration guidance concerns export documentation.*