01Open a versioned manifest
Record manifest ID, version, origin facility, carrier and account, service, route or destination, planned conveyance, creation time, local time zone, cutoff, preparer and status. Link the dock appointment, trailer or container, departure and any carrier batch or pickup reference. Define scope: parcel collection, route run, consolidated consignment, container load or another agreed population. Prevent two active manifests from claiming the same departure and prevent a retry from creating an unrelated second manifest. Preserve the exact outbound file or rendered document and schema version. A manifest number can also have formal customs meaning in some workflows; do not label an internal dispatch list as a customs filing or claim customs acceptance without the applicable carrier and authority process.
02Build expected and loaded populations
Start from released shipments and packages at outbound staging. List package, parent handling unit, order, shipment, destination, carrier service and load assignment. Compare with actual loading events tied to the physical vehicle, trailer or container. Exclude void labels and canceled shipments but retain their history. A parent pallet can represent child cartons only when the hierarchy is current and accepted by the transport process. Detect one child attached to two parents, a package with no shipment, a shipment split across manifests without approval and a loaded package still assigned to a different route. GS1 EPCIS supports object, aggregation, loading and shipping events; define which verified local event establishes the expected manifest population. Manual contingency lists require later event-by-event reconciliation.
03Validate identity, service and totals
Check uniqueness of tracking, consignment and package IDs across the relevant carrier account and reuse period. Match shipper, consignee or destination code, service, routing, package type, piece count and measured attributes used by the carrier. Do not invent weight, dimensions, dangerous-goods, customs or value data. Sum child packages to parent, package count to consignment and consignments to manifest control totals. Compare separate totals for labels created, physically loaded and carrier accepted. A matching grand total can hide a wrong package substituted for another, so retain identity-level comparison. Flag an invalid postal or location code, service not available, missing required reference, account mismatch and package data rejected by the carrier. Protect addresses, customer data and high-value routing details. Model the carrier hierarchy explicitly: pickup or end-of-day batch, trailer or container, master consignment, shipment, piece and label can each have a different identifier and acceptance state. Record which level the response and control total address. For multi-carrier consolidation, keep the consolidator's house reference, underlying carrier reference and last-mile tracking separate. Do not flatten reconsigned or relabeled parcels into one ID without predecessor and successor links. Verify that every printable label belongs to the account, service and manifest environment being closed; test and sandbox labels must never enter production totals. Detect tracking ranges consumed but unused, labels created after cutoff and packages manifested under a disabled shipper number.
04Transmit and interpret carrier response
Record transmission time, channel, file or message ID, checksum where supported and technical acknowledgement. Keep syntax acceptance, business acceptance and pickup or custody as different states. Parse rejection and warning codes without replacing the carrier's original response. Route rejected package, consignment or whole manifest to an owner. Retry only under idempotency controls so the same package is not accepted twice. Record carrier-assigned identifiers and map them back to internal IDs. A portal screen showing submitted is not evidence of acceptance if the process returns a later error. If the carrier provides no package-level response, document the limitation and strengthen physical and pickup reconciliation rather than inventing acceptance. Protect credentials and never paste secret account data into the operating record. Distinguish file receipt, batch validation, shipment creation, closeout acceptance, pickup-list availability and end-of-day confirmation when the carrier exposes those stages. Store the raw response code, human-readable description and affected line position. Check whether a rejected parent invalidates all children or only the container record. Some integrations return success before asynchronous validation; poll or receive the final status using the same correlation key. Quarantine timed-out requests until their remote outcome is known. A blind retry after timeout can create a second consignment. Reconcile carrier sequence numbers, trailer-load IDs, parcel-container IDs and end-of-day totals without assuming identical naming across services.
05Control cutoff, close and reopen
Define who may close a manifest and what must be complete: loading population, rejects, documents, route and carrier readiness. Store close time and locked version. A late package needs a deliberate next-manifest, alternate-service, controlled reopen or hold decision. If reopening is permitted, record reason, requester, approver, added and removed package IDs, revised totals, retransmission and carrier response. Prevent removal of a package that already transferred custody without a compensating carrier event. Void unused labels and preserve void confirmation. Do not backdate close to meet an operational metric. When the vehicle departs during a transmission outage, follow the authorized contingency and reconcile the exact departure population as soon as systems recover. Create a close-readiness dashboard from discrete conditions rather than one editable ready flag: sorter drained, exception chute cleared, manifest rejects resolved, packing backlog assigned, route containers sealed where used, handheld offline queue synchronized, pickup paperwork generated and supervisor variance review complete. Record not applicable rather than fabricating completion. Freeze the package candidate set while final counts run; new releases go to the next cycle unless an authorized reopen admits them. Keep the original close snapshot and a delta ledger showing each later action. This supports an exact before-and-after comparison when a carrier requires an end-of-day rerun or a collection is canceled after close.
06Reconcile carrier handover and departure
Compare carrier-accepted manifest packages with scan or signed pickup evidence, loaded events, vehicle or container assignment and gate departure. Keep carrier arrival, loading, manifest acceptance, custody handoff and departure timestamps distinct. For parcel containers, reconcile container seals or IDs and child package count where the process supports it. UNECE CUSCAR illustrates a formal cargo report with unique manifest reference, consignments, equipment and packages, but it is specifically for carrier-to-Customs reporting; use it only as structural context, not as a claim that an internal manifest satisfies customs requirements. Investigate manifested-not-loaded and loaded-not-manifested packages immediately and retain their physical location or carrier case. Capture trailer sweep or parcel-container closure through the facility's authorized process. Link a carrier handheld acceptance batch, dock receipt or pickup signature to the manifest version and container set it actually covers. When the driver signs only for container count, do not present it as child-piece acceptance. Record an exchanged cage, pallet or bag ID and any broken or replacement seal. Reconcile drop trailer, live pickup and unattended collection as different handover patterns. For a linehaul connection, record planned departure leg, induction hub and connection code without treating the warehouse manifest as proof of downstream sort. When a collection rolls to another vehicle, preserve the original failed handover and create the replacement equipment link. Compare the first carrier network event with the pickup cohort; absence after the agreed observation window becomes a tracing exception, not an invented departure scan.
07Close residuals and improve dispatch
Bridge released packages to loaded, carrier accepted, rejected, removed, held, carried forward and unknown. Sweep outbound staging and the vehicle handoff area for orphan packages and labels. Start from each manifest line to find the package event and from each departed package to find the manifest line. Close only when every difference has an outcome. Monitor manifest first-pass acceptance, rejected package rate, duplicate submission, loaded-not-manifested, manifested-not-loaded, reopen frequency, late package, voided label and reconciliation time. Analyze by carrier, service, interface, shift and error code. Use recurring findings to repair label data, package hierarchy, staging cutoff, interface retries or carrier setup. Do not improve manifest accuracy by excluding troublesome packages from the expected population. Reconcile the next carrier invoice or shipment activity file back to the accepted manifest when available. Unexpected billed tracking numbers, a manifest record with no later movement, duplicate pickup events and packages first scanned at another facility can reveal handover or integration gaps. Treat them as investigation signals, not automatic liability. Retain a departure cohort so later status corrections can be attached without reopening the physical warehouse count. Compare manifests by collection cycle and carrier account rather than mixing parcel, pallet and full-load workflows.