We operate one UK restaurant and are building our own website checkout for our own Square account, with deliveries handled by our own drivers. The integration is private to our business; we are not distributing an app to other sellers.
We want website-created, paid orders to use genuine DELIVERY fulfilment, appear in the restaurant’s active order workflow, and print the structured recipient address on the kitchen/order ticket.
The fulfilment guide describes restricted DELIVERY access and explains that a successful create response does not establish seller/POS visibility. In the 22 October staff reply, Square offered an app-specific First Party Delivery eligibility assessment for another custom website.
Could Square clarify:
- What is the current private assessment route for this own-restaurant use? Which beta/partnership approvals are required, and is public Marketplace distribution actually required for this case?
- After approval, which paid-order/fulfilment states and supported Restaurants/POS apps make API-created DELIVERY orders visible in Order Manager and the restaurant’s active order workflow?
- Separately, which supported app/mode and printer-profile settings print
delivery_details.recipientname, phone and full address, delivery time and instructions on the physical kitchen/order ticket? We need confirmation of the structured fields and ticket behaviour, beyond API acceptance or screen visibility.
We can supply application, merchant and location identifiers privately through Square’s approved channel. Please identify the appropriate team and next step; no private identifiers or credentials are included here.