V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryLoad Confirmation
Inventory & traceability · The complete guide

Load Confirmation: Dispatch and Distribution Record Evidence

In short

Follow the products, lots and quantities actually loaded from the loading bay into a retrievable distribution history.

4,010 words · ~19 min read
Dock worker in hair cover, mask, glasses and gloves scanning a labelled pallet with a handheld device as it is loaded into a trailer
On this page
  1. 01What load confirmation means—and what it does not prove
  2. 02US drug and food rules: where load records fit
  3. 03From loading instruction to confirmed dispatch
  4. 04Design the shipment-to-lot evidence trail
  5. 05Recover from interface failures and load changes
  6. 06Worked case: reconciling a short load with mixed lots
  7. 07Worked cases: recipient changes and ingredient-source queries
  8. 08Retrieve affected shipments without double counting
  9. 09Measure reconciliation quality and retrieval effort
  10. 10Failure modes and controls at the loading bay
  11. 11Implementation and review checklist
On this page · 11 sections
  1. 1What load confirmation means—and what it does not prove
  2. 2US drug and food rules: where load records fit
  3. 3From loading instruction to confirmed dispatch
  4. 4Design the shipment-to-lot evidence trail
  5. 5Recover from interface failures and load changes
  6. 6Worked case: reconciling a short load with mixed lots
  7. 7Worked cases: recipient changes and ingredient-source queries
  8. 8Retrieve affected shipments without double counting
  9. 9Measure reconciliation quality and retrieval effort
  10. 10Failure modes and controls at the loading bay
  11. 11Implementation and review checklist
AI · Explain it for MY operation

How does Load Confirmation apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What load confirmation means—and what it does not prove

Load confirmation is the recorded verification of the products, lots and quantities physically loaded onto a specified outbound shipment. In common dispatch practice, it connects evidence from the loading operation to the shipment record: planned contents describe intent, while confirmed contents describe the observed load.

The distinction matters when material is picked but left behind, substituted or removed before departure. A planned shipment line alone cannot establish which lot actually travelled. Linking confirmed contents to distribution records supports recall readiness by making the outbound lot-to-shipment relationship retrievable.

TermEvent or decision recordedBoundary
Pick confirmationStock selected from a storage location.Records selection or warehouse movement, not loading.
Staging verificationContents checked in the dispatch staging area.Staged material may still remain at the site.
Load confirmationProducts, lots and quantities verified aboard the specified shipment.Establishes the observed load, not downstream receipt.
Goods issueInventory posted out against an outbound transaction.An inventory posting is not itself physical loading evidence.
Proof of deliveryDelivery or receipt acknowledged at destination.Addresses the destination event rather than origin loading.
Quality releaseAuthorised product-disposition decision.Determines release status rather than shipment contents.

These are operational distinctions, not universal legal definitions; local systems may use different labels or combine transactions. Load confirmation does not itself establish customer receipt or replace an authorised quality-release decision. An EDI 945 shipping advice may communicate shipment information, but the message and its underlying loading evidence serve different purposes. When reviewing a dispatch record, distinguish what was observed from what was posted, communicated or approved.

02US drug and food rules: where load records fit

As an operational practice, treat load confirmation as supporting evidence for distribution records: map its fields to the applicable recordkeeping duties rather than treating a warehouse status as the legal requirement.

Binding law: US finished drug products

For US finished drug products subject to 21 CFR Part 211, 21 CFR 211.196 requires distribution records to contain the product name and strength, a description of its dosage form, the consignee’s name and address, the date and quantity shipped, and the drug product’s lot or control number.

For US finished drug products subject to Part 211, 21 CFR 211.150 requires written distribution procedures to be established and followed.

For US finished drug products subject to Part 211, 21 CFR 211.150(a) requires a procedure for distributing the oldest approved stock first and permits a temporary, appropriate deviation.

For US finished drug products subject to Part 211, 21 CFR 211.150(b) requires a system through which each lot’s distribution can be readily determined to facilitate recall if necessary.

Binding law: US food nontransporters

For US food nontransporters subject to 21 CFR Part 1, subpart J, 21 CFR 1.345(a) requires records to be established and maintained for food they release. For these US food nontransporters, 21 CFR 1.345(b) requires reasonably available information identifying the specific source of each ingredient used to make every finished-product lot.

For US food under subpart J, check the current text of 21 CFR 1.345 for record particulars. This mapping addresses nontransporter recordkeeping, not transport operating instructions or rules for other jurisdictions or product categories.

Industry practice, guidance and software support

Linking confirmed shipment contents to lot-level distribution records is an operational recommendation, not official agency guidance. For software implementation, use that linkage as a design objective and assign review and approval to accountable people. Treat a completed workflow as evidence to assess, not as a compliance conclusion.

03From loading instruction to confirmed dispatch

The following is a proposed dispatch-control sequence, not a mandated workflow. Its purpose is to connect the loading instruction to the goods actually leaving, with an accountable owner at each handoff.

  1. Identify the shipment and loading location. The loading operator checks the shipment reference, bay and assigned vehicle or trailer against the loading instruction. Warehouse teams can use a trailer pool record to help distinguish the intended equipment from nearby equipment.
  2. Associate recipient and carrier. The dispatch coordinator checks the intended recipient, delivery address and carrier against the shipment instruction before loading proceeds, so a correct product selection is not attached to the wrong destination.
  3. Verify physical contents. The loader or designated checker compares product identity, packaging and quantities with the instruction. Packing list verification supports this dispatch check, but the list remains a comparison document rather than proof of what entered the vehicle.
  4. Capture actual lots and quantities. The recorder attributes each loaded line to its actual lot, quantity and unit of measure, retaining container references where useful. This creates the dispatch handoff for bin-level lot genealogy rather than merely carrying forward planned allocations.
  5. Reconcile differences. A named discrepancy owner investigates shortages, overages and substitutions. Remove goods taken back off the vehicle from the confirmed contents; identify replacement lots explicitly; exclude cartons still at staging when closing the shipment.
  6. Review exceptions. The site's procedure should name who records loading, who resolves discrepancies and who authorises dispatch. The designated authoriser reviews unresolved differences and their disposition before permitting departure; recording an exception does not itself resolve it.
  7. Record departure and distribution linkage. The dispatch recorder captures the departure event and links the final confirmed contents to the shipment's distribution record, allowing the recipient and shipped lots to be retrieved together.

Use a final physical check after loading changes and before shipment closure as the confirmation observation point. Any subsequent movement calls for renewed reconciliation. Record when loading occurred separately from when the entry was made, identifying the recorder. Manual label-and-count checks and scanning can serve the same objective: verify the identity and quantity of physical goods. A scan alone does not establish that the scanned carton remained on the vehicle.

Suggested Load-Confirmation Workflow
  1. 1
    Identify shipmentMatch shipment, recipient, carrier and loading location.
  2. 2
    Check loadCompare physical goods with the loading instruction.
  3. 3
    Capture contentsRecord actual products, lots, quantities and units.
  4. 4
    Reconcile differencesAccount for substitutions, removals and goods left behind.
  5. 5
    Review exceptionsRoute discrepancies to the designated decision owner.
  6. 6
    Record departureCapture dispatch facts and preserve subsequent amendments.
  7. 7
    Link DistributionConnect shipped contents to retrievable recipient records.
Physical checks feed linked records; designated people resolve exceptions and authorise decisions.

04Design the shipment-to-lot evidence trail

A practical traceability data model links the records below without prescribing a database schema. Keep shipment, order and lot identities separate: an order can span shipments, while a shipment can contain multiple orders and lots. Record those relationships explicitly rather than using an order number as the shipment identifier.

RecordSuggested contents and relationships
ShipmentShipment identifier; linked orders; dispatch date; recipient identity and address as applicable to that shipment. Preserve this recipient snapshot instead of relying only on a mutable customer-master entry.
Load lineShipment link, order-line reference, product, lot, quantity and unit. Store the applicable conversion factor and source and destination units alongside any converted quantity. Separate mixed lots into distinct lines.
EventEvent identifier, action, time, actor and affected load lines. Where pallets are used, link the pallet identifier to its contents at that event; the identifier alone does not describe the load.
ExceptionAffected shipment, lines or events; discrepancy; reason; disposition; reviewer and review decision. Link any corrective event rather than leaving the resolution in disconnected notes.
Distribution entryShipment and recipient snapshot links, shipped product, lot, quantity and unit. Link each entry to the contributing load lines and supporting events so the recorded contents can be reconciled.
Lot genealogyFinished-lot links to consumed ingredient lots and their sources, supported by production or consumption records. Link the shipped lot to this layer; a loading event does not create manufacturing genealogy.

For the correction audit trail, retain the original event and identify the superseding event. Connect both to the exception reason and review decision, including reviewer identity and review time. Retrieval should distinguish the effective record from its retained history, not silently overwrite the earlier version. This supports attributable recording and data integrity. Record the correction effective date so retrieval does not misapply it to shipments confirmed before the change.

Keep batch and bin-level genealogy separate from dispatch evidence while retaining their lot-level connection, so a dispatch correction never silently rewrites genealogy already recorded upstream.

Illustrative shipment evidence model

Shipment

Identifies dispatch and preserves recipient context.

  • shipment_id
  • consignee_id
  • consignee_name_snapshot
  • consignee_address_snapshot
  • carrier_id
  • dispatch_status

Load Line

Connects loaded product and lot quantities.

  • load_line_id
  • shipment_id
  • product_id
  • lot_control_number
  • quantity_loaded
  • quantity_uom

Load Event

Preserves observation, timing and event identity.

  • event_id
  • load_line_id
  • event_type
  • occurred_at
  • recorded_at
  • operator_id
  • source_event_id

Exception

Links discrepancies, decisions and superseding events.

  • exception_id
  • load_line_id
  • reason_code
  • disposition
  • reviewer_id
  • supersedes_event_id

Distribution Entry

Records shipped contents; product attributes vary.

  • distribution_record_id
  • shipment_id
  • load_line_id
  • product_name
  • product_strength
  • dosage_form
  • shipped_at
  • quantity_shipped
  • quantity_uom

Lot Genealogy

Connects finished lots with ingredient-source records.

  • lot_record_id
  • product_id
  • lot_control_number
  • ingredient_source_record_id
Linked records preserve load identity, recipient context, corrections and source relationships.

05Recover from interface failures and load changes

Treat the following as a proposed industry-practice design, not a regulatory requirement or a statement of software capability. Map warehouse-to-transport interfaces and ERP integration around explicit record ownership:

  • Order management to warehouse execution: the order administrator owns authorised shipment instructions; the warehouse supervisor owns observed loading facts.
  • Warehouse execution to ERP inventory posting: the inventory controller owns acceptance and reconciliation of shipped quantities, not the physical observation.
  • Warehouse execution to transport planning: the transport planner owns the load assignment and acknowledges revised contents.
  • Accepted shipment records to distribution-record retrieval: the distribution-record custodian owns the retrievable shipment-to-lot view and unresolved-mismatch queue.

Separate event capture from transaction acceptance. A loading observation can exist while its inventory message remains pending acknowledgement. Display that pending state with the destination, source-event identifier, failure reason and responsible owner; do not label it completed posting. Keep acknowledgement status separately for each destination so transport acceptance cannot imply inventory acceptance.

Use a stable source-event identifier across retries. At each destination, associate the accepted transaction and acknowledgement with that identifier. A duplicate delivery should return the existing acceptance result rather than add shipped quantity again. Where acceptance is uncertain, reconcile the destination transaction before replaying the message.

For offline loading, capture shipment, lot, quantity, unit, operator and occurrence time. On recovery, retain receipt time separately and reconcile against physical contents and existing postings. Route late-arriving events and conflicting edits to the responsible owner; preserve earlier facts and record the resolution instead of silently overwriting them.

If a pallet is unloaded or another lot substituted after confirmation, link the removal and replacement to the original confirmation. Keep the revision pending while owners reconcile inventory and transport acknowledgements; only then make the reviewed contents the operative shipment record, retaining its predecessor.

06Worked case: reconciling a short load with mixed lots

Assume the shipment contains distinguishable lots, cartons have uniform contents within each applicable carton-to-unit conversion, and there is no unexplained loss. Quantities are expressed as cartons and individual saleable units. The conversion may differ between lots; use the applicable unit conversion for each line.

Observed facts and reconciliation

Some cartons from the partially loaded lot remain at the dock. All staged cartons from the other lot are loaded. Keep the observations separate by lot rather than treating the shipment as a single carton total.

LotLoaded cartonsShipped saleable units
Partially loaded lotStaged cartons minus cartons left behindLoaded cartons multiplied by saleable units per carton for this lot
Fully loaded lotStaged cartons minus cartons left behind; none remain, so loaded equals stagedLoaded cartons multiplied by saleable units per carton for this lot

Decision and reviewer check

Confirm only the physically loaded amount for each lot and record the short-load reason. Keep the dock remainder outside the departed quantity, retaining its lot identity and location through bin-level lot genealogy. Resolve the commercial order balance separately: an unfulfilled order quantity is not evidence that goods departed.

The reviewer compares loading observations, remaining staged stock, line-level quantities and the proposed distribution entry. For each lot, staged cartons should reconcile to loaded cartons plus cartons left behind; the shipped saleable-unit quantity should agree with that lot’s conversion. The proposed distribution entry should reflect those loaded quantities, not the original staging instruction. Do not use an order-level total to conceal a lot-level mismatch: agreement in aggregate cannot establish which lot actually shipped.

07Worked cases: recipient changes and ingredient-source queries

These hypothetical cases apply the regulatory mapping above through proposed operational controls, not additional legal requirements. They address drug distribution and food-source investigation separately; neither extends those rules to other products or jurisdictions.

Drug distribution: recipient changes after departure

Assume a drug shipment has departed, its loaded lots and unit quantities remain unchanged, and the intended recipient changes afterwards. The correction concerns destination history, not a new loading event. Preserve the departure record with its original shipment instruction, consignee context, lots, quantities and recorded units.

Attach a destination amendment identifying the revised recipient and address, the reason for the change, when it was authorised and by whom. Keep that authorisation distinguishable from the carrier’s acknowledgement or execution of the instruction. If forwarding occurs, link its movement record to the departed shipment. If a replacement shipment is dispatched, give it a separate identity and link the reason for replacement rather than rewriting the original consignee.

As a proposed retrieval control, present the original instruction, revised destination and any later receipt evidence as separate facts. An amended instruction indicates where the shipment was directed; it does not prove delivery there. Where receipt evidence is absent, leave receipt unresolved. Linked container status histories can help organise shipment-traceability evidence without substituting for destination or receipt records.

Food: tracing an ingredient source into shipments

Assume ingredient-source relationships already exist for finished-product lots, a source query identifies affected finished lots, and shipped quantities remain expressed in their recorded units. Start with the ingredient source and its associated ingredient lots. Follow the recorded consumption relationships into finished-product lots, then match those lots to confirmed shipment lines and their recipient records.

The proposed result retains the source-to-finished-lot relationship alongside each shipment reference, recipient, shipped quantity and unit. Keep unlike units separate rather than presenting an unsupported combined total. This connects ingredient traceability through lot genealogy with the dispatch evidence needed to identify recorded destinations.

If the ingredient-to-finished-lot link is missing, the shipping record may still show where a finished lot went, but cannot alone establish whether that lot used the queried source. Mark the relationship as unresolved and investigate production or ingredient-use records; do not interpret a missing link as evidence that shipments were unaffected.

08Retrieve affected shipments without double counting

For recall management, a practical retrieval view contains the affected lot, shipment identity, recipient name and address as recorded at dispatch, shipment date, shipped quantity and unit, and links to amendments. Keep quantities separated by unit unless a documented conversion supports aggregation.

Select records with evidence of departure; exclude staged and cancelled entries from dispatched totals. Use the effective amended record rather than adding superseded versions. Deduplicate interface retries by the underlying dispatch-event identity, not message arrival time, so repeated transmissions do not become additional distribution.

Keep later receipts and returns linked as separate events, with their own dates and quantities. Do not subtract them from or overwrite the original dispatch history. The result is distribution evidence for follow-up, not a complete account of current possession: onward transfers, consumption and unreported movements may remain outside the query.

09Measure reconciliation quality and retrieval effort

Use these proposed operational measures with a fixed reporting period, population and data cutoff. They support right-first-time performance review, not a conclusion of compliance.

  • First-pass reconciliation: confirmed shipments needing no quantity or lot correction divided by confirmed shipments in the chosen reporting population. Retain correction history so a corrected shipment does not become a first-pass success.
  • Lot-to-distribution linkage completeness: applicable departed load lines with a retrievable lot-to-distribution link divided by all applicable departed load lines. Define applicability before counting; neither all orders nor scan events is the denominator.
  • Unresolved exceptions: report counts by status and age since occurrence at the cutoff. Measure occurrence-to-entry delay from the physical event to record entry, separately from interface acknowledgement delay measured from transmission to acknowledgement.
  • Retrieval exercise: specify product, lot, departure period, destinations and included records before timing. Set completion as reconciliation of all in-scope departed lines to distribution records, with gaps identified. Record elapsed time and unresolved gaps at stopping; label an incomplete exercise accordingly.

Exclude loads cancelled before departure consistently. Count each shipment or line once, using its current entry while retaining superseded history. Keep missing-data cases visible as unknowns, not successes or silent exclusions; report affected counts alongside each measure.

10Failure modes and controls at the loading bay

Use this matrix as a practical loading-bay risk review, not a universal regulatory checklist. An FMEA can help prioritise controls according to the consequences of a misidentified or incorrectly recorded load.

Failure modeObservable signalPreventive or detective controlReview evidence
Confirmation copied from a pick listConfirmation reflects planned contents; no loading observation is recorded.Observe identified handling units entering the assigned vehicle or container.Loading-point check linked to shipment, operator and time.
Pallet label no longer matches contentsRepacked cases disagree with the pallet-content record.Verify the pallet-content relationship after changes and before confirmation.Updated content record and physical verification.
Unrecognised mixed-lot palletCase lot markings differ from the single recorded lot.Reconcile quantities separately for each lot on the pallet.Lot-level lines tied to the pallet and shipment.
Inconsistent quantity unitsCase counts are compared directly with individual-unit quantities.Use an explicit, product-specific pack conversion before reconciliation.Original units, conversion basis and reconciled quantities.
Shipment identifier reusedOne identifier points to unrelated dispatches.Check identifier uniqueness before assignment; retain separate load references.Identifier history and shipment-to-load relationship review.

Completeness can mislead: every field may be populated while the record describes the wrong shipment. Review relationships among shipment, pallet, lot and destination, then test correspondence with the physical load—not field presence alone. Contemporaneous recording supports the observation trail. For duplicate messages and offline events, use the recovery section above rather than treating populated fields as proof of successful recovery.

11Implementation and review checklist

Use this suggested checklist to accept and maintain local dispatch controls, assigning each acceptance step below to a named reviewer.

  • Process ownership: name who records loading, resolves discrepancies, approves relevant decisions and maintains the procedure. Keep human approval distinct from software status changes.
  • Event definitions: agree what staged, loaded, removed, confirmed and dispatched mean locally, and what evidence establishes each event.
  • Identifier relationships: test the links between shipment, order line, handling unit, product, lot and recipient without relying on free-text matching.
  • Quantity units: identify the recorded unit at each handoff and validate conversions, including partial handling units and product-specific pack sizes.
  • Exception authority: define who may stop dispatch, correct records or authorise an amendment. Connect unresolved discrepancies to exception-based review, with a named resolution owner.
  • Interface acknowledgement: distinguish a message sent from a transaction accepted; assign responsibility for missing acknowledgements and controlled recovery.
  • Record retrieval: demonstrate that an authorised reviewer can retrieve shipment contents, the recipient snapshot and supporting events, including corrections.

Acceptance and change review

Follow a physical load into the distribution view, then trace each recorded line back to its supporting events. Compare identities, quantities, recipient details and decision history. Retain the exercise result and assign any discrepancies for resolution.

Repeat with a short load, an amended shipment and an unavailable interface, using the reconciliation and recovery logic covered above. Check that the resulting distribution view reflects the resolved outcome without duplicating the shipment.

After relevant process or system changes, use change control to review identifier mappings, unit conversions, recipient snapshots and permissions.

Frequently asked questions

Q.Can a carrier’s signature serve as load confirmation, and what would it leave unconfirmed?+

A carrier’s signature can serve as an operational acknowledgement of the checks explicitly recorded beside it. A signature against a trailer identifier and pallet count does not, by itself, establish the products, lots or quantities inside those pallets. For stronger confirmation, connect the signed acknowledgement to the shipment’s itemised loading record and identify who performed each check. Packing list verification addresses contents; attributable recording helps distinguish the loader’s observations from the carrier’s acknowledgement.

Q.How can a cross-dock confirm contents when sealed pallets are not opened?+

A cross-dock can typically confirm identified handling units without claiming to have inspected their contents. Record each pallet identifier, its associated upstream contents record, visible condition, and any seal identifier or discrepancy. Describe the check as an external identity and condition check, with contents attributed to the upstream record. Seal management supports recording closure condition, while a container ID scan links the physical unit to its declared contents. Route mismatched or unreadable identifiers for investigation.

Q.Who should own the record when a third-party warehouse performs the loading?+

Operationally, distinguish the record creator, custodian and business owner rather than assigning an ambiguous single owner. The warehouse typically records the loading event; the contracting manufacturer or distributor defines how that evidence becomes part of its shipment history. The operating agreement should address access, corrections, retrieval and custody after the service ends. An EDI warehouse shipping advice can communicate shipment details, but WMS–TMS integration arrangements should also define which event represents physical loading rather than planned dispatch.

Q.How should bulk loads be handled when dispatch and inventory use different measurement units?+

Keep the observed loading quantity and unit alongside the converted inventory quantity rather than replacing the measurement with a calculated value. For a mass-to-volume conversion, record the density basis and any temperature basis used; distinguish measured density from an assumed value. For weighed loads, retain gross and tare values where applicable. Net-versus-gross reconciliation addresses the weighing basis, while a density checkpoint supports the conversion basis. Record rounding and investigate differences against the site's approved operating criteria.

Q.What record should remain when a confirmed shipment is cancelled before departure?+

As a recordkeeping practice, retain the original confirmation and attach a cancellation event rather than deleting the loading history. Record the reason, responsible person, time, and whether goods remained on the vehicle or were unloaded. Link any inventory reversal to the physical disposition, so cancellation does not imply that stock has already returned to storage. A process event log can distinguish loading, cancellation and unloading events without presenting the cancelled movement as a completed departure.

Q.How should returned goods be connected to the original confirmed shipment?+

A practical return record references the original shipment and its relevant product, lot and quantity lines, then records what actually came back. Keep the returned quantity separate from the original dispatched quantity, including partial returns and goods arriving through an intermediary. Where identification is uncertain, record the uncertainty rather than forcing a match. Returns management should preserve the return’s condition assessment and disposition decision separately from its shipment link; matching the shipment does not establish suitability for resale.

Q.Can paper loading checks and electronic distribution records work together?+

Operationally, yes: use a common shipment identifier and a defined reconciliation step between the paper check and the electronic record. Identify which medium holds each authoritative entry, who transcribes information, and how discrepancies are resolved. Preserve corrections without obscuring the original observation, and keep the paper record or its controlled copy retrievable through the shipment reference. Document control helps structure this arrangement. Whether a particular hybrid workflow meets applicable legal requirements depends on its product, jurisdiction and implementation.

Q.How should consignee records distinguish a customer’s head office from the actual delivery location?+

As covered above, 21 CFR 211.196 requires the consignee’s name and address on the distribution record. When a customer has multiple receiving sites, record the physical ship-to address actually used for that shipment rather than a single head-office entry, and keep it independent of a customer master record that can change later. This keeps recall readiness searches pointed at the location that actually received the lot.

Primary sources

  • 21 CFR 211.196
  • 21 CFR 211.150
  • 21 CFR 1.345
Software that covers Load Confirmation
V5 Ultimate Shop Floor Data Collection Software
Barcode scans, scale readings, operator checks and downtime reasons recorded at the station as work happens, each with who, what…
Talk to us about Load Confirmation

Want to see how Load Confirmation could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Related terms
  • → FSMA 204
  • → KDE
  • → CTE
  • → GS1-128
  • → GTIN
  • → SSCC
  • → EDI 856
  • → UDI

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC