For stops that are in progress, the Edit stop times modal presents two options instead of one:
Set actual arrival & planned departure time: Record the real arrival and adjust the planned departure. The stop stays open; the driver keeps the task flow and can still upload documents (CMRs, etc.).
Set actual arrival & actual departure time: Record both actual timestamps and complete the stop immediately, as before.
Stops that have not yet started keep the existing single-edit flow.
Why
Once a driver arrives and a stop is in progress, planners previously could not extend the stop's duration without setting a departure time—which auto-completed the stop and removed the driver's task flow on the board computer.
Use Cases
On-site delays: A customer site calls and says unloading will only start at 20:00. The planner extends the stop's planned departure without completing it, so the driver can still upload the CMR when unloading finishes.
Execution visibility: Planners can reflect real-world delays on the planning board as they happen, without orphaning the driver's task flow.
Terminology
Term | Definition |
In progress | A stop whose driver has already arrived and confirmed arrival on the mobile app or onboard computer |
Task flow | The sequence of tasks (e.g., upload CMR, confirm time windows) a driver sees on the board computer for a stop |
Planned departure | The expected time the driver will depart from the stop; editable until departure is confirmed |
Actual departure | The real time the driver leaves the stop; once set, the stop is complete and the task flow ends |
How
OPEN an in-progress stop and CLICK Edit stop times.
CHOOSE one of two options in the modal that appears.
FILL in the times according to your choice and SAVE.
The planning board updates immediately with the new times, and the dispatch team sees the delay reflected visually.
Edit an in-progress stop without completing it
OPEN the in-progress stop from the planning board (Timeline, Blocks, or Table view) or the trip stop detail.
CLICK Edit stop times.
A modal appears with two options:
In progress: actual arrival + planned departure (Keeps stop open)
Completed: actual arrival + departure (Closes stop)
SELECT 'In Progress: actual arrival & planned departure time'.
ENTER the actual arrival time and the new planned departure time.
CLICK Save. The stop stays open; the driver retains the task flow.
Complete an in-progress stop (existing flow)
OPEN the in-progress stop.
CLICK Edit stop times.
In the modal, SELECT Set actual arrival & actual departure time.
ENTER both the actual arrival and actual departure times.
CLICK Save. The stop is completed immediately.
Troubleshooting
Issue | Solution |
Modal only shows one option | The stop must be in progress (driver has confirmed arrival). Stops that have not yet started show the single-edit flow. |
Stop still shows as in progress after saving | You may have chosen Option 1 (Set actual arrival & planned departure time). This is correct; the stop remains open. To complete it, use Option 2. |
Driver's task flow disappeared | If you accidentally selected Option 2 and completed the stop, you can reopen it via the trip details and set it back to in-progress status (contact support if needed). |
Automating Stops Handling
Qargo does not currently support the automatic addition of a customs stop based on delivery location. However, you can achieve this functionality using these methods:
Manually Add a Customs Stop:
Navigate to
Locations > Internal stop actionsin the header.Click Add stop action in the left sidebar.
Create a custom action, such as "Customs" or "Inspection."
Open the order and go to the Execution section.
Click the stop icon in the Route to add a stop.
Choose Other (not Collect/Delivery).
Select the custom stop action you created.
Utilise Order Templates: - Set up an order template that includes a predefined "customs" stop. - When creating future orders from this template, the customs stop will be automatically added.
Automating Unloading Dates
To streamline order creation, Qargo allows you to automatically set an unloading (delivery) date to the day after the loading date. Here’s how:
Configure a service level with a one-day lead time, also known as a "next day" service level.
When this service level is selected while creating an order, Qargo calculates the delivery date automatically for the next calendar day. - The delivery (unloading) date will be automatically calculated as the next day after the loading date.
Qargo simplifies the management of stops and dates but may require specific configurations or workflows to address particular needs, such as adding customs stops or automating delivery dates. By using manual additions, templates, or service-level settings, you can tailor the platform effectively to streamline logistics.




