Help

🏢 Company View

Settings

The Settings page in Company View gathers company-wide preferences in one place. Each card opens a dedicated settings page; in Company View these settings apply to the whole company you have selected at the top of the screen (in Location View, the equivalent pages apply to a single location instead). Most options are simple on/off switches that save the moment you change them, confirmed with "Setting saved successfully".

The cards available in Company View are:

  • Order Manager — "Configure order time adjustment, delivery display, and printer settings"
  • Checkout — "Enable guest checkout and configure checkout behaviour"
  • Delivery Zones — "Enable route distance measurement and Google Maps integration" (Company View only)
  • Webhooks — "Register URLs to receive event notifications for this scope"
  • Customer — "Configure the information collected from customers upon registration" (Company View only)

Order Manager#

Settings for the Order Manager app that stores use to receive and process orders, applied across the selected company.

  • General

Disable Order Time Adjustment — stops staff from changing the preparation time when accepting an order. The tooltip explains: "Disable adjusting order time on the Order Manager app. Only default order time will be set". Display Customer Address for Outsourced Deliveries — shows the customer's address on orders handed to an external delivery provider.

  • Printer Setting

Hide Driver Tip on Receipt Hide Tip on Receipt

  • Table Booking Settings

Disable Table Bookings — switches off table reservations for the company.

Checkout#

Controls the checkout experience on the company's ordering website and apps.

  • Enable Guest Checkout — lets customers place an order without creating an account first.

Delivery Zones#

Company View only. Controls how delivery distance is measured when working out delivery zones and fees for the company.

  • Enable Route Distance Measurement on Google Maps — measures the distance a driver would actually travel instead of a straight line. The tooltip explains: "Measuring distance by route rather than a straight line".
  • Google Cloud API Token — appears once route distance measurement is switched on. Paste your token and click Save. The tooltip advises: "To measure distance by route we use the Google Cloud API. Please ensure that the Route API service is enabled in your Google Cloud account."

Webhooks#

Webhooks send automatic notifications to an address you provide whenever certain events happen, so your own systems can react in real time. In Company View, webhooks fire for events across the whole selected company. The table lists each webhook's Event, URL, Status (Active or Inactive), whether it is Signed, when it was last Updated, and its Actions. When none exist yet, the page reads: "No webhooks yet for this company. Add one to start receiving events."

Adding a webhook#

Click Add webhook and fill in:

  • Event — the trigger, chosen from events such as Customer created, Customer order created, Customer order accepted, Customer order on its way, Customer order completed, Customer order rejected, Customer order cancelled, Table booking created, and Table booking updated.
  • Payload URL — where the notification is sent. A secure https:// address is strongly recommended; an insecure address triggers the warning "Using http:// is insecure. An https:// endpoint is strongly recommended."
  • Signing secret (optional) — used to sign each notification so your system can verify it genuinely came from the platform. The form notes: "Optional. Used to sign the payload with HMAC-SHA256 so you can verify it came from us." On an existing webhook you can choose Rotate secret or Keep existing secret.
  • Active — pause deliveries without deleting the webhook.

Deleting a webhook asks "Delete this webhook?" and warns that events will no longer be delivered to that address and the action cannot be undone.

How deliveries work (reference)#

The page includes a collapsible How deliveries work panel for the technical team. In short: your endpoint should acknowledge each notification with an HTTP 200 response; anything else, or a timeout, counts as a failure. Failed deliveries are retried up to 6 times with increasing delays before being marked failed, and because delivery is at- least-once, your system should ignore duplicate notifications using the delivery identifier included with each one.

Customer#

Company View only. Controls what information the company collects from customers when they register, under Custom Form Fields. The on-screen note explains: "Specify the fields you would like to collect upon customer registration." Tick the fields you want on the registration form:

  • Age
  • Gender
  • Date of Birth
  • Area
  • Post Code