Ga naar de hoofdinhoud
Versie: 2.x

PAYMENT111: Payment recorded, till copy not saved

What this means​

Your store took this payment and it is on the order there. What failed afterwards was smaller: the till could not update its own copy of the order to match.

The money is safe and the sale is recorded. The payment pane already counts this payment in what is left to pay, but other views on the till — the cart and order lists — may lag until the till catches up, which is why the toast tells the cashier not to take the payment again.

WCPOS asks the store for a fresh copy of the order the moment this happens, so in most cases the till corrects itself within a few seconds.

Your data​

Money moved and your store has it. Never take this payment again — only the till's local copy of the order is behind, and the store's record is the one that counts.

Troubleshoot​

At the till — do this before the customer leaves:

  1. Do not take the payment again.
  2. Carry on from the balance the payment pane shows — it already counts this payment. Take whatever is still owed; if nothing is, the sale completes.
  3. Do not use the close button (X) to "reopen" the order. With a payment on it, closing opens Cancel payment, which gives money back rather than refreshing anything.
  4. If the till still looks out of date after the sale, open Store health → Database, open the ⋮ menu on the Orders row and choose Check for changes now.

On the store — for the site administrator:

  1. Nothing to repair on the store: it accepted the payment. The order in WooCommerce → Orders shows its current status.
  2. If a till repeatedly fails to save its own copy, check Store health → Database on that device — the storage used figure, and whether the device is low on free space. Its local database may be full or failing.

Details​

Code
PAYMENT111 (PAYMENT_RECORDED_NOT_MIRRORED)
Ernst
warn
Geïntroduceerd in
WCPOS 2.0.0