My Orders are Not grouping

Modified on Thu, 29 May at 6:21 PM

In Dispatch Science, driver run order grouping relies on several key settings to ensure compatibility between orders. If your orders are not grouping, review the checklist below to identify potential configuration issues.


Requirements for Order Grouping

For orders to be grouped for a driver’s run, they must meet the following criteria:

  1. Order Profile Grouping Settings

    • Orders must share the same Order Profile settings that support grouping.

  2. Allow Grouping from Different Accounts

    • In the Order Profile, the setting "Allow to group orders from different accounts" must be enabled.

  3. Reference Fields Configuration

    • Ensure none of the reference fields are set to "Updatable by the driver".

  4. Matching Workflows and Steps

    • Orders must use the same Workflow and have the same Workflow Steps selected.

  5. No COD Configuration

    • Orders with Cash on Delivery (COD) options will not be grouped.

  6. No Identity Requirement

    • If the "Require Identity" step is enabled in the workflow, grouping will be disabled.

  7. Overlapping Time Windows

    • Pickup windows must overlap for pickups.

    • Delivery windows must overlap for deliveries.


How to Identify Grouping Keys

To verify grouping compatibility and determine why stops are not grouping, use our Management API:


Step-by-Step Instructions

  1. Navigate to the Tenant API.

  2. Use the following endpoint:

    bash
    CopyEdit
    GET /api/v1/drivers/{id}/stops
  3. Replace {id} with the Driver ID.

  4. Click Execute and log in using your Dispatch Science credentials.

Example Output

You will see multiple stops with a field called groupKey. Here’s an example of two stops with different


 groupKeys:

makefile
CopyEdit
groupKey: 1_2_True_True_True_False_False_39.1577_-108.7352e07f4df7e884aa47d0dfbde4a47ef2ec47bba163 groupKey: 1_2_True_True_True_False_False_39.1577_-108.73521542418e9e018a877c5dd8925c3ccd270939c2e8



Since the groupKey values differ, these stops cannot be grouped.


Understanding the Group Key Structure

The groupKey is a unique identifier that defines grouping compatibility. It includes the following components:


PositionDescription
1Stop Type: 0 = Pickup, 1 = Delivery
2Order ID or Grouping Status: displays the Order ID if ungroupable due to reasons such as:
- Not optimized
- On Hold
- Grouping set to None
- Identity or COD/COP workflow step selected
 - Required reference fields for driver
3Group Compatibility: Shows either the Account ID or a set of True/False values depending on the “Allow different accounts” setting
4–7Order Options from Account Details:
- Package Validation
- Skip Orders with No Items Scanned
- Allow Partial Pickup/Delivery
- Allow Adding Items
 - Allow Validation Without Barcode
8Grouping Method:
- AddressLine1 if grouping by address
- Lat_Long if using geolocation
9Workflow Hash: ensures workflow steps are identical

Final Notes

  • Ensure consistency in setup across orders intended to be grouped.

  • Use the API to troubleshoot grouping issues.

  • If unsure, consult your account administrator to verify workflow and account configurations.






 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article