Last updated March 2024

Maven provides a powerful set of grouping options to combine individual pickup requests and individual deliveries on a manifest into stops. This way, when a fleet’s drivers go to a stop, Maven records a single stop, no matter how many pickup requests or deliveries are exchanged.

Grouping Deliveries

Criteria For Grouping Deliveries On Creation

When a fleet sends in a manifest for deliveries or adds deliveries to an inbound plan, Maven will group the deliveries into stops. The following configurations are available for the fleet to customize this grouping behavior.

[Proposed] Respect Customer Record or Formatted Address (applies to both deliveries and pickup requests)

Not currently available. Grouping is always based on formatted address.

When a manifest is sent to Maven, Maven can either group deliveries based on the deliveries' customer records or the deliveries' formatted address.

Grouping based on formatted address enables fleets with multiple customer records per actual real life customer location to overcome these data-quality issues. For example, if a fleet has a three deliveries to “Acme Company,” “Acme Co.,” and “Acme Incorporated,” if these all point towards the same real life location, they will be merged into a single stop.

Grouping based on customer records provides a more rigorous grouping that will result in more stops but there will be no ambiguity of which customer is being serviced.

geolocationOrCustomerRecord: [default] "geolocation" | "customer record" #Proposed.

Respecting Manifest Number

Maven will always respect the manifest number if provided. It will never attempt to merge or group stops that are not part of the manifest.

Respect Manifest Order

Manifests are often ordered based on how the trailer is loaded. When a fleet has manifests that are preordered, the manifest grouping logic can respect this order. Only deliveries that are continuous will be candidates for grouping.

For example a manifest that has the following deliveries:

Delivery 1: 5118 Liberty Ave.
Delivery 2: 5118 Liberty Ave.
Delivery 3: 123 Fairmount St.
Delivery 4: 5118 Liberty Ave.

If Maven respects manifest order, three stops will be produced:

Stop 1: 2 deliveries, 5118 Liberty Ave.
Stop 2: 1 delivery, 123 Fairmount St.
Stop 3: 1 delivery, 5118 Liberty Ave.

maintainSequenceOrder: true | [default] false

Respect Service Time Windows

Deliveries often have service time windows. Maven can respect these to varying levels.

Exact: Maven will only group deliveries with identical service start and end times.
Overlapping: Maven will only group deliveries with overlapping service start and end times.
None: Maven will not exclude shipments from being grouped based on time windows.

Minimum Overlapping Windows

If a delivery only overlaps with a stop by a few minutes, many fleets may want to treat this as a separate stop. Maven offers a minimum time overlap to check against in these cases over overlap. If a delivery time window and the existing stop’s time window are below a minimum overlap, then the delivery will not be grouped.

minimumIntersectingTimeWindow: 7200000
"minimumTimeWindow":7200000
Note: Not used if a fleet is using either Exact or No Window matching (see “Respect Service Time Windows”)

Exempt Deliveries Based On Shipment Tags

Some fleets may want certain deliveries to not be automatically grouped. For example, time-critical deliveries that need to remain as their own stop. Maven can respect these critical shipments and ignore them completely from grouping logic.

exemptTags: ["critical-service", "hot shipment"]

Calculating Resulting Delivery Time Windows

Once a stop has been determined, then Maven will calculate a stop window for the stop. This calculation can be configured based on the options below:

Resulting Stop Time Window (applies to both manifests and pickup requests)

Once a stop has been created from one or more deliveries, the stop’s service window must be calculated. Maven offers the following options:

Tightest window – the latest of the start delivery times and the earliest end delivery times.
Earliest windows – the earliest of the start and end delivery times.
Latest windows – the latest start and end times.
Widest window – The earliest of the start times and the latest of the delivery times.

combinationOption: [default] "tightest" | "earliestOpenEarliestClosed" | "latestOpenLatestClosed" | "earliestOpenLatestClosed"

Prioritized Time Windows

For stops with designated critical shipments, when calculating the stop’s time window (see “Resulting Stop Time Window), Maven will only calculate based on these critical tags.

preferredTags: ["critical-service", "hot shipment"]

Grouping Deliveries On A Manifest Update

Maven will update delivery stop groupings when an update to a manifest is sent in. The extent of grouping depends on whether the manifest has been begun by the driver or not.

For manifests that have not been begun, Maven will recalculate the entire manifest to align with the manifest update request. Any pickups or lunches already on the manifest, will be placed at the very end after the recalculated deliveries.

For manifests that are active, Maven will remove from the driver’s manifest any deliveries that are not present on the update manifest. Any new deliveries will be appended to the end of the manifest and available to the driver or dispatcher to merge together.

Grouping Pickup Requests

Maven receives pickup requests for individual shipments. Maven combines these requests into assigned and/or unassigned stops.

Criteria For Grouping Pickups On Creation

Respecting Manifest Number, Route Code, and Terminal

Maven will always respect the manifest number, route code, or Terminal if included in a pickup request. If there is any discrepancy between the three attributes (say the manifest is in a different terminal), Maven will always respect in order: 1. manifest number 2. route code 3. terminal.

Respecting Dispatcher Split Stop

When a dispatcher splits a stop, no additional pickups will be automatically grouped to either split stop. The dispatcher will still have the option to manually group.

Respect Customer Record or Formatted Address

See above for description.

Respect Service Time Windows

See above for description.

Exempt Pickups Based On Shipment Tags

See above for description.

Resulting Stop Time Window

See above for description.

Filter on Unassigned/Staged or Assigned Stops

When creating a pickup request, Maven can limit the options for grouping to assigned/staged or unassigned stops.

groupUnassignedAndAssigned: true / false

Filter on Delivery or Pickup Stops

When creating a pickup request, Maven can limit the options for grouping to whether a stop has a pre-existing pickup or delivery request.

groupPickupsAndDeliveries: true / false

Minimum Overlapping Windows

minimumIntersectingTimeWindow: 7200000
Note: Not used if a fleet is using either Exact or No Window matching (see “Respect Service Time Windows”)

Calculating Resulting Pickup Time Windows

Calculating time windows for pickups happens in an identical manner to grouping deliveries. See “Calculating Resulting Delivery Time Windows”.

Grouping Pickup Requests Updates

When updates to Pickup Requests come into Maven, Maven will only regroup if the following are changed on the pickupRequest:

shipper customer number or address
terminal, route, or manifest updated
service time window