FAQs: Truckload Shipment Tracking
We will attempt to locate the truck 90 minutes before appointment window start time (this 90-minute window can be configured per tenant as well).
Tracking will stop when one of the 3 below scenarios occurs:
-
Truck arrives and departs final stop geofence.
-
Truck arrives and stays at final stop geofence for 3 hours (number of hours is configurable)
-
No tracking information is received for 48 hours after the final stop appointment window (number of hours is configurable).
-
Carrier has not entered an update into their system of record.
-
Driver could be on break/truck is off.
-
Change in truck.
-
ELD malfunction
-
The driver’s phone is off or doesn’t have service.
-
Driver disabled location services.
-
Driver opted out of tracking or deleted the app.
Potential Reason 1: There is an issue with the ELD provider’s system.
Solution: Contact the ELD provider for support.
Potential Reason 2: There is an issue with the project44 system.
Solution: Contact project44 support.
This depends on tracking method. project44 attempts to get at least 15-minute tracking updates, and we will not prevent anyone from sending in updates more frequently.
A lot of components go into the ETA algorithm: the driver’s hours of service, historic and real traffic, historic and real weather, lane data, mechanical issues, fuel stops, and driving bans (only if in the EU). ETA is only provided when a status update is received. If the vehicle does not move, we sometimes do not get a status update. Updates are highly variable based on the data source.
Not by default. This setting can be enabled, if your location hours are populated, for the location hours to be to be considered when determining ETA.
Each tenant can be configured to utilize a default stop dwell. Individual location dwell times are being considered as a future enhancement.
Both options are available. For more information on setting up a webhook to get PUSH notifications about shipment tracking status, click here.
If utilizing the GET Tracking status API to PULL status updates, use either:
There are two different APIs available to retrieve status updates. You can either utilize the project44 ID (see GET: Get status of truckload shipment by unique system id) or utilize your BOL or order number (see GET: Get status of a truckload shipment by shipment identifier).
A push will occur if any of these 3 conditions are met:
-
Timestamp changes
-
Shipment location changes
-
Shipment status changes
No, only the current status and past two historical updates will be PUSHed.
Why are certain locations (e.g. Distribution Centers, Facilities) not tracking for a particular carrier?
There are a few potential reasons why certain locations are not tracking for a particular carrier:
Potential Reason 1: Carrier has not turned on certain “Bill-to” codes or Shipper ID’s that are associated with the account.
Solution: Confirm with your Carrier Account Rep that their Shipper IDs are “turned” on to send to project44. If you provided BOLs during the implementation phase, project44 can work with you to send over BOL examples to the carrier account rep to ensure all “Bill-to” codes are turned on. Ensure the certain location (e.g., Distribution centers, Facilities) is passing along the mutually decided shipment ID that will be used for tracking.
Potential Reason 2: Customer has initiated tracking after the pick-up occurred and the system will not track that shipment if initiation was “late.”
Solution: Initiate shipment with project44.
Potential Reason 3: Customer has not initiated shipment to project44.
Solution: Initiate shipment to project44.
Potential Reason 4: Address is not in HEREMaps System.
Solution: Submit support ticket to have address added to HEREMaps System.
Potential Reason: Carrier is doing drop-trailer shipments.
Solution: Because Carriers who joined the project44 network via their ELD are being tracked by ELD, the shipment must remain with the power unit to track properly. If a shipment suddenly changes direction or ceases tracking, it is most likely due to the Carrier doing drop trailer shipments. If a Carrier is doing drop trailer shipments, you need to be sure to receive all Truck #s at the beginning of the shipment and update the Truck #s for tracking to continue.
No. In order to receive all tracking updates, a webhook must be configured. Email notifications are reserved for specific events only.
We show “picked up” when the shipment departs the origin geo-fence and “delivered” when the shipment enters the destination geofence in VOC.
There are a few potential reasons why a shipment loses tracking:
-
Shipment identifier mismatch
-
Carrier has not entered an update into their system of record
-
Carrier has a connection issue with data feed coming to project44
-
Incorrect vehicle ID
-
Truck not on
-
ELD malfunction
-
ELD not sending data to project44 correctly
-
Driver has not accepted tracking/downloaded the app
-
Driver does not have location services turned on
-
Driver's phone is off/no service
Potential Reasons:
-
There is an issue with the project44 system.
-
The webhook was set up incorrectly – this would explain seeing shipment information in the VOC and not in TMS.
Solution: For either of these situations, escalate the issue to project44 for support.
Potential Reason: The carrier has not turned on certain “Bill-to” codes (shipper IDs that are associated with the account) or carrier is sending the wrong identifier.
Solution:
-
Review initial communication to carrier to see if the carrier got the correct shipment ID.
-
Resend appropriate shipment ID to the carrier.
-
Have project44 discuss the situation with carrier.
There are a couple reasons for why you did not receive arrival or departure information at the Origin:
-
The load could have been sent to project44 after truck left the origin (no departure information)
-
Tracking could have started once the truck was already at the origin (no arrival information)