> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rushly.us/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery Tiers

> The three delivery speeds you can offer at checkout

Pass one of three values as `delivery_tier` when creating an order. Pricing is fixed and global — the same across every store, not something you configure per retailer.

| Tier      | `delivery_tier` value | Customer price | Best for                                                            |
| --------- | --------------------- | -------------- | ------------------------------------------------------------------- |
| Standard  | `standard`            | \$25.00        | Default same-day delivery                                           |
| Priority  | `priority`            | \$35.00        | Faster dispatch — only drivers marked priority-capable are eligible |
| Scheduled | `scheduled`           | \$22.00        | Lower urgency — any available driver can take it                    |

`delivery_tier` is optional and defaults to `standard` if omitted.

<Note>
  The price you should show the customer at checkout is exactly the
  `delivery_fee` on the order returned by the API (in cents) — it's always
  derived from `delivery_tier` server-side, so it will never drift from this
  table.
</Note>

## How tier affects dispatch

Drivers are matched to orders by capability, not just proximity:

* A **priority**-capable driver can take `standard` or `priority` orders.
* A **standard**-only driver can only take `standard` orders.
* **Scheduled** orders can go to any available driver, regardless of tier — the lower urgency means tier matching doesn't apply.

If no eligible driver is available when the order is created, it's queued rather than failing — see [order lifecycle](/order-lifecycle) for what that looks like.