Fix a delivery stuck in Created

A delivery in Created status means Nash has the order but no provider has picked it up yet. Usually a provider is assigned within moments; if a delivery sits in Created, no provider took it automatically — often because none was eligible, or because the order isn't set to dispatch on its own.

Assign a provider yourself

The most direct fix is to pick a provider from the quotes:

1. Open the delivery and start Assign Provider. See manually assign a delivery.

2. If the list looks empty, turn on Show unavailable to reveal providers that couldn't take the delivery. Each is tagged Not eligible (no contract accepted the order, or the stop is outside the provider's coverage), Not in strategy, or Unavailable (the provider returned an error) — hover the tag to see the reason. For a Not eligible provider, the contract eligibility page shows which rule each contract failed.

3. Pick an available provider and confirm.

That reason tells you what to fix. If it's about the pickup or drop-off details, edit the delivery and try again; if a detail can't be edited, duplicate it with the correction. If it's no longer needed, you can cancel it.

Let a strategy dispatch it

If deliveries should go out on their own, that's the job of a dispatch strategy with auto-dispatch — deliveries created without one will wait in Created until you dispatch them by hand. Whether auto-dispatch and its rules are set up varies by organization; reach out to Nash if you'd like help.