We use Square for Restaurants in the UK on iPads and Square Register. All four iPads currently show version 7.30. On the inspected iPad, the Dashboard shows Full Service with the Main Restaurant Tablet Profile. Our Head Chef printer profile uses full in-person order tickets. The Register's exact app build has not been independently checked.
Our phone-order workflow is: Menu → Guest → add the customer's name and full postal address → Save/attach the guest → Actions → Fulfilment → Delivery → add items. Our team reports that the customer's name and phone print on the kitchen ticket, but the street address does not. Staff therefore put the address into Notes, choose the delivery charge manually and remove the dine-in service charge.
We checked one existing historical delivery: recipient name/phone were present, but street information appeared only in Notes and the linked customer-address fields were blank. That sample does not establish that a populated customer-directory address was dropped. We need the supported fresh-address workflow.
Delivery already maps to Delivery; the customer-details prompt is on, while order tracking and mode-level fulfilment override are off. We have not changed these settings or created a test order. Could Square clarify three parts of the same journey?
1. Enter the address once and print it. Does saving a Guest's full address populate the basket's delivery-recipient street address, or is a separate order-recipient field required? Where is that field in our app? Which UK app, minimum version/rollout and printer settings support structured delivery-address printing? Please distinguish the separate Restaurants app from Restaurant mode in the Square POS app. The May 2026 announcement describes address printing, but we have not established that our particular workflow is covered.
2. Apply the correct postcode fee before payment. Is there a supported native rule or pre-payment cart extension that can use that same address/postcode to add the correct delivery fee? Our delivery pricing uses the most specific matching full-postcode, sector or district rule. We need one address entry and one order/payment, without staff learning rates, using an unrelated calculator or adjusting a paid order. If native configuration cannot do this, please identify the supported limitation and extension route; a generic Square Online setting or Orders API example would not establish native-basket support.
3. Keep automatic Eat In service charge, exclude Delivery/Collection. Our current service charge is 12%, automatically applied to all orders. The visible alternatives are manual per order or automatic by party size; we did not see a fulfilment/dining-option exclusion. Can Delivery and Collection be excluded while Eat In retains the current automatic rate? Please give the exact supported setting/path. Switching every order to manual service charge would change the dine-in workflow.
Please provide the supported configuration/app coverage, or identify which parts require a product/support case. We can supply device details privately; no customer information should be needed publicly.
