Skip to content
FMX EPOS
Download
Help Centre home

Local, remote and Cloud operation

Local and Remote describe where the restaurant database is kept: on the till’s own computer, or on a database server the tills share. Cloud is a separate, optional service on the internet that the tills send data to. It does not hold the restaurant database.

In Local mode, one FMX EPOS installation keeps the restaurant database on its own computer.

  • With offline licensing, the till can trade without an internet connection. With Cloud licensing, it can trade offline within its grace period.
  • The local Back Office and printing do not depend on FMX EPOS Cloud. Card terminals and other payment services may still need their own connection to their provider.
  • Browser and Android staff devices still need a network connection to that till.
  • Other computers can open the kitchen screen and customer display in a browser from that till, once the matching switch is on in Local Settings → Security.
  • A second full till cannot use the local SQLite file as a shared live database.

Back up the data regularly. The simplest way is Automatic Backup in Back Office → Database, which saves an export file daily or weekly at a time you choose. You can also export the data yourself from the same page, or copy the whole installation folder after closing FMX EPOS, so the database is not copied while it is changing. See Database and maintenance.

In Remote mode, tills connect to a shared SQL Server or MySQL restaurant database.

  • Every till sees the same products, users, orders and settings.
  • The database server, its network and its backups are the restaurant’s responsibility.
  • The computer that holds the database needs a fixed IP address, so that the other tills can always reach it. Reserving its address in the router’s DHCP settings is usually the simplest way.
  • Windows on each till must treat the shop’s network as a Private network. On a network Windows treats as Public, the tills cannot reach each other.
  • The remote database is the restaurant’s permanent record. Automatic Backup in Back Office → Database can export it on a schedule. The database server’s own backups remain the restaurant’s responsibility.
  • Business data is shared, but each till keeps its own terminal settings, such as screens and printers.

FMX EPOS can keep supported billing going while the remote database is down. A till that is already signed in keeps its supported sales and sends them to the database, in order, once it is back. Nobody new can sign in on those tills until the database returns. The designated emergency terminal also takes emergency table bills and allows offline PIN sign-in. An administrator chooses that terminal in advance in Emergency Terminal under Back Office → Database → Terminals. Kitchen screens do not show emergency bills: their food goes to the kitchen on paper tickets only. Ordinary tills print no kitchen tickets until the database is back. See Choose the Emergency Terminal and Emergency terminal state.

While working this way:

  1. Follow the emergency or pending-sync status on screen.
  2. Do not try to copy a till’s waiting sales to another till.
  3. Do not enter an order again on another terminal just because it is not visible there yet.
  4. Get the remote database connection back as soon as possible.
  5. Before planned maintenance or moving the database, wait until no sales are waiting to sync.

An order taken on an ordinary till while the database is unavailable gets a long order number of 9 or 10 digits. Emergency bills on the emergency terminal use ordinary short numbers. Until the database confirms an order, its details show Pending Sync in place of the full order number. When the order reaches the database, it keeps its number unless another order that day already has it; then a letter is added, for example 3 becomes 3A. If you cannot find an order by the number on its receipt, look for the same number with a letter after it in Back Office → Orders (see Find an order).

Illustration, not a screenshot. The real screen can differ with the theme or version.

Cloud is an optional layer for management and customer services. Apart from store ownership and manager access, these services need the store to be connected and to use Cloud licensing; see Licences and licence modes.

Cloud can provide:

  • store ownership and manager access;
  • central sales, order, cash, tip, customer and audit views;
  • licence seats and optional add-ons;
  • catalogue publishing and coupon management;
  • selected store settings and staff changes;
  • customer websites, online checkout and QR ordering.

Cloud does not replace the local or remote restaurant database. If the Cloud connection fails, the till carries on with local work within its licence allowance. Cloud pages stop receiving new data, changes made in Cloud wait, and online or QR services that need the store’s connection may become unavailable.

One terminal acts as the Integration Host, the till that does the store’s background work with outside services. The Integration Host:

  • takes in new delivery platform orders, sounds the new-order alerts and shows the platform controls on its till;
  • releases scheduled table courses;
  • works out delivery routes;
  • keeps the store open to website, table QR and in-store orders, and receives them;
  • makes the automatic backup, when one is set up.

The computer that ran first-run setup takes the role to begin with. To move it to another terminal:

  1. Open Back Office → Online Platforms.
  2. Choose the terminal in Integration Host.
  3. Select Save Host. The page says “Integration Host saved. It takes over within a few seconds.”

Illustration, not a screenshot. The real screen can differ with the theme or version.

When no terminal is acting as Integration Host, online orders are not polled, scheduled courses are not released, no automatic backup is made and every till shows No Integration Host is running. See Online platforms.

Illustration, not a screenshot. The real screen can differ with the theme or version.

Keep that terminal:

  • running whenever connected services are offered;
  • connected to the restaurant database;
  • connected to the internet and FMX EPOS Cloud;
  • on the correct Windows time;
  • on a compatible Till version.

Cloud shows when the Integration Host and other terminals last reported in, but it cannot take live control of a terminal that is out of contact.

The browser mobile view and the FMX EPOS Android app connect to a till over the restaurant network. They do not go through Cloud.

  • The browser view needs trusted HTTPS and a live connection to the till.
  • The Android app pairs with one till.
  • Both need the Staff Mobile Ordering module and a switch in Local Settings → Security on that till: Till Web — PC, Mobile & Customer Display for the browser, Mobile App for the app. See Security and network access.
  • Neither can complete orders while the till or the restaurant database is out of reach.

See Browser staff ordering and Android staff app.

Need Suitable arrangement
One till, no shared database Local SQLite
Several full tills sharing live restaurant data Remote SQL Server or MySQL
A separate PC running FMX EPOS just for a kitchen screen or host stand Remote SQL Server or MySQL
Staff taking orders on phones or tablets in the restaurant Browser mobile or Android app connected to a till
Central reports and management from outside the restaurant Optional FMX EPOS Cloud connection, with Cloud licensing
Customer website, collection/delivery checkout or customer QR Cloud licence mode with the required add-on, the site or channel set up, and a running Integration Host

These can be combined. For example, a store can use a remote MySQL restaurant database, Cloud reporting and several Android staff devices. Each layer has its own connection and can fail independently. When something stops working, check which layer has the problem before assuming it is Cloud.