Restaurant profile, languages and hours

Open Settings for the selected restaurant. Confirm its name before saving changes.

Check shared POS settings before saving

A device assigned to a mode uses that shared mode’s service settings, not a second local iPad policy. Confirm the selected restaurant and assigned mode. The updated API merges edits to different POS-policy fields and rejects conflicting edits to the same field. In Admin, retain a rejected draft for review, then use Reload saved settings and confirm discarding it before reapplying the intended change. Do not repeatedly submit an outdated policy. Update the API before Admin and POS; older clients without the merge contract retain their legacy save behavior and must not edit shared settings during rollout. Restaurant identity, address, hours and customer records are not changed by a POS-mode edit. See shared mode recovery.

Check the restaurant before configuring POS methods

In Settings → Fulfillment → Point of sale → Manage by location, verify the restaurant before editing methods or optional customer information. These shared POS settings do not change its identity, address or customer database. Done prepares the draft; Save persists the whole configuration. An unsupported option or incomplete server confirmation leaves it unconfirmed: keep the draft and resolve the error. See POS method settings.

Review the by-weight authorization ceiling

For online by-weight orders, open Settings → Payments & VAT with settings.edit. Set Weight hold buffer % from 0 to 100 and save; the default for new restaurants is 20. A failed save keeps the draft. Zero still authorizes the estimate. Only the weight-priced subtotal gets a margin: 100 weighted + 50 fixed at 20% authorizes 170; delivery has no extra margin. Checkout shows the estimate, temporary ceiling and Confirm and authorize, in the restaurant theme. A changed ceiling requires customer review and another confirmation before payment; unknown policy blocks authorization. Existing reviewed checkouts and holds keep their ceiling. Staff confirm measured weights before capture and progression; excess beyond the hold is flagged for a separate payment, never automatically charged. Cash/pay-later makes no hold promise. Requires a configured authorize/capture provider, with partial capture, release and expiry validated before production. This neither changes the catering deposit/balance policy nor enables new-card saving with a CST weighted hold.

Edit restaurant information

In general settings update the displayed name, description, contact information and address fields available to your role. In Branding update logo and brand assets. Save and verify the guest-facing result; Website may have its own published design overrides.

Set supported languages

In Languages choose the restaurant languages and default language offered by the form. Translate catalog names and public website content separately. Changing the interface language alone does not translate every item or customer message.

Maintain opening hours

In Opening hours edit each day and its time ranges, including closed days. Check the restaurant time zone, calendar exceptions and separate pickup/delivery schedules. Save, then verify the next offered fulfillment slot without placing a real order. Orders & availability remains the common source for pickup/delivery receiving hours, closures and preparation. Delivery zones add coverage, days, fees and explicit same-day rules; they cannot enable a disabled service. Product-specific preparation replaces the restaurant default. If custom booking hours are active they retain their documented precedence; do not duplicate opening times in each zone.

Access the new controls

The entry sign-in invitation is now a published website order-journey preference. Order without an account remains available; this setting does not replace mandatory phone verification or payment/delivery validation. Google/Geoapify consumption and limits are separately available in Usage and quotas.

Staff contact details and courier destination

Staff contact details are managed in Admin → Staff → employee → Edit contact details. The restaurant-scoped name and phone are used for courier assignment and upcoming delivery reminders; the sign-in email remains read-only. Couriers can save a default final destination or link it to their home address. New routes propose that destination and allow an explicit override or removal. It is the courier’s end-of-route destination, separate from the customer’s delivery address. Existing populated routes and completed delivery snapshots keep their saved data. See staff profiles for saving, permissions and recovery.

POS code at staff activation

Staff activation checks the permissions assigned in this restaurant, including custom roles: orders.manage or payments.manage requires a private POS code. Read-only couriers and kitchen-only roles do not need one. Existing unused invitation links apply the same current rule. Changing a role label, courier address or route destination does not grant POS permissions. See activation and recovery.

Control weekly ordering manually

Weekly batch restaurants can choose Manual opening under Settings → Ordering & delivery → Orders & availability, with settings.edit. Save, then explicitly open or pause online orders using the pause control. Automatic opening/cutoff times do not control intake in this mode. Delivery days/windows, the restaurant timezone, preparation and stock rules remain in effect; existing orders are untouched. The website stays browsable during a pause. Active temporary test access must be disabled before reopening publicly. See the fulfillment settings guide for the complete procedure. Profile edits now persist only the fields actually changed so a concurrent name or contact save does not restore stale service hours. Opening-hour editors use a baseline: independent hour changes merge, while competing edits keep the draft and require reviewing the saved version. A zone name is only a label; configure its delivery weekdays in Delivery zones rather than relying on the name.

Test when an order is placed

In Orders & availability → Simulate an order, select Order date and time in the displayed timezone, then the receiving date and basket. Now reloads the server time. Preparation and same-day rules are evaluated at this reference using current saved settings and ready stock. A past date does not reconstruct history; this test neither reserves a courier nor creates an order. Customer orders retain the real server clock. See the simulation procedure.