When should delivery tracking software notify the consignee?
Key Takeaways
Wilson, by Cartage, tracks shipments, obtains an updated ETA and reason when a load is late, and notifies the people configured for that shipment. The receiving team also needs a clear next action when the changed arrival no longer fits its plan.
- Use the correct inbound load and receiving contact.
- Label the milestone, source, time zone and uncertainty.
- Keep carrier expectation separate from a facility-approved appointment.
- Ask receiving whether the new plan works.
- Escalate decisions outside the customer’s rules.
What does receiving need to know?
Shipment tracking software should help receiving understand the delivery impact. A general alert saying “late” may not tell the team whether to keep staff available, change a slot or request another update.
Name the shipment and destination milestone. Arrival near a terminal is different from arrival at the facility. An estimate is different from a confirmed appointment or completed delivery.
If a carrier response is still missing, say so. A useful early warning can identify risk without presenting an unverified plan as certain.
What should a useful update contain?
Keep the message short but complete enough for the receiving decision. The following fields are a buyer framework, not a required message template for every customer.
| Field | Example content | Purpose |
|---|---|---|
| Shipment | Order and load reference | Identifies the right freight |
| Milestone | Expected arrival at the receiving facility | Avoids mixing transport stages |
| Current time | ETA with time zone and source | Shows the supported expectation |
| Appointment | Original or newly accepted slot | Clarifies the facility commitment |
| Next action | Receiving response or carrier follow-up | Keeps ownership clear |
| Next update | Agreed check time where configured | Avoids an open-ended wait |
Use the contacts configured for that order and role. A broad distribution list can send irrelevant or confusing messages to the wrong people.
How does Wilson obtain the current status?
Wilson uses the best source available for the load: carrier API, GPS or ELD data, or the carrier’s website by PRO number. Where those are unavailable, it emails or calls the carrier.
When the load is late, Wilson gets the new ETA and reason, then notifies the configured recipients. It can contact drivers directly when the carrier shares driver contact information.
Keep the source and update time visible in the workflow. A current carrier statement should not be confused with an old portal event or a forecast for another stop.
Who changes the receiving appointment?
The facility owns its receiving capacity and dock-slot process. Wilson coordinates pickup and delivery times with carriers; managing dock slots inside a facility is not a current capability.
Ask receiving whether it accepts the revised arrival or needs another appointment. Then communicate the agreed instruction to the carrier. A proposed slot remains proposed until the relevant parties accept it.
If the change creates extra cost or a service decision outside authority, send it to the responsible person. A delay notification alone is not permission to make any replacement arrangement.
What happens if the carrier does not answer?
Keep the risk open and continue the configured follow-up. The team needs an owner and next check, especially when the original receiving window is approaching.
Wilson follows the customer’s escalation rules. Supply the after-hours contacts and decision boundaries needed for your operation. Do not assume every receiver has the same availability.
Keep product-quality, inventory allocation and customer priority decisions with their designated owners. Shipment tracking software provides transport information and follow-up; it does not automatically decide every business consequence.
What should the inbound-delay demo prove?
Bring a shipment with a changed ETA and a receiver that cannot accept the new time. Ask Cartage to show the carrier update, receiving notification, response ownership and revised plan.
Measure time to the first useful action and to an accepted plan. A quick alert is useful, but it does not prove the delay has been resolved. Show cases still waiting for an answer.
The ETA communication guide explains the evidence boundary. The useful result is an informed receiving team and an owned next action.
FAQs
Can Wilson notify the receiving team when a load is late?
Yes. Notifications follow the contacts and rules configured for that shipment, using the available tracking information and carrier follow-up.
Does a new ETA change the appointment automatically?
No. A carrier estimate and a facility-approved appointment are different. Confirm the receiving response.
Does Wilson manage dock slots?
Not today. It coordinates carrier-side times while the facility owns its dock-slot process.
What if the arrival remains unconfirmed?
Send a qualified risk update when the rules call for it, keep follow-up open and identify the owner and next check.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai