Automations

Dispatch automation is a way to dynamically manage your dispatch strategies. An automation is composed of several rules; when a rule’s conditions are met, its action applies a dispatch strategy to the job. Let’s assume you have three dispatch strategies:

Individual Order Dispatch Strategy (DS_1): comprised of short-distance gig providers, lowest price strategy
High Value Dispatch Strategy (DS_2): contains a list of long-range providers that specialize in white-glove delivery
Default Dispatch Strategy (DS_3): a mix of all providers

You may want to assign different dispatch strategies based on the content of each delivery. One way to do that is to have the logic live on your server and attach the appropriate dispatch strategy for each new order. Another way to do this is by creating an automation at the account level. An automation is a set of IF / ELIF / ELSE conditions:

# pseudo code
if condition_1:
  apply dispatch_strategy_1
else if condition2:
  apply dispatch_strategy_2
else:
  apply dispatch_strategy_3

Dispatch automations apply to any job that doesn’t have a dispatch strategy assigned. If a job meets the defined criteria then it will have the relevant dispatch strategy applied, otherwise, the default dispatch strategy will be applied. The fallback default dispatch strategy can also be None, if you do not want any dispatch strategy to apply (not common).

Properties

A rule’s conditions test properties of the incoming job. Text properties support equals, does not equal, in list, not in list, starts with, ends with, contains, and does not contain. Numeric properties support greater than, less than, and the other comparison operators. Weight and dimension properties let you pick the unit in the rule editor and Nash converts it for you; driving distance uses your organization’s distance unit. Where

Property	What it checks
Pickup Business Name, Pickup City, Pickup State, Pickup Zip, Pickup Country	The pickup address fields. Country is a two-letter ISO code.
Dropoff Business Name, Dropoff City, Dropoff State, Dropoff Zip, Dropoff Country	The dropoff address fields.
Pickup Store Location	The store location the job picks up from.
Driving Distance	The driving distance from pickup to dropoff, in miles or kilometers.

When

Property	What it checks
Minutes Until Pickup, Minutes Until Dropoff	Minutes from now until the scheduled pickup or dropoff.
Pickup Time, Dropoff Time	The time of day of the scheduled pickup or dropoff, in that location’s local time zone. Comparison operators only.
Day of Week	The weekday of the scheduled pickup, in the pickup location’s local time.

What’s in the package

Property	What it checks
Package / Order Value	The declared value of the order, entered in dollars.
Driver’s Tip	The tip on the order, entered in dollars.
Items Count	The number of items in the package.
Number of Packages	The number of packages in the job. Always `1` when the automation evaluates an order.
Package Weight	The declared weight of the package, in pounds or kilograms.
Package Total Weight	The weights of the package’s items added up, each multiplied by its quantity. Falls back to Package Weight when no item carries a weight. Comparison operators only.
Package Width, Package Height, Package Length	The declared package dimensions, in inches or centimeters.
Package Max Dimension	The largest single dimension across the package’s items. Comparison operators only.
Package Cube	The volume of the package, width × height × length, in cubic inches or cubic centimeters. Comparison operators only.
Package Requirements	The requirements set on the package, such as a signature or age verification. Contains operators only.
Delivery Mode	The order’s delivery mode: `now` or `scheduled`.

Your own signals

Property	What it checks
Tags	The tags on the order. Contains operators only.
Metadata	A key you set in `jobMetadata` (see below).
Random Grouping	A stable number from 0 to 99 derived from the package’s ID, so you can send a share of jobs down a different path. “Less than 20” routes about a fifth of your jobs.

Matching postal codes. Pickup Zip and Dropoff Zip compare against the postal code exactly as it’s stored on the address, with no normalization. An address Nash geocodes carries the five-digit US ZIP, while an address you send as separate components keeps whatever you sent, including a ZIP+4 such as 94103-1234. To match both forms, use starts with and the five-digit code rather than equals.

Don’t see the property you need?We are continuously adding to this list based on customer needs — reach out to support@usenash.com and we can help you add a new property.

Using job metadata

You can query fields, such as tags, that you set in jobMetadata when applying dispatch automations. For example,

jobMetadata: {
  "tags": ["catering"]
}

And then when creating your Dispatch Rule you would query that the jobMetadata “tags” key contains the value “catering”.

Configuration

Dispatch automations can be configured from the Nash Portal. If you plan to create several Nash Organizations to manage as part of a partnership with Nash, you can get in touch with your Nash point of contact to configure it at the Org Creation level.

Getting started

Order

Dispatch strategies

Workflows

Notifications

Store locations & zones

Jobs

Batch jobs

Providers

Routes

Optimization strategies

Shifts

Templates

Store catalog

Feedback

Shipping

Simulate delivery

Fleet

Miscellaneous

Automations

Properties

Using job metadata

Configuration

​Properties

​Using job metadata

​Configuration

Properties

Using job metadata

Configuration