Connect, transfer or release a store
Connecting links one restaurant database to a store in FMX EPOS Cloud. The Owner usually claims it with a one-time code from the till’s Licence page.
Before you connect
Section titled “Before you connect”Check that:
- the person claiming the store has an active Owner account, or creates one with the code (see Cloud accounts);
- the Owner has not reached their store limit;
- the till can reach FMX EPOS Cloud;
- the Windows clock is correct;
- you are signed in on the till as an Administrator;
- if the store will take website or QR orders, the Integration Host till can stay running, because it keeps that ordering live.
Use another cloud server
Section titled “Use another cloud server”Most shops never need this: it is for a server your supplier gives you. Before you connect, enter the server’s full address in Server under Cloud Licensing, then select Connect to Cloud. The till saves the address for every till in the store and gets the code from that server. Leave Server blank to use FMX EPOS Cloud. While the store is not connected and no code is showing, a till set to another server offers Use Default Server, which goes back to FMX EPOS Cloud. You cannot change the server while the store is connected, so switch to offline licensing first. Once the store is connected, the card shows the server in its details: FMX EPOS Cloud, or the address followed by custom.
Claim the store
Section titled “Claim the store”- On the till, sign in as an Administrator.
- Open Back Office → Licence.
- Under How This Store Is Licensed, select Cloud Licensing, then Connect to Cloud. The card shows an eight-character code in two groups of four, the time left and Waiting for the store to be claimed…. If a code is already showing, select Get a New Code only if you want to replace it.
- Sign in to FMX EPOS Cloud as the Owner.
- On the Stores page, find Claim a Store.
- Enter the code under Pairing Code, with or without the space. Give the store a clear Store Name, or leave it blank to use the shop name from the till.
- Select Claim Store. Cloud says Store claimed. Its till picks up the connection within a few seconds. If the store gets a Cloud trial, the message gives its end date.
- Go back to the till. You do not need to reload the page. The card shows Connected with the store’s name, the store moves to Cloud licensing by itself, and the till says Connected to Harbour Kitchen. The store now uses cloud licensing.
How This Store Is Licensed
Applies to every till in this store.
Illustration, not a screenshot. The real screen can differ with the theme or version.
- If the store has no Cloud licence it can run on, the till says Connected to …, but cloud licensing did not start: with the reason, and the store stays connected on its offline licences. Once the licence is in place, select Use Cloud Licensing on the same card.
- Open the store in Cloud and check the licence, the running tills and the first data sync.
The code works once and expires after ten minutes, and a new code replaces any older one. If the code expires, the till says The code expired. Get a new one. If Cloud says the store was claimed but the till never shows the connection, get a fresh code and claim it again, so that the till receives new connection details.
If Claim Store is refused:
| Cloud says | What to do |
|---|---|
| This code is not valid. Codes work once, for ten minutes. | Check the code on the till. If it has gone or expired, get a new one. |
| Your account may have … stores. | The account has reached its store limit. Contact FMX EPOS support. |
| This store belongs to another owner. | Another Owner has claimed this restaurant database and has not released it. Contact FMX EPOS support, who can move the store. |
If the store cannot have a trial, Cloud still claims it and says why.
The first connection can upload a snapshot of earlier business history. Cloud pages can be incomplete until that snapshot and the syncs after it have finished.
Rename the Cloud store
Section titled “Rename the Cloud store”The Owner can rename the store under Sales Settings → Shop Details: change Store Name on the Cloud Details card and select Save Cloud Details. The name appears on Cloud pages, in customers’ order emails and on the customer websites. The shop name the till prints stays as it is.
Release a store
Section titled “Release a store”Only the Owner can release a store. Release happens in two stages, so that no customer payment is left half-finished.
If Cloud confirms the store’s bookings, move booking confirmation back to the till first, with Transfer To Local in Back Office → Restaurant → Bookings (see Move booking confirmation), and let the till receive the last booking and table changes. Until then Cloud refuses the release with Move booking confirmation back to the till first, or says The till is still receiving the booking transfer or table changes.
- Export the store’s reports first if you need them (Reports → Export CSV). Afterwards the store is read-only in Cloud.
- Open the store’s Store Overview page and find the Release Store card.
- Make sure the restaurant knows that its connected services will stop.
- Select Release Store, read the warning and select Release Store again, or Keep Store to cancel.
- Cloud stops new customer orders at once and ends orders that the store has not accepted yet. If nothing else is waiting, the release finishes straight away and Cloud opens the Stores page, where the store shows Released.
- If something is still waiting, Cloud says New orders are stopped. Release is waiting for: and lists each item with how many there are, for example a card capture still being checked, a card authorisation awaiting release, a refund awaiting Stripe, an accepted order the till has not imported, or a member reservation the till has still to release. The store shows Release Pending on the Stores page, and its tills stay connected so this work can finish.
- Resolve each item where the message says, mostly under Online Ordering → Needs Attention in Cloud and in the till’s online orders. Then select Finish Release and confirm with Finish Release.
Release Store
Stop new customer orders, finish pending transactions, then disconnect its tills.
Illustration, not a screenshot. The real screen can differ with the theme or version.
While the release is pending, Resume New Orders cancels it and lets customers order again. Orders the release has already ended stay ended. If the till can no longer finish its part, contact FMX EPOS support. Payments, refunds and payment checks still have to be resolved first.
When the release finishes, the store loses its till seats, Cloud ordering stops and Cloud accepts no further sync. Each till picks up the release the next time it reaches Cloud and goes back to offline licence mode, and its Licence page offers Cloud Licensing and Connect to Cloud again. A till without its own offline licence cannot start new sales. The store shows Released and stays as a read-only record for the Owner until it is deleted: its pages can still be read, but nothing can be changed. Its website turns read-only too. The Owner can still disable or delete it, but cannot enable it again until the store is claimed. Local orders stay in the restaurant database.
To reconnect the same restaurant database, get a new pairing code on the till and claim it again; an old code cannot be reused. When the same Owner claims it, Cloud brings back the released store with its records, and the store counts towards the Owner’s store limit again.
Any other Owner who claims the released store with a new pairing code from its till takes it over. They get the store’s Cloud record, including its synced orders, customers, menus and coupons, and the store leaves your Stores page. Your Store Managers, its Cloud licence, its Customer Email, its website and its Stripe connection do not pass to them. If the store’s history must not go to anyone else, delete the released store.
Delete a released store
Section titled “Delete a released store”Once a store is released, its Owner can delete it from Cloud for good. FMX EPOS support can also do this. Store Managers cannot.
- Export the store’s reports first if you need them (Reports → Export CSV). Nothing can be restored afterwards.
- Open the released store’s Store Overview page and find the Delete Store card.
- Select Delete Permanently.
- Type the store’s name exactly as shown under Type the store’s name to confirm. Delete Permanently stays unavailable until the name matches.
- Select Delete Permanently to confirm, or Keep Store to cancel.
Illustration, not a screenshot. The real screen can differ with the theme or version.
Cloud then opens the Stores page. A store that has not been released has no Delete Store card: release it first.
Deleting removes everything Cloud holds for the store: its synced orders and reports, menus, coupons, customer orders, pictures, Store Managers’ access to it, its licence, its Stripe connection and its own website with that site’s pages, pictures and domains. FMX EPOS keeps a record in its activity log that the store was deleted. AI assistant connections that named the store no longer find it.
The tills are not touched, and local orders stay in the restaurant database. If the restaurant connects its till to Cloud again with a new pairing code, Cloud makes a new store with none of the deleted store’s data.
Switch to offline licensing
Section titled “Switch to offline licensing”An Administrator can also end the connection on the till.
While Cloud confirms the store’s bookings, the till refuses with This till must confirm the store’s bookings first. Use Transfer To Local in Back Office → Restaurant → Bookings first. Booking requests and arrivals still waiting for Cloud must reach it too, so keep the till online until they have gone.
- Open Back Office → Licence.
- Under How This Store Is Licensed, select Offline Licensing, then Switch to Offline Licensing.
- Read Switch to Offline Licensing?, including what happens to this till, then select Switch to Offline Licensing, or Keep Cloud Licensing to cancel. The till says Disconnected from FMX EPOS Cloud. The store now uses offline licensing.
Switch to Offline Licensing?
The store disconnects from FMX EPOS Cloud. Every till then needs its own offline licence; a till without one cannot start new sales. Cloud orders and sync stop.
Local orders are kept. Pending cloud sync records are cleared. Reconnecting uploads all data again. The cloud store is not deleted.
This till: keeps trading on its offline licence (until 31/12/2026).
Illustration, not a screenshot. The real screen can differ with the theme or version.
After you switch:
- every till in the store goes back to its own offline licence, and a till without one cannot start new sales;
- Cloud orders and sync stop. Local orders are kept, but changes not yet synced are not sent. If the store connects again later, everything is uploaded again;
- Cloud is not told. The Cloud store, its licence and its records stay as they were.
To connect again, select Cloud Licensing on the Licence page, get a new code and claim it in Cloud.
Switch to offline licensing or release?
Section titled “Switch to offline licensing or release?”| Switch to Offline Licensing | Release Store | |
|---|---|---|
| Where | Till, Licence page | Cloud, Store Overview page |
| Who | A till Administrator | The Owner |
| The Cloud store | Unchanged; Cloud still lists it | Stops new orders, waits for open payments, then becomes a read-only record; its tills lose the connection |
| Use it when | This restaurant database should stop using Cloud, for example before you move the database | The store is leaving that Cloud record |
If the restaurant is leaving Cloud for good, ask the Owner to release the store first, so that open payments are settled and the Cloud record is closed. Switch the till to offline licensing only if it does not pick up the release by itself.
Transfer a store to another Owner
Section titled “Transfer a store to another Owner”Only FMX EPOS can move a store that has not been released to another Owner, so contact FMX EPOS support. Owners and Store Managers cannot do it themselves. Ask the current Owner to export the store’s reports first.
A transfer works like this:
- The tills stay connected, and the store keeps its licence and till seats.
- The old Owner and their Store Managers lose access.
- The old Owner’s website, Stripe connection, Customer Email and changes still waiting for the store do not move to the new Owner.
- Website orders still waiting for the store to accept them, or for payment, are ended, and any card authorisation on them is released.
- A payment already in progress can still complete on the old Stripe account.
- Earlier online payments can no longer be refunded from the till once that payment account is removed.
- Printed table and in-store QR codes stop working until the new Owner sets up a website and new codes.
The new Owner should set up the replacement website, payment connection, staff access and channel settings before reopening online ordering.
If a claimed store does not sync
Section titled “If a claimed store does not sync”- On the till’s Licence page, check that Cloud Licensing shows In Use, and that This Till shows Licensed or No Seat. A till waiting for a seat can still carry the sync. Any other state, such as No Cloud Licence or Expired, stops it.
- Check that at least one till on the Cloud licence is switched on and can reach both the restaurant database and Cloud. Any such till can carry the sync; it does not have to be the Integration Host.
- On the till, open Back Office → System Settings → Cloud and read Last Error.
- In Cloud, open the store’s Store Overview page. Read any Store sync problem notice at the top, and check Tills and Platforms. While the first upload runs, a notice at the top of each store page shows how many tables are done.
- Fix the connection or licence problem shown and let the next sync run.
Do not release and reclaim a store to reset the sync. Releasing closes the store’s Cloud record and stops its connected services.