Skip to content
FMX EPOS
Download
Help Centre home

Manage bookings in Cloud

When a store’s bookings are confirmed by Cloud, the Owner and the store’s Store Managers can manage them in FMX EPOS Cloud. The store needs the Restaurant Booking add-on in its Cloud licence. Without it, Cloud says “Restaurant Booking is not currently licensed for this store. Existing bookings remain available to view and transfer.”

When the store confirms its bookings on the till (Local confirmation), Cloud cannot change them or their settings. To choose who confirms bookings, see Configure bookings.

Seating guests and seeing them out happen at the till or the host stand. Cloud keeps no live table states: its timeline shows a table as taken only while a booking seated there still holds it.

Open the store, then Bookings under Store Settings in the sidebar.

  • At the top: Refresh, Print List (the whole chosen day, whatever the filters), Booking Settings and New Booking.
  • On the left: the business date with the arrows and, on another day, Back to Today; the day’s Bookings, To Come and Awaiting Approval; and the lists Awaiting Approval, Late, To Come, Arrived, Seated and Finished. Cancelled, Rejected and No-Show folds away below them.
  • In the middle: Timeline, List or Week, with area buttons, a search box (name, phone or email), and status and source filters.
  • On the right: the chosen booking with its actions, or the booking form.

To add a booking, select New Booking, or tap an empty slot on the timeline. Fill in Name, Guests, Start (UK Time), an optional End (Optional), Telephone or Email, the Table Arrangement (Automatic, a table or a combination), Reception Notes, Known Allergies and Allergy Details, then select Create Booking. Link an Existing Customer (Optional) with Find links a synced customer. To change a booking, select it, then Edit, and Save Changes. Dragging a booking on the timeline opens its form with the new time and table.

The form has three boxes for exceptions: Confirm a guest count outside the table’s range, Confirm going over the arrival guest limit, and Manager: confirm overlapping bookings on these tables, which needs a Reason for Overlap. An overlap asks Confirm Manager Overlap with the clashing bookings before it saves.

If you leave a form with unsaved changes, for another booking, a slot, a drag or another page, Cloud asks Discard Unsaved Changes?. Keep Editing goes back to the form.

The actions depend on the booking:

  • A request: Approve, Edit and Reject. Saving an edit confirms the request, even if you changed only a phone number, and the guest gets the confirmation email. While Open Online Bookings is off, Approve and Approve Change are refused: turn it back on, or reject the request. A change request: Approve Change and Reject Change, with the original arrangement kept until it is approved.
  • A confirmed booking: Mark Arrived, Edit, No-Show and Cancel Booking. Mark Arrived and No-Show are offered for today and earlier days only.
  • An arrived booking: Edit and Cancel Booking.
  • A seated booking has no actions in Cloud: confirm the party has left at the till or host stand.

Each action asks first, with a Reason (Optional). For Reject, Reject Change and Cancel Booking on a booking with an email address, the box reads Reason (Optional, Sent to the Guest), because the reason goes to the guest in the email, so write it for them. If Cloud’s answer is not confirmed, the page says “A request still needs a confirmed result.” Select Check Same Request before changing anything else.

The booking form says beside its save button whether saving emails the guest. When a booking has an email address, Cloud emails the guest each time Cloud changes it, including changes sent from the till: when it is made, changed, approved, rejected or cancelled, and when a request or a change request expires. An arrival or a no-show is emailed only with Email the Guest when Marked Arrived or Email the Guest when Marked No-Show ticked in the booking settings. A new store has the no-show email on and the arrival email off, and a no-show email leaves out the reason staff give. Seating recorded at the till sends nothing. See Emails and reminders.

Open the store’s Restaurant page and its Bookings tab, or select Booking Settings on the Bookings page. The Owner and Store Managers can change these settings. They are the same as in the Back Office (see Configure bookings), and here Online Tables opens or closes each area and table online and sets each table’s Online Minimum Guests. Select Save Booking Settings.

The tab also shows the Public Booking Link with its QR code and Download QR Code, and Booking Records with Export Complete Booking Records. The export holds guests’ contact and allergy details, so keep it private.

Sometimes the till records an arrival, a seating, a move or a departure after Cloud has already changed the same booking, for example after a guest cancelled online. Cloud then cannot apply what the till recorded. The till keeps its record and its table bill, and the Cloud Bookings page lists the booking under Till and Cloud Records Differ, with what the till recorded and what Cloud has.

  1. Check with the restaurant what really happened.
  2. Select Keep Till Record to make Cloud show the booking as the till recorded it, or Keep Cloud Record to make the till show Cloud’s version.
  3. Confirm in the dialog.

Either choice is recorded in the audit log and sends the guest no email. The table bill on the till does not change. Until someone settles it, the till’s Bookings tab also lists the booking under “The till and Cloud record these bookings differently.”

The Owner (or FMX EPOS support) can stop Cloud confirming bookings from the Recovery and Transfer card on the Bookings tab.

  1. Select Freeze for Transfer To Local, read Freeze Cloud Bookings? and confirm.
  2. On the connected till, open Back Office → Restaurant → Bookings and continue the same transfer there, so the till takes the final records and Local confirmation starts.

While frozen, online booking, guest changes and all booking changes in Cloud stop. Normal till sales carry on. Do not disconnect the store until the till has finished the handover. Usually it is simpler to start from the till with Transfer To Local (see Move booking confirmation).