Dispatch strategy settings
Last updated: August 16, 2026
This is a reference for every setting on a dispatch strategy, grouped by the sections you see on the page. For how strategies work and how to create one, start with dispatch strategies.
Open a strategy at Orchestrate → Dispatch Strategies. If you have view-only access you'll see the settings but can't change them ("Ask an admin for edit rights"). Descriptions below explain what each control asks Nash to do — the result of a rule is decided when a delivery is dispatched, so treat behavior as intent rather than a guarantee.
The strategy itself
| Control | What it does |
|---|---|
| Name | The strategy's name. Required. |
| Strategy ID | A read-only identifier you can copy — useful when referencing the strategy in the API or with support. |
| Duplicate | Clone this strategy under a new name to build a variant without starting over. |
| Activate / Deactivate | A strategy only runs while active. Deactivate to pause it without losing the configuration; activate to bring it back. |
| Save | Saves your changes. Enabled once the form is valid and you have edit rights. |
Provider Selection
How the strategy picks a provider. Choose one mode; it decides how Nash orders the providers you allow. Default is Lowest Cost.
| Mode | How it picks |
|---|---|
| Lowest Cost | The most economical provider available, within your allowed list. (Default.) |
| Manual Ranking | The providers in the exact order you set — drag to reorder your list. |
| Most Reliable | Ranked by a reliability score from past performance (completion, cancellation, and more). |
| Weighted Distribution | Split volume across providers by a percentage you set per provider — the weights must add up to 100%. |
| Dynamic | Balances reliability against price automatically. Availability varies by organization — reach out to Nash if you'd like it. |
Allowed providers — the providers this strategy may use. You must add at least one. Drag to reorder them when you're using Manual Ranking; set per-provider percentages when you're using Weighted Distribution.
Delivery Fees
Maximum Delivery Fee — turn this on to set the most you're willing to pay for a delivery under this strategy, entered in your currency. Quotes above the cap are passed over.
Rules
Behaviors and requirements that apply while the strategy is in use.
- Auto-Dispatch on Creation — dispatch a delivery to a provider the moment it's created, rather than waiting for someone to review quotes and dispatch it by hand. For some integrations this is fixed and can't be changed.
- Auto-Dispatch Relative to Pickup Start Time — instead of dispatching at creation, dispatch a set number of minutes before the pickup time (for deliveries not already dispatched). Doesn't apply to orders using an optimization strategy.
- Package Requirements — restrict the strategy to providers that support the capabilities you select (for example proof-of-delivery photo or signature, ID/age verification, or alcohol handling). Providers without them are passed over.
- Vehicle Request — request a minimum vehicle type (car, van, truck, and so on) for deliveries under this strategy. If the delivery itself also specifies a vehicle, the larger of the two is used.
Auto-reassign
Triggers for moving a delivery to the next eligible provider in the strategy. Turn on the ones that fit your operation — with one exception: don't enable auto-reassign on creation time and on pickup time together (see the caution below).
When a provider cancels
- Auto-Reassign on Provider Cancellation — if the assigned provider cancels, reassign to the next provider automatically. Optionally reassign using a different strategy, and add a time constraint so it only reassigns when the delivery is still a set number of minutes before pickup.
- Smart Reassignment — before reassigning, Nash weighs whether another attempt is likely to succeed; if it isn't, the delivery is canceled instead of retrying repeatedly.
- Split Batch on Provider Cancellation — if a provider cancels an entire batch, split it into single deliveries and reassign them using a dispatch strategy you choose.
When it isn't picked up in time
- Auto-Reassign on Pickup Time — if the delivery's status hasn't advanced within a time you set, reassign. You define how many minutes before or after pickup to act, and which status it must still be at (for example still only Assigned Driver, or already Pickup Enroute — note that reassigning once a driver is en route may incur a cancellation fee). You can also send the reassignment to a different strategy.
When it's never assigned
- Auto-Reassign on Creation Time — if a delivery stays unassigned for a number of minutes you set, reassign it to the next eligible provider.
Warning
A caution on time-based auto-reassign. Use on creation time or on pickup time, not both — running them together can work against each other. And either can, in a close race, overlap with a provider just starting the delivery, so a time-based auto-reassignment may occasionally incur a cancellation fee. Nash does everything possible to avoid this, but in a tight race condition it's still possible.
To put a strategy to work, see dispatch strategies; for how dispatch and optimization strategies relate, see what strategies are.