Skip to content
Sign InBook a Demo
Keep control · Business Continuity

When the internet goes, the shop keeps selling

The question is not what a till does on a good day but what it does at half past six on a Saturday when the connection drops. This one carries everything it needs on the terminal, sends the day up afterwards, and keeps going when one counter fails.

How it usually goes

The internet goes and the till goes with it, because the till was a browser tab. The queue stands there while somebody restarts the router, and the sales that happen in the meantime are written on a pad to be typed in later — or not.

When it comes back, the pad gets typed in twice, or an order that was half-sent gets sent again, and the day's figures carry a duplicate nobody finds until the drawer does not reconcile.

And with two counters, the second one is only useful if it can see what the first one started. If the connection between them runs through a server somewhere else, a bad afternoon for the connection is a bad afternoon for the whole shop.

Step by step

From a connected set-up to a day that does not depend on it

The cloud is where the day goes afterwards, not something the sell screen waits for. Each step below names what needs the internet, and what does not.

Step 01/ 07
  1. Customers

    Set the terminal up once, online

    First activation needs the internet. From then on the whole catalogue, taxes, service charges, coupon codes, staff, PINs and the full customer book are in a database on the terminal, in Point of Sale.

  2. Sell with the connection down

    Recording an order, a payment or a cash movement is written to the terminal first and needs no call to our servers. Staff PINs are checked on the device, so signing in is the same speed either way. There is no connectivity detector: the terminal simply keeps working locally and retries on a timer, about once a minute.

  3. Point of Sale

    Let the counters find each other

    Register the terminals once and they discover each other over your own network rather than through us. Open orders and the trading day are shared, so an order started at one counter is settled at another, while each terminal keeps its own cash drawer.

  4. Point of Sale

    Lose a counter, not the shop

    The terminals elect a coordinator between themselves and re-elect automatically if it disappears. Every counter carries its own copy of the open orders and the day, so a failure is a counter that stops rather than a shop that does.

  5. Send the queue up once

    When the connection returns, the records waiting on the device go up. Each carries its own identifier and the server matches on it, so a retry cannot duplicate an order or double-post a payment. A record the server rejects is kept and retried; one that has run out of retries is held on the device rather than thrown away.

  6. Point of Sale

    Settle what two counters both did

    If two counters manage to take the same payment, that is recorded and raised on screen for a person to settle. The software does not quietly reverse money on its own.

  7. Analytics & Reporting

    Close the day where you are

    The drawer is counted and the day's report — takings, payment mix, top items, sales by staff — is built on the terminal from what is on it, so closing does not wait for the connection either. The cloud catches up once the day has synced, and the business-wide dashboards in Analytics & Reporting read it from there.

    Workflow complete
Overview

The branch, once everything has synced

What the office sees after the tills reconnect: revenue and order KPIs, the trend and the top items — the same records the counters kept while offline.

The IMFlow360 overview dashboard, scoped to the current branch: revenue and order KPIs for the period, a sales trend chart, and top-selling items.
What changes

What changes

The queue moves whatever the router is doing

The catalogue, prices, staff and customers are on the terminal, and so is the order once it is taken. A dropped connection is something the person at the counter finds out about later, if at all.

Nothing typed in twice

What happened offline goes up when the connection returns, each record once, matched on its own identifier. The pad by the till can go.

Two counters that agree without a server

Open orders and the day are shared over your own network, with a coordinator the terminals choose between themselves. The second counter is useful precisely when the connection is not.

A failure with a known shape

A counter going down is a counter going down. The others keep the day, keep selling and re-elect, and a payment taken twice is a question put to a person rather than a silent correction.

A close that does not wait

The count, the variance and the per-counter report are built from the device, so the day ends when the shop does — not when the connection is back.

What it does not do

Worth knowing before a demo rather than after one.

  • First activation needs the internet, and so does signing back in after someone signs fully out. The offline claim is about a terminal that has been set up.
  • Voiding or refunding an order needs the cloud today, because the list of reasons is fetched from the server before the reason picker opens. That is a known issue; every other counter action records locally.
  • Offline means the internet. Several counters sharing a day and a tablet customer display both run over your own network, so that network needs to be up for those two things.
  • There is no connectivity detector. Recovery after a drop takes up to a minute rather than being instant, and a record that has run out of retries is held on the device for someone to go looking — the ones that matter most raise a warning on screen.
  • Cloud-side reports and the stock deduction for a sale happen when the order syncs, not at the moment of sale. Only the terminal's own day report is live while it is offline.
FAQ

Questions about this workflow.

What owners ask before they move a live business onto a new platform.

Can I void or refund a sale while the internet is down?

Yes. The IMFlow360 till keeps its list of void and refund reasons, so voids and refunds work offline once the till has been online at least once. Sales, payments, cash movements and closing the drawer all work offline too.

If one till goes down, do the other tills keep working?

Yes. IMFlow360 tills in a branch share open orders and the business day, and if the till coordinating them goes down another takes over within seconds. If two tills take the same payment during the handover, it's flagged on screen for someone to sort out.

Does a brand-new till work offline straight away?

No. A new IMFlow360 till needs the internet to be set up and signed in the first time, and again if someone fully signs out. After that, it keeps your services, prices, staff and client list on the till and sells without a connection.

How do I know every offline sale reached IMFlow360?

Each sale is sent once and matched, so retries never create duplicates. Anything the till couldn't send stays on the till and keeps retrying, and the important items show a warning on screen.

See it against your own work

The on-device database, idempotent sync, clustering with coordinator election, and the counted close in full.