What Is a Shipping Manifest? Template, Carrier Handoff & Tracking Reconciliation

Shipping Manifest is a document or electronic record that lists the packages or shipments tendered to a carrier and summarizes which pieces were handed to the driver or dropped at a carrier induction point. A manifest is used to batch and communicate shipment details (tracking numbers, weights, package counts and identifiers) to a carrier, but generating a manifest is not the same as physical carrier acceptance or final delivery confirmation.

Below is a compact visual example of a manifest header and a couple of line items so you can see the fields you will use when creating one in a WMS, 3PL portal or spreadsheet; after the example the article explains how manifests operate across parcel end-of-day, pallet freight and 3PL workflows and how to reconcile mismatches between your packed orders, the carrier's recorded pick-up and the carrier's first scans.

Visual Example — Manifest Header And Line Items

Header: Facility: ABC Fulfillment, Origin Facility ID: FTL-001, Carrier: ExampleCourier (Ground), Service: Expedited, Dispatch Date: 2026-11-10, Manifest ID: M-20261110-42, Batch ID: B-987

Line Items (sample):

OrderNumber,PackageSeq,TrackingNumber,Weight_lbs,Length_in,Width_in,Height_in,DeclaredValue,Contents,Special
100523,1,EXC123456789,2.3,12,8,4,25.00,Shirt,None
100524,1,EXC123456790,5.1,18,14,6,120.00,Shoes,SignatureRequired

How A Manifest Differs From Carrier Acceptance And Delivery

A manifest is a sender-created summary. It can be electronic (EDI/API/CSV upload) or printed. Carrier acceptance occurs when the carrier physically takes custody and records that action (a scan, a signed POD, or an EDI acceptance message). Delivery is the carrier’s final scan or proof-of-delivery. All three are related but separate events: you can generate and transmit a manifest before collection, and a manifest by itself does not prove the carrier accepted every listed piece.

Document Comparison — When They Overlap And When They Are Separate

Document	Primary Purpose	When It Overlaps	When It Is Separate
Shipping Manifest	Summarize all pieces tendered to a carrier in a batch.	Overlaps with carrier acceptance summary when the carrier records acceptance against the manifest.	Separate when the manifest is generated but the carrier hasn’t yet scanned/accepted pieces.
Carrier Scan/Acceptance Summary	Carrier’s record of which items it scanned or accepted and when.	Overlaps when carrier maps acceptance to manifest line items.	Separate when carrier uses different identifiers (e.g., internal waybill numbers) or when some pieces were not scanned.
Freight Load Manifest	Describes palletized or LTL loads, often includes pallet IDs and pallet weight.	Overlaps for pallet counts and pallet-level control numbers.	Separate when pallet contents don’t match order-level picks (e.g., split pallets).
Packing List	Describes what’s inside each order/package for recipient reference.	Overlaps with manifests at SKU-level verification steps.	Separate when manifests report package-level data but not internal pack contents.
Bill Of Lading (BOL)	Legal/contract document for carriage of freight (usually LTL/FTL).	Overlaps when a BOL includes line-level package counts and is used as a manifest for freight.	Separate when parcel shipments use manifests instead of BOLs.
Shipment Labels	Piece-level shipping identifier and routing information used by carriers.	Overlaps when label tracking numbers are listed on the manifest.	Separate when labels are printed but not yet matched to an outbound batch manifest.
Customs Documents	Declare content and value for cross-border shipments.	Overlaps for international manifests that must align with customs export declarations.	Separate when domestic manifests don’t require customs paperwork.

Typical Manifest Fields You Should Include

• Sender/Shipper: Company name and billing account.
• Origin Facility: Physical location, facility ID and address.
• Carrier/Service: Carrier name and service level (e.g., Ground, LTL Standard).
• Dispatch Date: Date/time the batch is scheduled for pickup.
• Manifest ID / Batch ID: Unique identifier for the manifest upload or printed sheet.
• Order Number / Reference: Merchant order or internal reference for reconciliation.
• Package Count: Total packages and packages per order.
• Tracking Numbers / Waybills: Per-piece identifiers that carriers scan.
• Weights / Dimensions: Per-piece or pallet totals used for billing and routing.
• Exceptions / Notes: Address issues, hazardous material flags, special handling.
• Signature / Digital Handoff: Driver signature line or EDI/API acceptance token.
• Contact & Control Data: Shipper contact, receiving contact, and control checksums/QR codes.

Warehouse Workflow: From Packing To Carrier Closeout

Manifests sit inside the outbound flow that starts at pick-and-pack. Typical steps:

• Pick and Pack: Orders are picked from inventory, packed into parcels or onto pallets, and assigned package IDs or pallet IDs by the WMS.
• Label Creation: Shipping labels (and commercial invoices for exports) are printed with tracking/waybill numbers. Labels should embed a visible human-readable tracking and a machine-readable barcode/QR.
• Manifest Generation: The WMS or shipping system groups packages into a manifest (by carrier, service and pickup window) and generates an electronic or printed manifest file (CSV, API call or EDI message) to send to the carrier or to print for the driver.
• Closeout / Tendering: The manifest is transmitted to the carrier (API upload, EDI 210/856, or manual CSV/email). For many parcel carriers this triggers an expected pickup reference and allows the carrier to route the driver.
• Driver Collection / Induction: Driver arrives and either signs/initials a printed manifest or the warehouse operator scans each piece as handed to the driver. Carriers may provide an acceptance scan confirmation or an EDI acceptance message after collection.
• Carrier Acceptance Scans: The carrier’s handheld device performs the first scan (tender acceptance). That scan is the carrier’s record for that piece and is often what appears as the first tracking event.
• End-Of-Day Reconciliation: Warehouse reconciles the WMS packed list, the manifest sent, and the carrier’s acceptance scans to create an exception report for missing or mismatched items.

Common Problems And How To Investigate Them

Manifests and the physical world rarely match perfectly; here are typical issues and what to check:

• Counts Don’t Match: Manifest shows 100 labels but driver scanned 98 packages. Investigate packing logs (WMS packed count), check printed label spool for duplicates or skipped labels, and confirm driver’s acceptance list. Pull CCTV or packing station timestamps if available.
• Late Manifest Upload: If manifest upload happens after driver arrival, the carrier may not link scanned pieces to your manifest. Check API/EDI transmission logs and timestamps; resend a corrected manifest and escalate to carrier support with timestamp evidence.
• Mixed Carriers: Packages routed to different carriers but sent in one manifest confuse acceptance. Verify manifest grouping rules; separate manifests by carrier/service before tendering.
• Duplicate Labels: Duplicate tracking numbers on multiple parcels cause one scan to close multiple packages. Search for duplicate tracking in the WMS and void duplicate labels. Pull the last-known scan locations to isolate which parcel moved.
• Cancelled / Changed Orders: If an order was cancelled after label print but before pickup, it may remain on the manifest. Reconcile cancelled orders against the manifest and, if accepted by carrier, open a claim for return to sender or interception.

When A Printed Manifest Or Scan Form Matters

Some carriers accept a signed printed manifest as proof the driver picked up pieces—others rely solely on handheld scans or EDI acceptance messages. Always follow carrier-specific rules: parcel carriers often publish pickup/manifest acceptance procedures; LTL carriers rely on a signed BOL/manifest at the dock. For claims, a signed printed document plus time-stamped handoff details strengthens your position, but a manifest alone may not suffice if the carrier’s system shows missing scans.

Step-By-Step Reconciliation Procedure

Use this process daily to reconcile WMS packed orders, the manifest, and carrier first scans; it ends with an exceptions report you can act on:

• Step 1 — Export WMS Packed Orders: At closeout, export a CSV of packed orders with order number, package sequence, tracking number, weight, dimensions and pack timestamp.
• Step 2 — Export Manifest Sent To Carrier: Save the manifest file/ID you transmitted with the manifest ID, timestamp and line-level tracking numbers.
• Step 3 — Pull Carrier Acceptance/First Scans: From the carrier portal or API, request the first-scan/acceptance report for the manifest period (list of tracking numbers and timestamps for first scans or acceptance events).
• Step 4 — Automated Three-Way Match: Match rows by tracking number across WMS, manifest and carrier acceptance. Flag three categories: full match (present in all three), partial match (present in WMS + manifest but not carrier), and manifest-only (present on manifest but not in WMS).
• Step 5 — Exception Triage: For partial matches: check packing timestamps, driver proof (signed manifest), CCTV, label print spool. For manifest-only: search for label reprints or incorrect label assignment. For carrier-only: check for mispicked or returned items.
• Step 6 — Create Daily Exception Report: Document each mismatch with order number, tracking, timestamps from each system, supporting evidence (photos, CCTV, signed manifest), and proposed action (rescan, reship, claim).
• Step 7 — Escalate And Track Resolutions: Send the exception report to operations, customer service and the carrier. Track resolution and log claim numbers and final disposition in your WMS or 3PL portal.

Manifest Template — CSV Columns And Printable Example

Use this CSV header for system imports or as a minimal manifest schema. Below the header is a printable two-line example you can paste into a spreadsheet.

CSV Header:
ManifestID,BatchID,DispatchDate,OriginFacilityID,OriginAddress,Carrier,Service,OrderNumber,PackageSeq,TrackingNumber,Weight_lbs,Length_in,Width_in,Height_in,DeclaredValue,Contents,SpecialInstructions

Printable Example Row 1:
M-20261110-42,B-987,2026-11-10,FTL-001,"123 Warehouse Rd, City, ST, 12345",ExampleCourier,Ground,100523,1,EXC123456789,2.3,12,8,4,25.00,Shirt,

Printable Example Row 2:
M-20261110-42,B-987,2026-11-10,FTL-001,"123 Warehouse Rd, City, ST, 12345",ExampleCourier,Ground,100524,1,EXC123456790,5.1,18,14,6,120.00,Shoes,SignatureRequired

Sample 3PL End-Of-Day Reconciliation Checklist

• Export WMS Packed List: Save CSV with timestamps and tracking numbers.
• Save Manifest Upload/Print: Archive manifest file(s) and printed sheets with manifest ID.
• Download Carrier Acceptance Report: Include first-scan timestamps and driver-signed manifests if provided.
• Perform Three-Way Match: Identify full, partial and manifest-only matches.
• Identify Exceptions: Log missing scans, duplicates, cancelled orders and mixed-carrier items.
• Gather Evidence: Attach label spool, packing photos, CCTV clips, and signed pick-up sheets.
• File Claims/Escalations: For accepted-but-missing or not-accepted-but-tendered items, open carrier ticket with evidence and reference manifest ID.
• Communicate To Customers: Inform customer service of orders impacted and planned remediation (reship, refund).
• Archive Records: Keep manifest, WMS export and acceptance report for the carrier’s claims window (per carrier SLA).

Practical Three-Way Example And Investigation Steps

Hypothetical: 120 parcels were printed and labeled. The printed carrier collection sheet (manifest physical copy) shows 119 recorded by the driver at pickup. Carrier first-scan data later shows 118 first scans.

Investigation steps (no assumptions which parcel is at fault):

• Step A — Reconcile Label Spool: Confirm 120 unique tracking numbers were printed and assigned in WMS; check for duplicate or skipped sequences.
• Step B — Compare Manifest To WMS: Find which tracking number is missing from the manifest (120 WMS vs 119 manifest). That missing tracking could indicate a label printed but not included on the manifest sent to the carrier.
• Step C — Compare Manifest To Carrier Scans: Identify the tracking number present on manifest but missing in carrier first-scan list (the one that makes 119->118). That parcel may have been recorded by the driver on paper but not scanned by the handheld, or the carrier's system failed to accept it.
• Step D — Physical Traceback: Ask the warehouse to check packing station logs/CCTV around the pack timestamp for the missing tracking numbers; confirm whether both parcels were physically handed to the driver.
• Step E — Driver Signed Sheet: If the driver signed a physical manifest or pickup sheet, check which tracking numbers were circled or written; this can show which pieces the driver acknowledges taking.
• Step F — Carrier Escalation: For the item on manifest but not in carrier scans, escalate to the carrier with manifest ID, driver signed sheet photo and timestamps. For item printed but not on manifest, determine whether it was withheld or accidentally excluded and re-present to carrier if necessary.

FAQs

Is a shipping manifest the same as a bill of lading? No. A shipping manifest is a batch-level list of pieces tendered to a carrier; a bill of lading (BOL) is a contractual and legal carriage document commonly used for freight (LTL/FTL). They overlap when a BOL carries line-item counts, but they are different documents with different legal roles.

Does a manifest mean my package was shipped? Not by itself. A manifest shows the shipper intended to tender those packages and that they were included in a pick-up batch. The carrier’s acceptance scan or signed pickup record is what the carrier uses to confirm actual tendering. Always verify carrier first-scan events or signed driver paperwork.

What is a carrier acceptance scan form? It is the carrier-generated record (electronic or printed) that documents which items the carrier scanned or accepted at pickup/induction. For parcel carriers, this appears as the first tracking event (e.g., "Accepted at Pickup"); for freight, it is usually the signed bill of lading or the carrier's load manifest.

What if a manifest and tracking scans disagree? Run a three-way match: WMS packed list vs manifest sent vs carrier acceptance scans. Collect evidence (label spool, packing photos, signed manifests, CCTV, API logs) and present to the carrier if their scans are missing items listed on the manifest. Create an exception record in your system while the carrier investigates.

In short, the Shipping Manifest is the shipper’s organized batch record of what was tendered to a carrier; it supports routing, billing and reconciliation but does not replace the carrier’s acceptance scan or signed pickup record. The next operational step is to implement the three-way daily reconciliation above (WMS export, manifest archive, carrier acceptance pull) and add the exception checklist to your closeout routine so mismatches are detected and resolved before customer impact.