Existing Square-managed Nash delivery from a custom checkout: supported dispatch route and DELIVERY access

[MariaLuisaEmpanadas]

We support a US restaurant with an existing Square-managed Nash On-Demand Delivery arrangement. We are preparing an independent website using Square Web Payments SDK, Payments API and Orders API, with ordering and payment remaining within that website.

We understand that creating a DELIVERY fulfillment or setting managed_delivery does not itself request a courier. We have read the Square team guidance here:

Delivery Integration

Orders created with the Orders API won’t push to the courier to be fulfilled with the Square built integrations. That connection is something that you would have to build with the integration you want to use to fulfill orders. Currently the DoorDash/Uber integrations allow sellers to accept orders through those integrations. If you want the DELIVERY orders to appear in the Dashboard and POS Order Manager once they are paid for then yes, you will need to enroll your account in the beta for DELI…

Does On-Demand Delivery dispatch via the Orders API, or is it Square Online only?

On-Demand Delivery is Square Online only — it does not dispatch a courier via the Orders API. The Orders API supports a DELIVERY fulfillment type (currently Beta), but creating an order with it does not automatically trigger Square’s managed courier dispatch (DoorDash/Uber). That courier-dispatch workflow is tied exclusively to Square Online’s checkout flow. For your follow up questions: Multi-item handoff into a Square Online cart — No. There is no supported URL parameter, API, or signed r…

Nash support supplied a guide requiring Square Online Ordering, while Square Customer Success referred our technical question here. We need a clear supported route before enabling delivery:

1. Can an independent API checkout use the restaurant’s EXISTING Square-managed Nash dispatch arrangement? If not, please confirm that limitation explicitly.
2. If there is an approved partner/API route, what enrollment, endpoint or event actually requests dispatch, and can it preserve the existing couriers, coverage, rates, billing and dispatch rules? We are not requesting a new service or changes to existing terms.
3. Separately, what enrollment is required for paid DELIVERY orders to appear in Square Order Manager/POS and the kitchen printer?
4. What safe test process would verify the supported integration before live courier dispatch?

A Customer Success case already exists; we can reference it through an appropriate private support channel. No credentials, customer records or account identifiers are included here.

[jseok]

1. No. An independent checkout built on the Web Payments SDK, Payments API and Orders API can’t use the restaurant’s existing Square-managed On-Demand Delivery arrangement. Courier dispatch only runs through Square Online checkout. An Orders API order with a DELIVERY fulfillment never requests a courier, and you can’t hand a cart off from an external site into Square Online.
2. Square doesn’t offer a partner or API route that triggers dispatch under the existing arrangement. If dispatch has to happen from your site, you would integrate directly with a delivery provider, and that would be a separate arrangement from the current one.
3. DELIVERY fulfillment requires enrollment on the seller account. Without it, CreateOrder still returns 200, but the order isn’t visible to the seller. A PICKUP or SHIPMENT fulfillment will show up in POS and print.
4. Square has no dispatch integration to test. For order visibility and printing, place a paid test order once the account is enrolled and confirm it shows in Order Manager and prints.