Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usenash.com/llms.txt

Use this file to discover all available pages before exploring further.

Dispatch Automation provides a way to dynamically manage your dispatch strategies. An Automation is comprised of several Rules. If the conditions of a Rule are True, then the resulting action is that a Dispatch Strategy will be applied to the job. Let’s assume you have two dispatch strategies:
  • Individual Order Dispatch Strategy (DS_1): comprised of short-distance gig fleets, lowest price strategy
  • High Value Dispatch Strategy (DS_2): contains a list of long-range fleets that specialize in white-glove delivery
  • Default Dispatch Strategy (DS_3): a mix of all fleets
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: 
# psuedo code
if condition_1:
  apply dispatch_strategy_1
else if condition2:
  apply dispatch_strategy_2
else:
  apply dispatch_strategy_3
Dispatch Automations will apply to any job that does not 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

Dispatch Rules have a set of properties that can be used to evaluate incoming jobs. Here’s a list of those properties:
  1. Package Value
  2. Pickup Business Name
  3. Pickup City
  4. Pickup State
  5. Pickup Zip/Postal Code
  6. Dropoff Business Name
  7. Dropoff City
  8. Dropoff State
  9. Dropoff Zip/Postal Code
  10. Items Count
  11. Driving Distance
  12. Minutes Until Pickup
  13. JobMetadata
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

​
Utilizing Job Metadata

You can query fields tags that you set in the 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 CS member to configure it at the Org Creation level. Dispatch Automation