Why do delivery dates in Qargo sometimes differ from expected or external system dates?
Delivery dates in Qargo can sometimes differ from expected dates or those shown in external systems due to various factors, including how dates are calculated, propagated, or interpreted across systems. Below, we explain the key scenarios and principles that can lead to these discrepancies.
Overview of Date Filters in Qargo
Qargo uses a system of date filters to manage and display delivery dates. These dates can be influenced by:
The last stop date among trips associated with an order.
The method used to update dates within Qargo.
Differences in date calculation logic between Qargo and external systems.- Lead time defined in service levels, which can shift stop dates. Adjusting these settings ensures order dates align with intended schedules.
Common Scenarios of Date Discrepancies
Filtering Logic and Overlapping Timestamps
When filtering by a specific date, Qargo may display orders with a different "main" date. This occurs because the filter considers timestamps related to trips, such as estimated or planned times, or stops overlapping the selected date. If any part of a trip aligns with the chosen date, it may appear even if the displayed order date differs.
Differences Between Scheduled and Actual Dates
Discrepancies can occur when hours are imported from telematics systems. The "start date" reflects when the job or activity was originally scheduled, while the "actual date" updates to when the driver completed the work. Late data transmission from telematics systems may result in earlier start dates but actual completion dates corresponding to when the driver finalized the work.
Invoice Delivery Dates Reflecting Later Stop Dates
In Qargo, the delivery date shown on an invoice is derived from the last stop date among the trips associated with the order. If any stop in the associated trips has a later date than the order’s delivery date, the invoice will reflect that later "last stop" date.
To verify this:
Open the order in Qargo.
Review all linked trips.
Check the dates of each stop to identify the latest stop date, which will be used on the invoice.
Date Propagation When Updating Stops
When updating dates in Qargo, the propagation of changes depends on the method used:
Order Detail Page (Edit Flow): - Propagation occurs only when there is a single, consistent offset across the edited dates. - For example, if you change the pickup date by +1 day and the delivery date by +4 days, no automatic propagation will occur. However, if the offset is consistent (e.g., both pickup and delivery are changed by +2 days), the system will propagate this offset to other stops.
List Page (Date Edit Modal): - Dates are updated per stop, and each change immediately establishes a clear, consistent offset that is propagated to other stops. Subsequent updates to another stop will not overwrite the first propagation.
To ensure correct propagation, either apply a single consistent offset in the order detail edit flow or use the list view’s date edit modal.
Cross-System Date Discrepancies
Delivery dates may differ between Qargo and external systems (e.g., Alliance) due to differences in how dates are calculated. For example, some networks calculate delivery dates based on:
Manifest Date: The date freight is handed over to the network.
Service Level: Determines transit time (e.g., Economy = 2 working days).
In such cases, the external system may calculate a delivery date based on the manifest date and service level, while Qargo displays the planned delivery date. This can lead to discrepancies between the two systems.
Conclusion
Understanding how Qargo calculates and propagates delivery dates, as well as recognising differences in external systems, can help identify and resolve date discrepancies. By reviewing associated trips, applying consistent offsets, and considering external system logic, ensure accurate and consistent delivery date management.
Troubleshooting Steps for Date-Related Issues
Review Service Level Settings: Check lead time settings in service levels to ensure they align with scheduling needs.
Understand Date Fields: Familiarise yourself with differences between scheduled and actual dates, especially when using telematics systems.
Analyse Filtering Results: Consider all timestamps and overlapping events when filtering by a specific date to avoid unexpected results.