The Power Goes Out. You Keep Selling.
SaleSprint is built offline-first, not offline-tolerant. The device holds its own database, writes go into an outbox, and the outbox drains the moment connectivity returns. Selling never waits on the network.
A Database on the Device
The working set — products, prices, customers, open documents — lives locally. Screens read from the device, so they load whether or not there is a signal.
Outbox Sync
Every write goes into an outbox first. When the connection comes back, the outbox drains automatically — in order, without anybody pressing a “sync now” button and hoping.
One App, Six Platforms
Windows, macOS, Linux, Android, iOS and the web from a single codebase. The same screens, adapted per form factor — not a cut-down mobile version of a desktop product.
Receipts That Print
Thermal and A4 printers, several layouts, barcodes and QR codes, and print preferences saved per device — so each till behaves the way its operator set it up.
Sessions Cached
A device that boots without a network still knows who its user is and what they may do. Permission and plan changes live-refresh as soon as it reconnects.
Automatic Updates
The app checks a per-platform release manifest and offers the update — or requires it, when a security floor demands — using the right mechanism for each operating system.
Six targets, one product
A phone forks the layout but shares the logic with the desktop. That is why a feature does not arrive on one platform months before the others — there is only one build to ship.
Windows
Counter and back office
macOS
Owner and manager desktops
Linux
Low-cost till hardware
Android
Phones, tablets and handhelds
iOS
iPhone and iPad floor staff
Web
Any browser, nothing to install
Installers for every platform live on the downloads page.
What “offline-first” actually means here
Plenty of cloud POS products are websites with a spinner. In a market where the power and the network both go out, that is not a product — it is a promise you cannot keep on a Friday evening. SaleSprint inverts the order: the device is the source you work against, and the server is what it reconciles with.
Reads hit the local database
Catalog, prices and customers are already on the device.
Writes queue in the outbox
The sale completes and the receipt prints; delivery is the app's problem, not the cashier's.
The drain is automatic
Connectivity returns, the queue empties, the books catch up.
Permissions survive the blackout
Cached sessions mean a cold boot with no signal still enforces the rules.
Printing, properly
A thermal slip and an A4 invoice are not the same document, and pretending otherwise produces receipts nobody can read. SaleSprint treats them as different outputs from the same sale.
- Thermal and A4 layouts, several designs each
- Barcodes and QR codes on the receipt
- Print preferences stored per device
- The same document also exports to PDF
Updates that reach the tills
Devices in shops drift. The app checks a per-platform release manifest and handles the upgrade itself, using whatever each operating system expects.
- Optional updates are offered, not forced
- A security floor can require the upgrade
- Google Play in-app updates on Android
- App Installer on Windows, Sparkle on macOS
- The store on iOS, a reload on web
Try it with the Wi-Fi off
Install SaleSprint on the device you already have, unplug the router, and sell a few items. That is the demo.