Orders API DELIVERY fulfillment returns 200 but isn't seller-accessible — need First-Party Delivery enabled

Questions
,
1

We’re a production Square merchant (Khachapuri) running our own website ordering directly on the Orders API. I’m trying — again — to get DELIVERY-type fulfillments working end-to-end, and I believe the blocker is that our account isn’t enrolled in First-Party Delivery.

What happens:

  • POST /v2/orders with a DELIVERY fulfillment returns 200 (success).
  • But the order isn’t accessible to us as the seller, doesn’t appear in Order Manager, and won’t auto-fire to our kitchen printer — only a manual “print to all” on the terminal reaches it.
  • PICKUP fulfillments behave fully on the same account (Order Manager + automatic kitchen printing), so the pipeline itself works — this is specific to DELIVERY.

This matches the documented gated behaviour (“Requests to create a DELIVERY fulfillment order succeed with a 200 response even if you don’t have a partnership agreement… However, the delivery order cannot be accessed by a seller and does not appear in the Square Order Manager”).

Prior history: I raised this back in March and never got an official Square response — the only reply was a community member correctly pointing out our production account likely isn’t flagged for First-Party Delivery: :backhand_index_pointing_right: Using the API with fulfilment type Delivery not working

What I’m asking:
Could a Square staff member please either (a) enroll/flag our account for First-Party Delivery, or (b) point me to the exact team/process/owner to get it enabled? We’re a single-location restaurant using this for our own delivery orders (not a delivery platform), so I want to make sure I’m on the right path rather than the wrong application queue.

Merchant location ID: [redacted] · Application ID: [redacted]. Happy to move to a private channel with full account details.

Thanks — really hoping to get this actioned this time.

2

Thank you for flagging. Sending you a DM for more info.

3

Your troubleshooting looks solid, and the behavior matches what Square documents for accounts without First-Party Delivery enabled. A Square staff member will likely need to verify your account and route your request to the team that handles enrollment. I’d also recommend removing your IDs from the public post and sharing them privately instead.

4

Thank you for this - I cannot see where I can edit my original post unfortuantely, but I’d be happy to remove those IDs now there is a square team member communicating in DMs. I’ve been searching but it seems unclear to me.

I can click 3 dots in my reply end there’s a delete or edit option but perhaps it’s been too long since I posted for edits to still be allowed.

5

For anyone experiencing these issues in future, this is the forum to post on, not contacting support in messages or emails. Also giving all the details as above clearly for the Square staff to pickup on (although perhaps leaving out IDs with the offer of communicating via DMs). This second post got a reply and resolution within days and it does unlock all of the issues. The system works perfectly once enabled - just strange how some things work and the APIs appear to work even if you haven’t been enrolled. Thanks for the resolution!

6

I went ahead and redacted the fields for you! And yes the forums is our main surface for developer support and will get the fastest support from us. Occasionally replies in threads can be missed but please feel free to post a new topic for additional help needed in the future. Thanks for building with Square!