Route long-distance orders to a different strategy

Last updated: September 22, 2026

Goal: send orders past a distance you choose down a different dispatch strategy, so short trips and long trips each go to the providers that handle them well — without anyone sorting orders by hand.

Workflows is a beta feature; if you don't have it yet, reach out to Nash for early access.

The recipe

  • Trigger: Order has been created
  • Condition: Driving Distance Greater Than your threshold
  • Action: Set dispatch strategy

Every order that comes in above the threshold gets the strategy you name; everything else keeps the strategy it already had.

Why this is worth setting up

A single dispatch strategy applies one provider-selection rule to every order it touches. It can't switch providers by how far the trip is — so if your short and long trips are carried well by different providers, one strategy has to compromise on both.

Splitting them by distance lets each strategy be built for the work it gets:

  • A local strategy over the providers that do well on short, on-demand trips.
  • A long-distance strategy over the providers that go further, often with more notice — pair it with timed auto-dispatch so those orders reach providers when they'll quote them.

Adding more bands

You can run more than one of these. Add a second workflow with a higher threshold and a third strategy, and order them so the most specific band wins. Keep the bands few and the boundaries round — every band is another strategy to maintain, and the gain comes from the providers being genuinely different, not from the precision of the cutoff.

To find where your own boundaries sit, read what providers turn down on the orders you already run — see see why a provider didn't quote.

When to use it

Reach for this recipe when you can see two different jobs in one order stream: a dense local zone that almost always finds a driver, and a longer tail that needs different providers or more notice. If every order you run is served well by the same set of providers, one strategy is simpler and you don't need this.

See how to build this and all triggers, conditions, and actions.