E-BON App

Work offline and check connection health

Keep ringing up sales when the network drops. Learn what the header cloud icon means, how to read printer status, and what to do when something goes red.

Work offline and check connection health

If you have ever wondered what the cloud icon in the app header is telling you, this page is for you. It answers the three questions every operator asks the first time the network drops: what does the badge mean? are my receipts lost? when will it come back?

Recognize the two connections

The app cares about two connections, and they fail independently.

Connection	Where you see it	What it affects
Cloud link — between the app and e-bon servers	The cloud icon in the app header (grey `cloud-off`, green `cloud-done`, or amber `cloud-queue`)	Whether commands sent from the Portal reach this device.
Printer link — between the app and the fiscal device (AMEF)	The colour badge next to each device on the Devices tab — `Online`, `Busy`, `Warning`, `Error`, `Offline`	Whether this app can issue commands to that printer.

The two badges can show any combination. "Cloud reconnecting + printer Online" is normal during a quick mobile-data blip. "Cloud Connected + printer Offline" usually means a Bluetooth, USB or power problem on the device — not a network problem.

Read the cloud status icon

The cloud icon lives in the app header on every screen. Its shape and colour track the cloud link:

Grey crossed-cloud (cloud-off) — you are in Standalone mode (not signed in). There is no cloud link, by design.
Green cloud with a tick (cloud-done) — Linked and live. This is the normal signed-in state.
Amber cloud (cloud-queue) — Reconnecting: you are signed in but the live link is momentarily down and the app is dialling back.

A small count bubble appears on the icon when receipts are still waiting to sync to the cloud — the number is how many are unsynced, and it disappears once everything has synced. The icon also gives a quick pulse when a command arrives from the cloud.

The icon is informational. There is no "tap to retry" — recovery is automatic and usually takes less than a minute.

Keep selling while the cloud is down

Losing the cloud — or never signing in at all — does not stop the till.

The fiscal printer is local. Keep ringing up sales as usual — the receipts print, get stored on the device, and sync to the cloud when the network returns (or when you eventually sign in).

The app is offline-first by design. Everything that matters at the counter works without any cloud account:

Issuing fiscal receipts on the printer in front of you.
Running X reports and Z reports. The CUI lives inside the AMEF itself, so reports never need the cloud.
The ANAF journal — local fiscal activity is recorded on this device.
Pairing, unpairing and managing printers at this device's active location (the local Standalone sentinel when signed out, or a real location when signed in).
Browsing and reprinting recent receipts.

What changes while the cloud is unreachable (or you have never signed in):

Receipts on the printer in front of you: unaffected. Print as usual.
Commands sent from the Portal (a colleague pressing "Print receipt" remotely, an integration call): only relevant once you have signed in. If you are signed in and the cloud drops, queued commands wait for the link to come back; anything not delivered within 3 minutes is marked failed in the Portal and can be re-sent.
The count bubble on the cloud icon: this is how many receipts are still waiting to sync to the cloud. Once the link is healthy they upload in the background and the bubble clears to nothing; while the cloud is unreachable the number simply holds until it returns.

Reconnect after a dropout

You don't have to do anything — the app retries on its own with a growing wait between attempts (1, 2, 4, 8, 16, 30 seconds, then once every 30 seconds until it gets through). Most short blips clear up within a minute.

Two cases need help from you:

After signing out, the cloud stays disconnected

That's expected and harmless — the app only talks to the cloud when someone is signed in. Standalone use does not need a cloud link at all; the icon simply shows the grey crossed-cloud. Signing back in from Settings re-opens the connection and automatically re-links any local printers and receipts to your organization.

Your session was rejected. Sign out and sign back in. See Sign in to cloud.

While e-bon is in the foreground it keeps a single long-lived secure connection to the cloud and receives updates live. When you switch to another app, e-bon closes that connection on purpose to save battery. If something needs delivering — a remote command, a Portal action — the server sends a silent push notification that only wakes the app up; the actual command is fetched over the reopened connection. On reconnect the app first drains any commands that were queued on this device, then catches up on anything it missed before returning to live updates.

Curious how this works under the hood? See Architecture overview and the developer-facing Realtime getting started page.

Read the printer status badge

Each device on the Devices tab shows a coloured badge:

Badge	Meaning	What to do
Online (green)	The printer is reachable and idle.	Nothing — this is the normal state.
Busy (blue)	A command is running on the printer right now.	Wait for it to finish.
Warning (yellow)	One ping to the printer failed.	Wait one more cycle (30 seconds). It usually clears on its own.
Error (red)	The printer reported a problem (paper out, drawer open, fiscal error).	Open the device, follow the on-screen instructions.
Offline (grey)	Three pings in a row failed. The app will try to reconnect on its own.	If it does not come back within a minute, check the cable, Bluetooth pairing, or power.

Common causes of a printer going Warning or Offline:

Bluetooth was unpaired or the phone was out of range.
The USB cable was unplugged.
A network printer was powered off or its network cable was unplugged.
The paper roll ran out mid-print.

Match symptoms to actions

What you see	What it means	What to do
Amber cloud-queue icon	The cloud dropped briefly.	Wait. Keep selling. It usually clears in under a minute.
The count bubble persists more than 2 minutes	Receipts have been waiting to sync longer than usual.	Check phone connectivity (mobile data on, Wi-Fi connected). See Troubleshooting.
Cloud stays disconnected right after sign-in	Your session was rejected.	Sign out and sign back in. See Sign in to cloud.
Header is green but a printer shows Warning then Offline	Problem with the printer link, not the network.	Check Bluetooth pairing, cable, and printer power. See Devices.
The cloud icon is amber and a printer row is red	Both links are down — most often the phone has lost network.	Keep printing receipts. Everything will sync when the network is back.

Where to next

Devices tab — manage printers and read their status.
Operations — what you can do from the app.
Sign in to cloud — optional, lives in Settings; recover after a rejected session here too.
Troubleshooting — symptom-by-symptom recovery.

Installing on Android

Install the E-BON Android app, grant the Bluetooth and location permissions needed for fiscal printers, and take the first-launch tour. Cloud sign-in is optional and available later from Settings.

Device detail

Inspect a single fiscal printer — check cash balance, run X and Z reports, edit fiscal settings, and review the command history for that device.