Troubleshooting missing shipments in Maven Dispatch

overview

Use this article when a shipment does not appear in Maven Dispatch where you expect it.

Confirm the shipment is really missing

1. Search by shipment ID or reference number.

2. Clear or reset all filters (date, terminal, status, tags).

3. Check both:

   • Inbound/unassigned views

   • Active routes and stops

Only treat it as missing after you confirm it does not appear anywhere.

Look for the shipment in inbound or unassigned views

1. Open the inbound or unassigned shipments view.

2. Filter by:

   • The correct operating date

   • The correct terminal or service area

3. Scan for the shipment ID or customer.

If you find it here, assign it to the correct route and proceed with normal dispatch.

Check for the shipment on another route, date, or terminal

1. Remove terminal and date filters temporarily.

2. Search for the shipment ID again.

3. Open any matching routes or stops and confirm:

   • The date

   • The terminal

   • The driver and status

Confirm upstream creation

If the shipment still does not appear:

1. Verify that planning, TMS, or import tools created the shipment.

2. Check for confirmation numbers or logs in upstream systems.

3. Compare expected shipment data (ID, date, terminal, customer) with what those systems actually show.

If upstream never created the shipment, treat it as an upstream issue, not a Dispatch problem.

Escalate recurring missing‑shipment issues

When missing shipments become a pattern:

1. Collect examples that include:

   • Shipment ID or reference

   • Intended date and terminal

   • Screenshots from Dispatch and upstream systems

2. Send the examples to your internal data or integration owner.

3. Track follow‑up so you can confirm when the issue no longer occurs.

Do not hide recurring issues with repeated manual fixes; get the root cause corrected.