Offline Mode
Learn how Eleo Edge handles printing and operations when the internet is unavailable.
One of the key benefits of Eleo Edge is its ability to continue operating when your internet connection drops. Edge’s local fallback path ensures that critical operations like receipt printing keep working even during outages.
How offline mode works
Under normal conditions, print jobs are routed through the Eleo cloud API (the “cloud path”). When Edge detects that the API is unreachable — due to an internet outage, DNS failure, or server maintenance — the Eleo Suite dashboard automatically switches to the “local fallback path”.
In local fallback mode, the browser communicates directly with Edge over your local network at http://localhost:21321. This bypasses the internet entirely, so printing continues as long as the browser and Edge are on the same machine (or local network).
The switch between cloud and local paths is automatic. You do not need to toggle anything — the dashboard detects connectivity issues and fails over transparently.
What works offline
- Receipt printing — Receipts can be printed using cached store data (name, address, logo). The logo is stored locally as a Base64 image during initial sync.
- Label printing — Labels can be printed using locally cached product data.
- Printer detection — Edge continues to discover and communicate with printers connected to the host computer.
What requires internet
- Remote printing — Printing from a device other than the one running Edge (e.g. printing from a tablet to a printer on a different computer) requires the cloud path.
- Device pairing — Pairing new devices requires communication with the Eleo API.
- Settings changes — Updates to receipt settings, store information, or station configuration require an internet connection to sync.
- Print job history — Viewing print job history and statuses in the dashboard requires the cloud API.
Reconnection
When internet connectivity is restored, Edge automatically reconnects to the Eleo platform:
- The WebSocket connection is re-established.
- Any queued outbound data (print job statuses, health reports) is replayed to the cloud.
- The dashboard switches back to the cloud path for subsequent print jobs.
- Local caches are refreshed with the latest data from the server.
Before relying on offline printing in a production environment, disconnect your internet and try printing a receipt. This verifies that Edge is running, your printer is properly configured, and the local fallback path is working correctly.
The local fallback path communicates over localhost. This means the browser sending the print job and the Edge app receiving it must be running on the same computer. If they are on different machines, you need internet connectivity for the cloud path.