Skip to main content
All CollectionsResourcesQargo mobile app
FMS / Mobile App Stop updates: Cut off configuration
FMS / Mobile App Stop updates: Cut off configuration

It is possible to configure how early or late updates entered by a driver are handled, when related to a stop.

Arynne Hargreaves avatar
Written by Arynne Hargreaves
Updated over a week ago

It is now possible to configure the Qargo Mobile App or a similar Fleet Management System (FMS) integration that would update stop times, with how the cutoff time is handled.

In the 'Use planned times' section, it is possible to configure how the updates are handled, depending on when the driver performs the update. This cut-off window helps to account for stops being updated early or late, which then impacts visibility on the planning board.

  • Enable start timestamp correction: This toggle can be used to enable or disable the start timestamp correction.

    • If it’s enabled, the user can choose the threshold in the amount of hours difference that needs to be between the start timestamp of the stop in Qargo and the actual start timestamp update coming from the FMS, for the correction logic to trigger. The default is 8 hours.

    • Example: so if you planned a stop on 13:00 PM and you get an update from the FMS that tries to set the start timestamp to 22:00 PM (+9h), the correction logic will determine this a faulty update and retain the planned timestamps.

    • ❕Setting a cutoff time of 0 hours essentially means to always trigger the correction logic.

  • Enable end timestamp correction: This toggle can be used to enable or disable the start timestamp correction

    • If it’s enabled, the user can choose the threshold in the amount of hours difference that needs to be between the start timestamp of the stop in Qargo and the actual end timestamp update coming from the FMS, for the correction logic to trigger. The default is 8 hours.

    • Example: so if a driver started a stop at 08:00 PM in their FMS and then went home for the day. The next day the driver would completed the stop finally at 08:00 AM, so the update would be 12 hours late. This would trigger the correction logic and the end timestamp of the stop will be set to the 08:00 PM the previous day instead.

    • ❕Setting a cutoff time of 0 hours essentially means to always trigger the correction logic.

  • Allow timestamp updates to completed stops:

    • This essentially determines if you want timestamp updates to already completed stops or not. Other kind of updates will still go through no matter what.

    • Example: if the planned already completed the stops in Qargo. The stop updates from the FMS won’t be able to mess up the planning anymore.

Some more examples:

  • You have a stop that starts at 6am, the cutoff is set at 3 hours and your current time is 10am. You complete the stop now on Transics (4h > 3h). Only the stop status is updated and the planned times are kept on the stop.

  • The “allow updates to completed stops” is set to off. You have a stop that was completed by the planner at 7pm. The cutoff is 3 hours and you complete it on Transics at 8 pm. The times that are present on the stop will not be updated.

Please contact your Account Manager if you would like to configure these.

Did this answer your question?