Shipping Manifests

Shipping Manifests consolidate multiple shipping orders into unified Bill of Lading documents for carrier pickup and freight management. The system groups shipments by destination, carrier, or pickup date while generating standardized shipping documentation that includes packing lists, weight totals, and piece counts for commercial transportation.

Shipping manifests integrate with shipping order management, carrier coordination, freight billing, and warehouse shipping operations to streamline outbound logistics and ensure accurate shipping documentation.

Access: Shipping → Shipping Manifests (Report Type 106)

Understanding Shipping Manifests

Shipping manifests serve as master shipping documents grouping related shipping orders for pickup by common carriers. They provide consolidated packing information, weight calculations, and piece counts required for freight bills of lading while maintaining individual shipping order detail for customer delivery and invoicing.

Screen Components:

• Manifest List: Grid of created manifests with dates and shipment counts
• Manifest Header: Carrier, pickup date, total weight, total pieces
• Manifest Lines Grid: Individual shipping orders included in manifest
• SO Reference Links: Click-through to underlying shipping order details
• Print Function: Generate Bill of Lading PDF or thermal label
• Status Indicators: Open, printed, picked up, or closed manifests
• Search/Filter: Locate manifests by SO number, date, or carrier

Key Operations:

• Group Shipments: Combine multiple SOs destined for same carrier/route
• Consolidate Documentation: Single BOL for multiple shipments
• Calculate Totals: Aggregate weight, pieces, and cube across all SOs
• Generate BOL: Print carrier-ready Bill of Lading with manifest details
• Track Pickups: Monitor manifest status through shipping cycle
• Freight Reconciliation: Use manifests for carrier invoice validation

Manifest Workflow:

1. Shipping orders created and ready for shipment
2. Warehouse picks and packs individual orders
3. Shipping coordinator groups SOs by carrier/route/date
4. Manifest created with selected shipping orders
5. System calculates total weight, pieces, cube
6. Bill of Lading generated with manifest number
7. BOL provided to carrier at pickup
8. Manifest marked as picked up after carrier departs
9. Freight bill validated against manifest totals
10. Manifest archived as shipping documentation

Manifest Header Fields

Manifests consist of header information describing the shipment grouping and line items listing individual shipping orders included.

Manifest Header:

Field Notes:

• Manifest Number: Auto-incremented identifier for tracking and reference
• Carrier: Helps group shipments by transportation method or carrier account
• Calculated Totals: Dynamically update as SOs added/removed from manifest
• BOL Number: Some carriers provide BOL numbers in advance for electronic integration
• Status: Tracks manifest through shipping lifecycle

Manifest Line Items

Each manifest line represents a shipping order included in the consolidated shipment. Lines provide drill-down to SO details while manifesting for carrier documentation.

Line Item Fields:

Field Notes:

• Shipping Order: Links manifest line to source SO for detailed packing list
• Customer/Ship To: Displayed for verification, ensures correct grouping
• Weight/Pieces/Cube: Roll up to manifest header totals
• PO/Reference: Customer identifier for delivery confirmation

Creating Shipping Manifests

Group multiple shipping orders into consolidated shipments for common carrier pickup, generating unified Bills of Lading with aggregate totals.

Required:

• Security ID 127 (Shipping Manifests access)
• Existing shipping orders ready for shipment
• SOs not already on other manifests
• Optional: Carrier information

When to Create Manifests:

• Multiple shipments to same region/carrier on same day
• LTL (Less Than Truckload) consolidation for freight savings
• Daily pickup scheduled with carrier requiring BOL
• Cross-dock operations grouping inbound to outbound shipments
• Multi-stop routes with single carrier
• End-of-day manifest for all shipments picked up

When NOT to Create Manifests:

• Single shipping order pickups (use SO documentation directly)
• Parcel shipments with integrated carrier systems (UPS/FedEx small package)
• Customer pickups not requiring BOL
• Drop-ship orders bypassing warehouse

Workflow:

1. Navigate to Shipping → Shipping Manifests
2. Click Create Manifest or New Manifest button
3. Manifest Header Entry:
   • Manifest Date: Select pickup date (defaults to today)
   • Carrier: Choose transportation company (optional)
   • BOL Number: Enter if carrier-provided (optional)
   • Notes: Add special instructions or routing details
4. Click Save to create manifest header
5. System assigns manifest number
6. Navigate to Lines or Add Shipping Orders
7. Select Shipping Orders:
   • Browse available SOs (typically filtered to ready-to-ship status)
   • Multi-select SOs for same carrier/route/pickup
   • Verify customers and destinations compatible for consolidation
   • Check SOs not already manifested
8. Click Add Selected or Add to Manifest
9. System adds SO lines to manifest
10. Review totals automatically calculated:
    • Total Weight = sum of all SO weights
    • Total Pieces = sum of all SO package counts
    • Total Cube = sum of all SO volumes (if tracked)
11. Verify manifest contents accurate
12. Print Bill of Lading for carrier
13. Provide BOL to driver at pickup
14. Mark manifest as Picked Up after carrier departure

What Happens:

• Manifest record created in BillOfLading table
• Manifest number auto-generated (sequential or configurable format)
• Selected SOs linked to manifest (cannot be added to multiple manifests)
• Totals calculated dynamically from SO data
• Status set to “Open” initially
• Manifest available for BOL printing
• SOs marked as manifested (prevents duplicate manifesting)

Manifest Grouping Strategies:

• By Carrier: All FedEx shipments on one manifest, all UPS on another
• By Route: Group destinations along same delivery route
• By Pickup Time: Morning pickup vs afternoon pickup manifests
• By Service Level: Standard freight vs expedited service
• By Customer: Large customers with multiple daily shipments
• By Warehouse Zone: Group by pick zone for staging efficiency

Managing Manifest Lines

Add or remove shipping orders from manifests to adjust consolidated shipments before carrier pickup and BOL finalization.

Required:

• Security ID 127 (Shipping Manifests access)
• Existing manifest (header created)
• Available shipping orders to add

When to Manage Lines:

• Late-arriving orders need addition to scheduled pickup
• Order cancellations require removal from manifest
• Rerouting shipments to different carriers
• Correcting manifest errors (wrong SO added)
• Splitting large manifests for carrier capacity limits
• Combining manifests to consolidate pickups

Workflow:

1. Navigate to Shipping → Shipping Manifests
2. Locate and select manifest to modify
3. Click Lines or Edit Lines button
4. Grid displays current shipping orders on manifest
5. Add Shipping Orders:
   • Click Add SOs or Add to Manifest button
   • System displays available SOs (not already manifested)
   • Filter by status, customer, carrier, or date as needed
   • Select SOs to add via checkboxes
   • Click Add Selected
   • New SOs appear in manifest lines grid
   • Totals recalculate automatically
6. Remove Shipping Orders:
   • Locate SO in manifest lines grid
   • Click Remove or delete icon
   • Confirm removal
   • SO removed from manifest (returns to available SOs)
   • Totals recalculate excluding removed SO
7. Reorder Lines:
   • Some systems allow line reordering for BOL print sequence
   • Drag-and-drop or up/down arrows if available
   • Sequence may affect BOL document layout
8. Review updated manifest totals
9. Save changes if not auto-saved
10. Reprint BOL if already printed and changes made

What Happens:

• Adding SO: Links SO to manifest, updates SO status to “manifested”
• Removing SO: Unlinks SO from manifest, reverts SO to “ready to ship”
• Totals recalculated: Weight, pieces, cube updated with each change
• BOL outdated: Previously printed BOLs invalid after line changes
• Audit trail: Changes logged with user and timestamp

Line Management Rules:

• Cannot add SO already on another manifest (must remove from first manifest)
• Cannot add SO not in “ready to ship” or similar status
• Cannot modify manifest after marked “Picked Up” (typically locked)
• Removing last SO from manifest may delete manifest (empty manifest handling varies)

Printing Bill of Lading

Generate carrier-ready Bills of Lading with manifest details, totals, and shipping order line items for freight documentation.

Required:

• Security ID 127 (Shipping Manifests access)
• Manifest with at least one shipping order
• Printer or PDF capability
• Report configuration for BOL format

When to Print BOL:

• Before carrier pickup (provide to driver)
• After manifest finalization (no more changes expected)
• For freight audit documentation
• Customer requests for shipment proof
• Carrier requires advance electronic submission
• Internal shipping documentation file

Workflow:

1. Navigate to Shipping → Shipping Manifests
2. Locate and select manifest for BOL printing
3. Click Print or Print Bill of Lading button
4. System generates BOL report using configured template
5. BOL Content:
   • Manifest Header: Manifest number, date, carrier
   • Shipper Information: Warehouse/company name and address
   • Totals Section: Total weight, pieces, cube
   • Line Item Details: Each SO with customer, ship-to, weight, pieces
   • Special Instructions: Notes from manifest or SOs
   • Signatures: Shipper signature line, carrier signature line
6. Review BOL for accuracy
7. Print Options:
   • Printer: Send to thermal label or laser printer
   • PDF: Generate PDF for email or electronic submission
   • Copies: Print multiple copies (shipper, carrier, file)
8. Provide BOL to carrier driver at pickup
9. Obtain driver signature on shipper’s copy
10. File signed BOL for shipping records
11. Mark manifest as Printed status if tracked

What Happens:

• Report execution queries manifest header and lines
• Stored procedure rpt_manifest_header retrieves manifest data
• Stored procedure rpt_manifest_content retrieves line item details
• PDF generated using configured BOL template
• Manifest status may update to “Printed” (prevents inadvertent changes)
• Print event logged for audit trail

BOL Format Components:

• Header Section: Shipper, consignee, manifest number, date
• Totals Block: Weight (lbs or kg), pieces, cube, value if insured
• Line Item Grid: SO number, customer, destination, weight, pieces per SO
• Terms and Conditions: Carrier liability, special handling instructions
• Signature Blocks: Shipper certifies contents, carrier acknowledges receipt
• Barcode: Manifest number or BOL number for scanning (optional)

BOL Copies Distribution:

• Original: Carrier (travels with freight)
• Shipper Copy: File with signed acknowledgment
• Accounting Copy: Freight audit and billing reconciliation
• Customer Copy: Proof of shipment if requested

Tracking Shipping Manifests

Monitor created manifests, pickup status, and shipment groupings through filterable list views and status tracking.

Required:

• Security ID 127 (Shipping Manifests access)
• Existing manifests in system

Status Categories:

1. Open: Manifests created but not yet finalized or picked up
2. Printed: BOL generated, awaiting pickup
3. Picked Up: Carrier departed with shipment
4. Closed: Manifests archived after freight billing reconciled
5. All: Complete manifest history

Tracking Workflow:

1. Navigate to Shipping → Shipping Manifests
2. Grid displays manifests with key information:
   • Manifest number
   • Manifest date
   • Carrier
   • Total weight/pieces
   • Status
   • Number of SOs on manifest
3. Filter Manifests:
   • By Date Range: Manifests created in specific period
   • By Carrier: Filter to specific transportation company
   • By Status: Open, Printed, Picked Up, Closed
   • By SO Number: Find manifest containing specific shipping order
4. Click manifest to view details
5. Manifest Detail View:
   • Header information (date, carrier, totals)
   • Line items (all SOs on manifest)
   • Links to individual SO details
   • Print BOL option
   • Edit/Delete options (if open status)
6. Update Status:
   • Mark as Picked Up after carrier departure
   • Mark as Closed after freight billing complete
   • Status updates may be automatic based on workflows

Manifest Research:

• Find SO: Search by SO number to locate containing manifest
• Freight Audit: Compare manifest totals to carrier invoice
• Pickup Verification: Confirm all manifests picked up on scheduled date
• Carrier Performance: Track pickup timeliness by carrier
• Volume Analysis: Review shipment volumes and consolidation rates

Use Cases:

• Daily Pickup Tracking: Monitor today’s manifests for carrier coordination
• Freight Reconciliation: Match carrier invoices to manifests
• Customer Inquiries: Trace shipment by finding SO on manifest
• Documentation Retrieval: Reprint BOL for lost/damaged freight claims
• Performance Metrics: Analyze consolidation efficiency and freight costs

Validation and Business Rules

Manifest Header Rules

• Manifest number auto-generated (cannot manually specify)
• Manifest date required (defaults to current date)
• Carrier optional but recommended for routing and reporting
• Totals calculated dynamically from manifest lines (read-only)
• Status managed by system based on actions (not manually set)

Manifest Line Rules

• Each SO can appear on only one manifest at a time
• SOs must be in appropriate status (ready to ship, picked, etc.)
• Cannot add canceled or completed SOs to manifests
• Removing SO from manifest returns it to available pool
• Line numbers auto-assigned sequentially

Printing Rules

• BOL can be reprinted any number of times
• Recommend reprinting after line item changes
• BOL layout configured via report template (system-wide setting)
• Signature capture not supported in digital BOL (manual process)

Status Transition Rules

• Open → Printed: After first BOL print (optional status)
• Printed → Picked Up: Manual update after carrier departure
• Picked Up → Closed: After freight billing reconciliation
• Cannot revert status (e.g., Picked Up back to Open)

Total Calculation Rules

• Total Weight = SUM(SO weights) from all manifest lines
• Total Pieces = SUM(SO package counts) from all manifest lines
• Total Cube = SUM(SO volumes) if dimensional data tracked
• Totals recalculate immediately when lines added/removed
• Null/zero values in SO data default to zero in totals

Deletion Rules

• Can delete manifests in Open status (not picked up)
• Deleting manifest unlinks all SOs (returns to available pool)
• Cannot delete manifests after Picked Up (retain for audit)
• Recommend marking Canceled instead of deleting

Admin Options

Configuration Notes:

• Security ID 127: Required for manifest operations, separate from shipping order permissions
• Report Type 106: Configures columns, filters, and sorting for manifest list

Permission Granularity:

• View Manifests: Read-only access to manifest list and details
• Create/Modify Manifests: Add new manifests and manage lines
• Print BOL: Generate Bill of Lading documents
• Delete Manifests: Remove open manifests (typically restricted)

BOL Template Configuration:

• BOL format defined in report configuration (Crystal Reports or similar)
• Template references manifest header and content stored procedures
• Customizable for carrier-specific requirements or branding
• Barcode inclusion optional based on template design

Integration Settings:

• Manifest data available for EDI transmission to carriers
• API endpoints may provide manifest creation/retrieval for external systems
• Carrier integration modules use manifest data for electronic BOL submission
• Freight audit systems import manifest totals for invoice matching

Best Practices

Strategic Manifest Consolidation. Analyze shipping patterns to identify optimal consolidation opportunities balancing freight savings against shipment complexity. Group shipments by carrier to maximize volume discounts and reduce pickup frequency charges. Consider geographic routing for multi-stop deliveries ensuring logical delivery sequences. Evaluate service level requirements avoiding consolidation of time-sensitive with standard shipments. Use freight class and commodity codes to ensure compatible goods on same manifest preventing carrier surcharges. Monitor minimum charge thresholds using manifests to meet carrier minimums for favorable rates. Coordinate manifest creation timing with carrier pickup schedules avoiding last-minute additions that delay departures.

Documentation Accuracy and Compliance. Verify all manifest totals match actual shipment weights and piece counts before BOL generation preventing freight audit discrepancies. Review shipping addresses and customer information for accuracy ensuring proper delivery routing. Include special handling instructions and hazmat declarations where applicable maintaining compliance with transportation regulations. Capture carrier driver signatures on shipper copy providing proof of pickup for claims and disputes. Maintain BOL copies for required retention period supporting freight audits and customer inquiries. Cross-reference manifest numbers with freight invoices during payment processing catching billing errors. Use consistent BOL numbering aligned with manifest numbers simplifying traceability and reconciliation.

Operational Efficiency Integration. Integrate manifest creation with warehouse pick and pack workflows coordinating staging areas by manifest groupings. Use manifest line items to generate consolidated packing lists reducing documentation per individual shipping order. Schedule manifest finalization deadlines aligned with carrier pickup windows ensuring BOL availability for drivers. Train warehouse staff on manifest procedures including how to identify and stage manifested shipments. Implement manifest status tracking visible to customer service enabling accurate shipment inquiries. Automate manifest totals validation alerting to weight or piece count discrepancies requiring verification. Establish manifest correction procedures for handling late changes or errors discovered after BOL printing. Monitor manifest utilization rates identifying under-utilized manifests or opportunities for additional consolidation.

Troubleshooting

Issue: Cannot add SO to manifest - already manifested error

Problem: Attempting to add shipping order results in error indicating SO already on manifest. Solution: Search manifests for SO number to locate existing manifest. Remove SO from current manifest if incorrectly assigned. Verify SO not on multiple manifests due to data error (should be prevented by system). If SO must move to different manifest, remove from first then add to second. Prevention: Check SO manifest status before attempting to add to new manifest. Implement workflow that clears manifest assignment when SO canceled or rerouted.

Issue: Manifest totals incorrect or not calculating

Problem: Total weight or pieces don’t match sum of manifest lines. Solution: Verify all SO data complete (weight and piece counts populated). Check for null values in SO fields causing calculation errors. Refresh manifest page to trigger recalculation. Review if custom modifications affecting total calculation logic. Query database directly to compare manifest table totals vs calculated sums from line items. Prevention: Enforce weight and piece count entry during shipping order creation. Implement data validation preventing null values in critical fields.

Issue: BOL not printing or blank document generated

Problem: Print function executes but no output or blank PDF generated. Solution: Verify manifest contains at least one SO line (empty manifests may fail BOL generation). Check report server configuration and template availability. Review stored procedures rpt_manifest_header and rpt_manifest_content execute without errors. Test with different manifest to isolate data vs system issue. Check printer connectivity and driver if printing to physical device. Prevention: Implement validation preventing BOL print of empty manifests. Monitor report server health and template file integrity.

Issue: Cannot remove SO from manifest - modification denied

Problem: Attempting to remove SO from manifest fails or option unavailable. Solution: Check manifest status (may be locked after Picked Up status). Verify user has modify permissions for manifests. Confirm not attempting removal via read-only view. Review if SO already shipped (may prevent manifest modification). Check for concurrent user editing causing lock. Prevention: Complete manifest modifications before marking Picked Up. Communicate manifest finalization to prevent late changes.

Issue: Duplicate manifest numbers or numbering gaps

Problem: Manifest numbering not sequential or duplicates exist. Solution: Review manifest number generation logic (auto-increment sequence). Check for concurrent manifest creation causing number conflicts. Verify database sequence or identity column functioning correctly. Investigate if manual number entry allowed and causing duplicates. Re-seed sequence if gaps result from deleted manifests. Prevention: Use auto-increment exclusively preventing manual number entry. Implement unique constraint on manifest number preventing duplicates.

Issue: Carrier pickup but manifest still shows Open status

Problem: Physical pickup occurred but status not updated in system. Solution: Manually update manifest status to Picked Up. Train shipping staff on status update procedures. Implement workflow checklist ensuring status update at pickup. Review if automatic status update failed due to integration error. Check audit log for failed update attempts. Prevention: Establish end-of-day manifest status reconciliation. Implement pickup confirmation workflow with status update requirement.

Issue: Freight invoice doesn’t match manifest totals

Problem: Carrier billing shows different weight or piece counts than BOL. Solution: Compare BOL copy to freight invoice line-by-line. Check if carrier reweighed shipment finding discrepancies. Verify all SOs on manifest match carrier pickup documentation. Review if late additions to manifest not reflected on driver’s BOL. Investigate carrier data entry errors in billing system. Dispute invoice with supporting BOL documentation if manifest correct. Prevention: Verify shipment weights using certified scales before manifesting. Obtain driver signature on BOL with weight attestation. Implement freight audit process comparing all invoices to manifests.

Key Reports

Manifest Analytics: Track consolidation rate (average SOs per manifest) measuring freight efficiency. Monitor manifest creation to pickup time identifying bottlenecks in shipping processes. Calculate cost per manifest analyzing carrier charges relative to shipment volume. Review carrier utilization by manifest count optimizing carrier relationship mix. Analyze regional consolidation opportunities identifying underserved routes or geographic clusters. Measure BOL accuracy rate comparing manifest totals to carrier invoices spotting systemic issues.

Related Topics

• Shipping Orders - SO creation and management feeding manifest consolidation processes
• Receiving - Inbound documentation parallel to outbound manifesting for complete logistics tracking
• Warehouse Operations - Pick, pack, and ship workflows coordinating with manifest creation
• Carrier Management - Carrier setup and rate management supporting manifest carrier selection
• Freight Audit - Invoice reconciliation using manifest documentation for payment validation