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

Questions
1

Hi all — we build front-ends for Square sellers, and I’d like to confirm the
current (2026) supported story before committing to an architecture. The seller’s
most valued feature is On-Demand Delivery, so the overriding constraint is that we
must not break courier dispatch.

Setup. A prepared-food and packaged-grocery seller running a Square Online
(classic) storefront with On-Demand Delivery enabled — Square dispatches the
courier and the customer pays the fee. They want a custom menu/marketing
front-end on the apex domain, with Square Online moved to an order. subdomain.

Is On-Demand Delivery reachable from the Orders API? Concretely: if we create an Order with a DELIVERY fulfillment and take payment with the Web Payments SDK on our own domain, does that dispatch a courier the way a Square Online order does — or is On-Demand Delivery strictly a Square Online feature?

If a custom checkout retains courier dispatch, our whole design changes and the
rest of this post is moot. If it doesn’t, we fall back to a no-cart showcase site
that deep-links each item into Square Online, and the follow-ups below apply.

What we already established

  • No supported ?add-to-cart style URL parameter for Square Online.

  • No external ordering widget, and iframing the storefront is unsupported (the
    cart session breaks).

  • Buy Buttons / Payment Links appear to be the wrong channel — as I understand it
    they don’t dispatch an On-Demand Delivery courier and don’t carry item
    modifiers. Please correct me if that’s wrong, as it’s load-bearing for us.

  • Item deep-links of the form /product/<slug>/<id> are in the sitemap and look
    stable.

Follow-ups, if the answer to the above is “Square Online only”:

  1. Is there any supported way to hand a multi-item selection from an external
    site into a Square Online cart — URL parameters, an API, or a signed redirect?
    I believe the answer is no today; I want to know whether that’s still accurate
    and whether anything is planned.

  2. Are Square Online item URLs stable when a seller renames an item? Does the
    <slug> change, and does the old URL 301 to the new one? We’d be linking to
    these externally, so silent rot is a real risk.

  3. Snippets API — the docs say Square Online APIs are “publicly available as part
    of an early access program.” What’s the current path to get an application
    enrolled? We’d use it only to align typography and colour so the handoff to the
    storefront feels less abrupt.

A clear confirmation either way is genuinely valuable here. We’re choosing
between two architectures, and one of them is significantly better for the seller
if it’s viable.

Thanks.

3

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:

  1. Multi-item handoff into a Square Online cart — No. There is no supported URL parameter, API, or signed redirect to pre-populate a Square Online cart from an external site.

  2. Item URL stability on rename — The slug portion of the URL does change when the seller edits the SEO permalink field. Square does not auto-generate a 301 redirect; the seller must manually add one via Website → SEO → URL Redirects. The item ID in the path may persist, but the slug can silently rot if renamed without a redirect.

  3. Snippets API enrollment — No special enrollment is needed. Despite the “early access” label in the docs, the Snippets API is publicly available to developers in the US, Canada, UK, Australia, and Japan. You need production credentials and a live Square Online site (Sandbox is not supported). Start here: Add a Snippet to a Site