How POS sync works and how to clear Sync Problems
Sell offline and the POS holds each sale in a local outbox, then syncs it to the server in the background when the connection returns — you don’t wait and you don’t re-enter anything. If a sale is permanently rejected by the server (rare — e.g. it references something that changed), it isn’t lost: it moves to the Sync Problems screen with an alert badge, where you can retry or discard it. No offline sale ever disappears silently.
Step by step
- Sell offline as normalPOS (Android/Sunmi): complete sales with no internet. Each is saved locally and queued in the outbox with a pending count.
- Let it sync in the backgroundWhen you’re back online the POS uploads queued sales automatically — no action needed. See Offline POS and how sync works.
- Watch for the Sync Problems badgeIf a sale is permanently rejected, a badge appears and the sale is listed under Sync Problems, decoded so you can see what it was.
- Retry or discardTap Retry on a sale (or Retry all). If it succeeds you’ll see “Sale synced.” and it clears; if it still can’t sync it’s “kept for review.” Use Discard only when you’re sure it shouldn’t post.
Why a review queue beats a silent failure
Cheaper POS systems either lose a rejected offline sale or freeze the whole queue behind it. RushFlow separates the two: good sales sync, and the rare rejected one waits for a human decision in Sync Problems — so one odd sale never blocks the rest, and you never quietly lose revenue.
Frequently asked questions
Where do my offline sales go?
Into the POS outbox, which uploads them to the server automatically when you reconnect. You don’t re-enter anything.
What happens if the server rejects an offline sale?
It moves to the Sync Problems screen with an alert badge, decoded for review. You can retry it (or retry all), or discard it — it’s never silently dropped.
Ready to run your business on RushFlow?
Start a free trial, or explore the live demo — no credit card needed.
Create your account →