Finocket keeps working when your signal doesn’t, up to a point, and the point is worth knowing before you walk into a basement godown. What you record is held on the device and sent when coverage returns. What you want to read is fetched fresh every time, so most screens can’t show you your own figures until you’re back on.
What works with no signal
- The app opens. Screens you’ve already visited are served from the device; anything else lands on a short offline page with the entry screens still on it.
- What you record is queued. Payments, expenses, visits and clients accept your entry with no network, hold it on the device with a visible badge, and send it in order when coverage returns (parents before children, so nothing lands orphaned).
- Nothing is dropped quietly. An entry that fails for a real reason rather than a network one stops retrying and is listed for you, with its error, instead of disappearing.
What still needs a connection
- Your figures. Lists, dashboards, reports and balances are read from the server each time you open them, so they can’t be shown offline, not even for something you recorded a minute ago on this same device.
- Anything the server decides: a number it issues, a return it files, a message it sends, a bank feed it reads, an answer Mysty works out.
A counter sale that won’t send
A sale you ring up at the counter with no signal is held on the device and billed the moment the signal is back, in the order it was rung. The till won’t let you close the register while any of them are still waiting. That money is in your drawer and not yet in your books, and a Z-report taken over it would be short.
If one of them is refused again and again, the till stops trying it after a few goes and puts it on a Held sales list, so the sales behind it go through instead of waiting on it. Open that list from the counter to see what each one is worth and the reason it was refused. You then have two choices, and only you can make them:
- Send it again once the reason is dealt with. It goes back in its own place in the queue and gets a fresh set of tries.
- Write it off, which removes it from the device without recording the sale. Your Z-report will be short by exactly that amount, deliberately, because you said so.
Nothing is ever thrown away on its own. A held sale stays on the device until you pick one of those two.
Invoice numbers while offline
Today an invoice raised with no signal is numbered the usual way once the device is back online. Your accountant may turn on a separate offline series for your business. If they do, each device numbers the invoices it raises from its own series, with a short device code in the prefix, so two devices do not normally hand out the same number. In the rare case that two devices drew the same code, the second invoice to reach the server is refused as a repeated number. Each number is used at most once on a device, and numbers are kept as they are when the device syncs. A number is taken as soon as you save, so an invoice that fails to save or is abandoned can leave a gap in that device’s run. If the saved numbering on a device is ever restored to an older copy, the device stops numbering offline instead of repeating a number, and needs resetting. That check cannot tell when the whole browser profile is restored from a backup: the database then refuses the repeated number when you save. This is off until your accountant has confirmed it suits your GST filing.
Where do I check sync health?
Settings → Offline sync shows what’s waiting, what failed and why, how much storage the cache uses, and whether your device has agreed to protect the queue from being cleared when space runs low. Installing the app makes that protection far more likely to be granted.