SYNC201: Record rejected
What this means
Your store refused this change, so it hasn't reached the store.
Read the store's reason. If Store health → Database lists the change, fix the record and tap Send again, or Discard it. If not, the store's version was restored — make the change again if it's still needed (see SYNC202). Nothing retries a refused change on its own.
Your data
Don't clear this device's data — it may hold changes your store doesn't have yet. A refused change that is listed in Store health → Database stays there until you send it again or discard it. A refused edit to an existing product, variation, customer or coupon is usually undone automatically and logged as SYNC202 instead. If it shows as this code and the change is listed in Store health → Database, the automatic undo didn't happen — treat it like any other listed change below. If this keeps happening, use Copy debug info on the Logs tab and contact WCPOS support.
Troubleshoot
- Read the store's reason — it is on the log entry, and on the change's row in Store health → Database.
- Open Store health → Database. If the change is not listed there, the store's version was already restored on this device and there is nothing to send — see SYNC202. Fix what the reason names, then make the change again if it's still needed.
- If it is listed — an order, a record created on this device, or a catalogue edit whose automatic undo didn't happen — the refused change is under "… changes never reached your server" with your store's reason on its row. Fix what the reason names on the record itself, for example a field on the order, while the change stays listed.
- Back in Store health → Database, tap Send again on that row. It rebuilds the change from what is now on this device and sends it.
- If the change is no longer wanted, tap Discard instead: the store's version is kept. Read the confirmation first — for a record the store never saved, discarding deletes it from this device.
- Site admin: if the reason says the user is not allowed to make the change, their role lacks that task — see AUTH201. If the reason mentions a field the POS does not show, open the same record in WP Admin — another plugin may add validation the POS cannot see. If it is still refused, use Copy debug info on the Logs tab and contact support.