Require the driver to scan the hub to start the round

If activated, the driver must scan the QR code of the hub to be able to start the round

Require the driver to scan the hub to end the round

If activated, the driver must scan the QR code of the hub to be able to end the round

Use zone preferences of the drivers

If activated, the optimization will try to respect the zone preferences of drivers during the round creation, meaning that the drivers will work in priority in their preferred zones. This is not a hard constraint. If more optimal rounds can be created the drivers might work in different zones too.

Include breaks in the rounds

If activated, the optimization will split the round with breaks (either by specific time or by working time)

Dispatcher signature at preparation

If activated, the dispatcher must provide their signature in the app at the preparation stage

Send a notification when some tasks are not geocoded when the optimizer runs in automatically

If activated, a notification will be sent, warning that during the AUTOMATIC optimization, some tasks have geocoding errors 

This optimization will use a virtual fleet

If activated, the optimization will use a virtual fleet (without drivers) allowing the customer to select vehicles and mention how many are assigned, where they should start/end the round, if they are or are not linked to a hub, and the start time.

Assign the drivers sequentially, independently of their vehicle

This option can only be activated when the fleet assignation is specified as a set of drivers (the customer assigns drivers). This toggle, when activated, will ask the optimizer to follow the sequence in which the drivers have been added to this section.

Group tasks by recipient

If activated, this feature ensures that all tasks going to the same recipient will be grouped into the same round and will be delivered in sequence. The service time of the stop inside the round will also be adjusted based on the selected rule.

Use traffic data during the round calculation

If activated, the optimization will take into account the traffic data in order to create the rounds

Only allow to create rounds starting in the future

If activated, only rounds starting after the actual time will be created. For example, If you announce tasks to be performed from 09:00 to 18:00 but it's already 10:00 then all rounds will be created starting after 10:00.

Only allow to optimize tasks with status "Received"

If activated, the optimization will only take into account the tasks that have been at least dispatched to create rounds. 

Validate rounds manually

If activated, the optimization will only create rounds with the status `created` that have to be manually validated (then they will be ready to be prepared in the hub). In this case, a round can NOT be edited unless it goes back to the ‘created’ status.

Publish rounds manually

If activated, the optimization will only create rounds with the status `validated` that have to be manually published (then they will become available for the driver to see). In this case, a round can NOT be edited unless it goes back to the ‘created’ status.

Do not re-optimize tasks with the status "in preparation"

If activated, rounds that are already being prepared by the driver will not be affected if the optimization is relaunched.

Inform when tasks with similar coordinates are assigned to different rounds

If activated, an info symbol will appear next to the announcement only if some tasks with similar geocoded addresses are assigned to different rounds

Inform when tasks with similar coordinates in a round don’t have sequential sequence numbers

If activated, an info symbol will appear next to the announcement only if some tasks with similar geocoded addresses do not have sequential numbers in a round, meaning that they do not follow each other in the delivery/pick-up process.

Recalculate path after optimization

If activated, the optimization will recalculate the rounds after having received the optimized rounds from our optimizer. Start time and sequence are kept as suggested by the Optimisation but the path between the tasks and the ETA will be recalculated.

Enable ESRI custom configuration

If activated, the customer can set a custom configuration of the ESRI optimizer and select preferences that will be applied for the specific optimization. Such changes will impact future optimization results so prior testing is highly recommended!

Enable Graphhopper custom configuration

If activated, the customer can set a custom configuration of the GraphHopper optimizer, revealing two other toggles: whether the optimizer should make the round ‘finish at the hub’ and another toggle to ‘enable speed factor’ 

Force day-unique order IDs

If activated, the platform will force tasks to have unique IDs for the day. Two tasks cannot have the same ID. If duplicated IDs are encountered then an error will appear in the announcement.

Restrict order IDs per type only

Linked to force day-unique order IDs. If activated it will only affect tasks with the same type (Delivery / Pickup).

If a delivery has the same ID as a pickup, it's accepted as they are of different types. But if two deliveries or two pickups have the same ID, you will receive an error in the announcement.

Create unplanned tasks

This toggle is present only for planning flows. If activated, the flow will create tasks in the platform without a date of delivery. 

Use a relative time window

If activated, and if no date or delivery time window is present in the announcement file then the tasks will be performed during a relative time window instead of a fixed time window.

Enable automatic replanification 

The system will automatically replan failed delivery attempts to another date and time. Here a script is needed in order to set the rules for replanification of tasks that were not delivered.

Allow updating items

If activated, customers have the ability to update items of tasks that were previously announced.

Allow updating metadata

If activated, customers have the ability to update metadata of tasks that were previously announced.

Generate pickup automatically

The system will automatically generate a pick-up located in the hub when you announce a delivery task without a dependency

Planning 

If activated, you will create a flow where planning is enabled 

Planning via tracking page

If activated, the possibility to choose an available time slot to perform the task will appear on the recipient’s tracking page.

Allow flexible time windows

If activated, it will allow the creation of tasks with a time window that doesn’t match exactly the time slots defined in the hub and it will be assigned to the time slots which match the most. If the time window doesn’t match at all a time slot, then it will be rejected. 

Ignore capacity constraints in timeslots

If activated, the restriction of the capacity of the time slot will be ignored and the time slot can be overloaded.

Limit the number of bookings allowed

If activated, the tracking page informs the recipient about how many times deliveries can be replanned

Block booking x days or less before the planned delivery date

If activated, the tracking page informs the recipient up until when they can replan their order

Do not allow to select timeslots that reached the cutoff time

If activated, it will only be possible for the recipient to reserve a time slot before the cutoff time set for that specific time slot

Barcode scan

If activated, the dispatcher must scan the barcodes of every item for pickup tasks upon arrival

Photo

If activated, drivers must take a picture when they mark the pickup task as ‘FAILED’

Barcode scan

If activated, drivers must scan the barcodes of every item in order to validate the pickup

Customer signature

If activated, the recipient’s signature is necessary in order for the driver to validate the pickup

Customer commented signature

If activated, the recipient’s signature is necessary in order for the driver to validate the pickup and a comment can be added 

Contactless 

If activated, the driver must perform a contactless pickup and introduce the PIN code received by the recipient

Comment 

If activated, a comment must be shared about the experience of pickup 

Photo

If activated, drivers must take a picture in order to validate the pickup

On site

If activated, if the driver is not at the right location for the pickup, a warning pop-up will appear in the app to warn the driver. Then the driver can either cancel or validate his position.

Barcode scan

If activated, the dispatcher must scan the barcodes of every item in delivery tasks on arrival

Barcode scan

If activated, drivers must scan the barcodes of every item in order to start their round

Check list

If activated, drivers must check on the checklist every item in order to start their round

Photo

If activated, drivers must take a picture when they mark the delivery as ‘FAILED’

Barcode scan

If activated, drivers must scan the barcodes of every item in order to validate the delivery

Customer signature

If activated, the recipient’s signature is necessary in order for the driver to validate the delivery

Customer commented signature

If activated, the recipient’s signature is necessary in order for the driver to validate the delivery and a comment can be added 

Customer concerns about items and signature

If activated, the recipient’s signature is necessary in order for the driver to validate the delivery and the recipient can share if they have concerns about the condition of the delivered goods

Contactless 

If activated, the driver must perform a contactless delivery and introduce the PIN code received by the recipient

Comment 

If activated, a comment must be shared about the experience of delivery 

Photo

If activated, drivers must take a picture in order to validate the delivery

On site

If activated, and if the driver is not at the right location for the delivery, a warning pop-up will appear in the app to warn the driver who can either cancel or validate his position.

Barcode scan

If activated, drivers must scan the barcodes of every item in order to validate the drop-off

Customer signature

If activated, the recipient’s signature is necessary in order for the driver to validate the drop-off

Customer commented signature

If activated, the recipient’s signature is necessary in order for the driver to validate the drop off and a comment can be added 

Customer concerns about items and signature

If activated, the recipient’s signature is necessary in order for the driver to validate the drop-of and the recipient can share if they have concerns about the condition of drop-off goods

Contactless 

If activated, the driver must perform a contactless drop-off and introduce the PIN code received by the recipient

Comment 

If activated, a comment must be shared about the experience of drop-off 

Photo

If activated, drivers must take a picture in order to validate the drop-off

On site

If activated, and if the driver is not at the right location for the drop-off, a warning pop-up will appear in the app to warn the driver who can either cancel or validate his position.

Reject addresses geocoded in a different postal code

If activated, there will be a check of the tasks’ postal code during the announcement (geocoding), and addresses with a different postal code will be rejected

Exclude the street number from address validation

If activated, the system will not check if the street number exists or not during the announcement 

Use Arcgis

If activated, geocoding will be checked and performed through Arcgis.

Use Google

If activated, geocoding will be checked and performed through Google.

If both Arcgic and Google are activated, the flow will run the geocoding through both and take the best result.

Active

When Webhooks are created you can choose if they are active or not

Activate message in case of webhook not delivered

If activated, allow the platform to send a notification if webhooks are not delivered

Reassign password

If activated, allows you to modify the user’s password

External

If activated, the driver is known as an external