Internet down. Still printing. Still taking cash.
Reamstead keeps the counter trading when the cloud is unreachable: queued and cached jobs keep printing, staff keep taking money locally, and every one of those actions syncs exactly once when the line comes back. Card and wallet are the honest exception, and we say so on this page rather than in a footnote.
Cash · voucher · account credit · deferred, all taken with the line down

What the appliance does between the line dropping and the line returning
Outages are not hypothetical in every market we sell into. Jamaica lost power island-wide in June 2026, and in plenty of places the backhaul flickers weekly. The appliance is built for the counter to carry on without anybody making a decision about it.
- 01
A failure, or the event channel drops
The appliance moves to DEGRADED. The cloud is still reachable over HTTPS, so jobs still arrive, but they are collected by polling instead of being pushed. Nothing changes at the counter.
Failures inside 60 s
- 02
No contact for 90 seconds
It switches to offline operation and says so on the console, in red, across the top of every screen. A DNS failure skips the wait entirely: with no name resolution there is no cloud to hold out for.
The cloud marks the appliance OFFLINE after 90 s with no heartbeat
- 03
The counter carries on
Staff sign in with their PIN, take a walk-in job from a machine on the shop network, price it from the cached rules, take the money, print it, and reprint a cached job if a copy is spoiled. Every consequential action is written as an immutable event before anything else happens.
- 04
Money is counted while it is offline
The console shows what has been taken locally and not yet reconciled: unsynchronised events, the cash total and the deferred total. A refund given during an outage is always flagged for review, because cash left the drawer with nobody to authorise it.
- 05
The line returns
Two consecutive successful probes with the event channel back up, and the appliance calls itself online again. One lucky packet is not a recovery, so a flapping link reads as degraded, which is what it is.
Recovery probes: 2
- 06
Everything syncs, once
The outbox is drained oldest first in batches of up to 500 events. The cloud acknowledges each one, recognises anything it has already seen as a duplicate, and sends anything genuinely ambiguous, such as a job paid twice by two routes, to a review queue for a person to settle rather than guessing.
90seconds
How long the appliance waits before it stops waiting
Ninety seconds without a successful exchange and it switches to offline operation rather than leaving your staff wondering. The outbox is an fsync'd SQLite table, so a payment that reached the drawer survives a power cut as well as an outage: the machine comes back up with the event still queued.
What keeps working, and what needs the line
The second column is the one worth reading. Pretending card payments work offline would be the fastest way to lose your trust on the first outage, so they are listed where they belong.
Keeps working
- Printing
- YesQueued jobs and any cached job still inside its retention window
- Counter intake
- YesPDF or image from a machine on the shop network
- Pricing
- YesCached rules, the same engine the cloud prices with
- Cash
- YesChange calculated on the console
- Voucher
- Yes
- Account credit
- Yes
- Deferred
- YesOn account, where the tenant allows it
- Reprints
- YesA new attempt with its own id
- Operator sign-in
- YesPIN hashes are cached, so sign-in does not need the cloud
- Printer management
- YesState, test page, re-detect
Needs the line
- Card payment
- NoThere is no invented offline card path
- Wallet payment
- NoIt goes through the same provider as card
- New jobs from a QR sign
- NoThe upload goes to the cloud, so the customer waits or the counter takes the file
- Jobs never cached locally
- NoThe document has to be on the appliance to print
- Portal and reporting
- NoFigures resume when the events sync
- Configuration changes
- DeferredThe cloud is authoritative; the cached configuration is used until it returns
Offline card authorisation is enabled only where the payment provider and a certified terminal genuinely support store and forward. Plan on no.

Tell us how often your line drops
If outages are a monthly event where you trade, this is the page to bring to the conversation. We will go through which tenders you would want enabled at the counter and what your exposure would look like during a long one.
offline operation · the counter keeps trading