Sync issues & how to fix them PRO APP
Offline sales are always recorded on the website, because the money was already taken. When something did not match — the total, the stock, a serial number, a plan renewal — the site saves the sale anyway and puts it on the Sync issues list for a manager. Sales the site truly cannot accept are rejected and stay on the device. This page explains each flag (needs_review, oversold_offline, serial_conflict, renewal_conflict, rejected and the register flags) and exactly how to resolve it.

The Sync issues list (site)#
| Column | What it shows |
|---|---|
| Actions | Open order (when an order was created) and Mark reviewed (while it needs attention). |
| Sale | Order number (link) and the app’s local number, e.g. D3-000004. |
| Device | Device name, offline when the sale was made offline. |
| Sold at | When the sale happened on the device. |
| Issue | Plain-language description (see below). Several issues are joined with “·”. |
| App total / Store total | What the app charged and what the order total is on the site. |
| Status | To review (amber), Reviewed (green) or the raw status (rejected / failed). |
The count next to the title is the number of open issues (sales + register events). Include reviewed also shows the ones already marked reviewed; Open issues only hides them again.
Who can see it: the same people who can open Settings → POS Apps.
Flags on saved sales — what each means and what to do#
needs_review — “Total differs from the store calculation”#
Why: the site recalculated the sale from its lines with its own tax engine and got a total that differs from the app’s by more than 0.01 — for example a price or tax rate changed on the site while the device was offline. The order is saved with the app’s total (that is what the customer paid); an “App total adjustment” fee line covers the difference and the order has a note.
Fix: Open order → compare prices / tax with what the customer paid. Usually nothing needs changing; if a price was wrong on the device, correct the product and press Sync now on the devices. Then Mark reviewed.
Variant: “Recovered after an interrupted upload — check stock and payments” — an upload was interrupted and the site finished it when the app sent it again. Check that stock and payments of the order are complete, then mark reviewed.
oversold_offline — “Sold offline without enough stock: …”#
Why: when the offline sale arrived, the location had less stock than was sold (two counters sold the last unit, or a stock adjustment happened meanwhile). The sale is still recorded because it physically happened — even if overselling is switched off — and stock may now be negative. Online sales keep the normal overselling rule.
Fix: count the product on the shelf. Correct stock with a stock adjustment or transfer, or receive the purchase that was not booked yet. Then Mark reviewed.
serial_conflict — “Serial / IMEI numbers sold offline could not be recorded: …”#
Why: the serial picked offline was no longer available (sold meanwhile on another device, moved to another location, invalid or used twice). The unit is sold without that serial; the order line and an order note name it.
Fix: find which physical unit the customer got. Correct the serial on the order / in Serial numbers, and fix the other sale if two receipts carry the same IMEI (warranty!). Mark reviewed.
renewal_conflict — “Plan payment for a cycle that was already paid — not applied twice …”#
Why: a mobile plan payment was taken for a cycle that is already paid — typically two counters took the same renewal while offline. The sale is saved, but the renewal is not applied a second time: due date unchanged, no renewal row and no commission. The receipt said “Renewal not applied twice – the shop will check it”.
Fix: ask the customer. If they paid twice by mistake, refund one payment (sell return). If they really wanted to pay one more cycle, record the renewal by hand in Mobile Plans. Mark reviewed.
activation_failed / renewal_failed — “Plan activation / payment sold offline could not be recorded — record it in Mobile Plans”#
Why: the activation or plan payment details of an offline sale were invalid on the site (e.g. missing customer or previous carrier, cancelled line). The line was sold as a normal product without the plan record.
Fix: create the activation (Mobile Plans → New Activation) or record the renewal by hand with the details from the sale, then Mark reviewed.
Rejected sales#
A rejected sale is shown as “Not accepted: <reason>”. Nothing was booked on the site (no order, stock or payment). In the app it stays under Pending / Sync → Sync issues with Retry and delete buttons.

| Reason (examples) | Typical fix on the site, then Retry in the app |
|---|---|
| Product not found / deleted | Restore the product (from trash), or delete the sale on the device and record it by hand with a replacement product. |
| location_not_allowed | The device no longer has that location, or the cashier lost access to it: re-assign the location (Edit device / Store Staff). |
| method_not_offline | A payment method was used offline that the site does not allow offline: enable it for the POS, or delete and re-record. |
| Discount above limit, price edit not allowed, register required, credit limit | Web POS rules for this cashier: adjust the permission / setting, then Retry. |
| mobileplans_forbidden | Give the cashier the Mobile Plans add / edit permission, then Retry. |
| card_txn_used / card_txn_invalid | The card payment was already used by another sale or is not approved. The app releases the card payment; choose another payment or void it on the site. |
| uuid_conflict | Same sale id from another device — never retried automatically. Contact support with the local number. |
Retry re-sends the same sale id, so the site still records it at most once. Delete removes it from the device and puts the stock back on the device — only when the sale did not really happen or you record it another way.
Offline cash register issues#

| Issue text (site) | Why | What to do |
|---|---|---|
| Expected cash differs — app X, store Y | When the offline closing arrived, the site recalculated the expected cash and it differs from the app’s figure by more than 0.01 (e.g. a sale was rejected, or a web-POS cash move happened in the same register). | Open register → compare movements with the counted cash; correct moves on the web if needed. Mark reviewed. |
| Opened offline while the cashier already had this register open — the offline session was added to it; check the opening float | The cashier already had an open register at that location (web POS / another app); the site adopted the offline session into it. | Check the opening float of that register. |
| Closed offline after the register was already closed — check the counted cash | The register was closed on the web before the offline closing arrived. | Compare the counted cash; correct on the web. |
| Not accepted: … (register_already_open, register_open_elsewhere, session_rejected…) | The event could not be applied. | Fix the register on the site; in the app use Retry, or Remove the event. |
In the app these appear under Cash register – flagged by the server (with Mark as seen) or under Sync issues (rejected events: Retry / Remove — “A manager should correct the register on the site.”).
Daily routine for managers#
- Open Settings → POS Apps; the Sync issues count shows open items.
- For each To review row: Open order → fix stock / serial / plan as above → Actions → Mark reviewed.
- For each rejected row: fix the cause on the site, then ask the cashier to press Retry on that sale in the app (or delete it if it did not happen).
- Check offline cash register rows against the register report.
Does “Mark reviewed” change the order?
No. It only removes the row from the open list. Make your corrections first.
Why was an offline sale accepted with negative stock even though overselling is off?
Because the goods were already handed over. Refusing it would hide a real sale. It is flagged instead.