Skip to main content
Nash is a delivery orchestration platform that connects you to multiple courier networks through a single integration. Nash automatically routes orders to the best available driver across providers.

Overview

  • Coverage: Global
  • Plan: needs storekit+. Without it, the Nash page shows Upgrade to enable Nash instead of Get started.
  • Store type: listed only for stores that take pickup or delivery orders, not for table-ordering (in-store) stores.
  • Multi-provider: Access multiple courier networks
  • Smart routing: Automatic provider selection

Connected Providers

Nash connects to courier networks including:
  • DoorDash Drive
  • Uber Direct
  • Stuart
  • Roadie
  • Local courier fleets
  • And more

Setup

  1. Sign up for a Nash account at nash.io
  2. Add your billing / payment details in your Nash account
  3. Connect your preferred courier providers in Nash
  4. Obtain your Nash API key
  5. In storekit, go to Stores → your store → Settings → Integrations → Nash
  6. Click Get started if it’s shown
  7. Open Nash account → Edit and enter your API key and Org ID. When you first save, storekit checks them with Nash; if Nash rejects them you see Nash didn’t accept that API key and Org ID. Check them and try again.
  8. Open Pickup details → Edit and enter Pickup instructions (required before you turn Nash on; up to 280 characters)
  9. In Pickup details, set a Pickup phone if you want drivers to call a number other than the store phone. It’s required if the store has no phone number.
  10. (Optional) Open Dispatch → Edit to set Minimum vehicle size. Leave Send to Nash when order is on Accepted (see the warning below)
  11. Turn Nash on with the Enable Nash switch in the header, then Save
Nash cannot create a delivery job until valid billing / payment details are held in your Nash account. Nash bills you directly for its per-delivery platform fee plus the courier provider’s fees (see Pricing) — storekit does not pay the courier on your behalf. If billing details are missing, expired or a payment fails, orders are still accepted and paid in storekit but no delivery is created. See No Delivery Job Was Created.

Dispatch Settings

Open Dispatch → Edit on the Nash settings page:
Keep Send to Nash when order is on Accepted. Today storekit only sends jobs to Nash when an order is accepted, so with Preparing or Out for delivery selected no delivery job is created at all.

Pickup Phone Number

The pickup phone is optional when the store has a phone number — when it’s blank, Nash uses your venue’s store phone as the pickup contact. If the store has no phone number, you must set one here. To override it, open Pickup details → Edit on the Nash settings page and set a different number. This is useful when:
  • Your delivery coordinator uses a different number
  • You want drivers to contact a specific department
  • Your venue phone doesn’t accept calls during delivery hours
The phone number must be in E.164 format (e.g., +442012345678).

Pickup Instructions

Pickup instructions are required when Nash is switched on and tell couriers where to collect orders. Set them in Pickup details → Edit. If Nash is switched on and set up without pickup instructions, its status is Needs attention, and the Finish setup checklist shows Add pickup instructions.

How It Works

  1. Customer places a delivery order
  2. When the order is accepted, storekit sends it to Nash
  3. Nash evaluates available providers
  4. Best provider is selected based on the rules in your Nash account
  5. Driver is assigned and tracked
  6. When the courier heads to the customer, the order moves to Out for delivery; when Nash reports drop-off, it moves to Delivered
If you cancel the order in storekit, storekit also cancels the Nash job.

Order Data Sent

The customer’s email address is not sent to Nash.

How Pickup and Drop-off Times Are Calculated

The two times sent to Nash are derived from the order’s requested fulfilment time — for a pre-order, the start of the slot the customer chose at checkout; for an ASAP order, the current time plus your Delivery preparation time and the drive estimate to the customer’s address.
  • Drop-off start is the requested fulfilment time itself. For a 12:00–12:30 delivery slot, Nash is told the drop-off window starts at 12:00 — the slot start is the start of the window, not the promised arrival moment. Customers see the same slot start at checkout and on their tracking page, so a delivery landing inside the window is on time even when it isn’t at the slot start. See Pre-orders → Understanding slot times.
  • Pickup time is worked backwards from that: requested fulfilment time minus the delivery leg, where the leg is the per-address drive estimate storekit calculated for the customer’s address plus a fixed 10-minute buffer (collection and handoff allowance — not configurable). When no per-address estimate exists, the leg defaults to a flat 20 minutes. Example: a 12:00 slot to an address with an 8-minute drive estimate gives a pickup time of 11:42 (12:00 − (8 + 10) minutes). If the computed pickup time has already passed when the order is dispatched, storekit sends 5 minutes from now instead so Nash can still assign a courier.
storekit never marks a delivery “late” — the slot is a customer-facing expectation window only. If the courier runs behind, lateness is tracked by Nash and the courier network, not against the slot in the dashboard. See Who is responsible for the delivery.
The same pattern — drop-off window anchored on the requested fulfilment time, pickup backed off by the drive estimate plus a fixed buffer — is also used by Uber Direct and Orkestro. Other courier integrations compute their windows differently.

Routing Rules

Routing is configured in your Nash account, not in storekit. The storekit Nash settings have no routing options. Typical Nash strategies:

Priority-Based

Set provider priority order:
  1. First choice: Cheapest available
  2. Second choice: Fastest available
  3. Fallback: Any available

Cost Optimisation

Nash selects the cheapest option that meets your requirements:
  • Maximum delivery time
  • Minimum driver rating
  • Vehicle type requirements

Speed Optimisation

Prioritise fastest delivery:
  • Select provider with shortest ETA
  • Pay premium for speed when needed

Round-Robin

Distribute orders across providers:
  • Balance volume across partners
  • Test provider performance
  • Meet volume commitments

Customer Experience

Regardless of which provider fulfills the delivery, the customer’s order status page shows the courier’s name and photo, a button to call them and the order’s progress. storekit doesn’t receive an ETA from Nash, so the courier’s arrival estimate isn’t shown.

Fallback Handling

If the primary provider can’t fulfill:
  1. Nash automatically tries next provider
  2. Process continues until driver assigned
  3. If Nash cancels the job, the delivery shows as cancelled on the order (see Delivery Cancelled or Failed)
If storekit can’t create the job at all, the order shows a No courier booked warning (“Nash couldn’t book a courier at …”).

Where to Check a Delivery in the Dashboard

Not sure whether your store delivers through Nash, Uber Direct or another courier network? Go to Stores → your store → Settings → Integrations, pick the Delivery filter, and look for the tile marked Connected. Every Nash delivery is tracked on its order in storekit. To see live status and courier contact details:
  1. Open the order from the dashboard
  2. On the order, find the delivery tracker (the step indicator showing Pending → Assigned → En route → At dropoff → Delivered). Nash doesn’t send storekit an ETA, so no Pickup ETA or Dropoff ETA appears for Nash deliveries
  3. Select Details to open the Delivery details modal
The Delivery details modal shows: Nash deliveries have no Timeline, Fleet or Failure reason in this modal, and there is no Cancel delivery button: cancel a Nash job in the Nash portal, or cancel the order in storekit (which cancels the Nash job too).

Troubleshooting

No Delivery Job Was Created

If an order is accepted and paid in storekit but no delivery ever appears — no delivery tracker progress, and nothing in the Delivery details modal — the job was most likely never created by Nash, usually because of billing:
  • Check your Nash account for missing, expired or failed billing / payment details. Nash bills you directly for its platform fee plus the courier fees (see Pricing), so it cannot dispatch a courier without valid payment details on file
  • Check your email (including spam) for messages from Nash about billing or payment failures — this notice can arrive days before deliveries stop being created, and there is no advance warning about it in the storekit dashboard. Once a booking fails, the order shows a No courier booked warning
  • Once the billing details are fixed in Nash, new delivery jobs are created automatically again — no change is needed in storekit
  • In the meantime, contact support with the order: we can create the outstanding delivery job manually so the order still gets collected

No Driver Assigned Yet

While Nash is still searching for a driver, the delivery sits on the Pending step and the Delivery details status reads Not Assigned Driver (the same “we are still looking for a driver” state as a newly Created or Scheduled job).
  • Nash keeps searching and can automatically reassign the job across your connected courier networks until a driver accepts
  • Watch the delivery tracker on the order rather than preparing the food too early — a driver may not arrive for a little while after the order is ready
  • If your kitchen has not started, hold off on cooking until a driver is assigned (the tracker moves to Assigned), so hot food isn’t left waiting. For a live ETA, open the job in the Nash portal with View in provider dashboard
  • If no driver is assigned as the pickup window approaches, contact support with the Provider ID from the Delivery details modal

Driver Is Late to Pick Up

If a driver has been assigned but pickup is running late:
  • Check the live status on the order — the delivery tracker step shows where the courier is. For the ETA, open Delivery details → View in provider dashboard
  • Contact the courier directly: open Delivery details and tap the courier’s phone number in the Courier section
  • If you can’t reach the courier or the delay is significant, contact support with the Provider ID so we can follow up with Nash and the courier

Driver Arrived Before the Order Was Ready

storekit requests the Nash job when the order reaches the status chosen under Order status in the Nash settings (Accepted by default). The pickup time it sends is earlier than the delivery time shown to the customer: storekit takes the promised delivery time and subtracts both the driving time to the customer and a 10-minute buffer (20 minutes in total if no driving time is known). On a pre-order due at 11:00, for example, the courier is asked to collect at around 10:30, and a driver can turn up a little before that.
  • If the order is nearly ready, ask the driver to wait — the timeline in Delivery details shows when they arrived at pickup
  • If the driver leaves without the order, see Order Needs Another Courier below
  • If drivers regularly arrive too early on pre-orders, set Order status to Preparing so the job is only created when you move the order to that status — there is no setting in the storekit dashboard to change the pickup time itself

Order Needs Another Courier

If the courier left without the order, cannot be reached, took the wrong order, or the job ended before pickup, the order needs a new job. There is no button in the storekit dashboard to request a second or replacement courier, and storekit does not request one automatically — the Delivery details modal can only Cancel delivery.
  1. Open Delivery details and call the courier from the Courier section first, if a courier is still assigned
  2. If the job is still open but the courier is not coming back, click Cancel delivery so the job does not stay open (any cancellation fee is set by Nash and the courier network); this does not cancel the customer’s order
  3. Contact support and include the order number (the # code on the order), the store name, the Provider ID from Delivery details, and why a new courier is needed (for example “driver arrived at 10:30 before the order was ready and left”). We create a replacement job in Nash and send you the new tracking link

Delivery Cancelled or Failed

The Delivery details status badge (and the Delivery cancelled banner on the order) shows how a delivery ended:
  • Cancelled (Canceled By Provider, Canceled By Customer) — the courier network, Nash or the customer cancelled the job. A job Nash reassigns to another provider also shows as Canceled By Provider on the original attempt
  • Expired (Expired) — no driver was found within the allowed window
  • Failed (Failed) — the delivery could not be completed
  • Returned (Returned, Return In Progress) — the order is being, or has been, returned to your store
storekit doesn’t store Nash’s cancellation reason; check the job in the Nash portal with View in provider dashboard. If a delivery is cancelled or fails and you need help resolving it, contact support.

Who Is Responsible for the Delivery

storekit passes each delivery order to Nash; Nash then selects and manages the courier network that collects and delivers the order. This means the outcome of a delivery — including late pickups, no driver being assigned, or damage in transit — is handled by the courier partner performing the delivery, not by storekit. If something goes wrong, storekit support can raise a claim or refund request with Nash on your behalf. Any refund or compensation is subject to the courier partner’s approval, so we can’t guarantee an outcome, an amount or a timeline. To start this, contact support with the order and the Provider ID from the Delivery details modal.

Pricing

Nash charges:
  • Per-delivery platform fee
  • Plus courier provider fees
What the customer pays for delivery is set by your storekit delivery zones. Cost limits and subsidies for the courier fee are set in your Nash account; storekit has no Nash pricing settings.

Best Practices

Multiple Providers

Connect 2-3 providers for redundancy

Test Routing

Test different routing rules in Nash to optimise cost/speed

Set Limits

Set maximum costs in your Nash account to control spending

Monitor Performance

Review analytics to identify best providers