SYNC221: Record conflict
What this means
A change on this device met a newer edit in your store. Nothing is lost.
If Store health → Database lists a held change for this record, tap Send again to keep this device's version, or Use server version to keep the store's. Otherwise, nothing to do — it has already been settled.
Your data
Nothing is lost. When a change is held, your store keeps its version and this device keeps its change until you choose which to keep; further edits to that record wait on this device until then. Don't clear this device's data while a change is held — clearing deletes the held change.
Troubleshoot
- Open Store health → Database. A held change is listed in a panel beginning "1 change was held" (or "… changes were held"), with the record it belongs to.
- If nothing is held for this record any more, it has already been settled — here or in another tab — and there is nothing to do. An order clash that WCPOS settles by itself, by sending this device's version again, is logged as SYNC222 instead.
- If a change is held, press Open record (where shown) to see this device's version, and compare it with the same record in WP Admin (a site admin may need to do this).
- To keep this device's version, tap Send again — the change is sent again and replaces the store's values for the fields this device changed. To keep the store's version, tap Use server version (some rows say Discard device change) and confirm — this device's change is dropped. Further edits to that record wait until you choose.
- Frequent conflicts on the same records usually mean two people edit the same data in parallel — for example stock on the till and in WP Admin. Agree on where each kind of edit happens.