Conflicts & errors

Swann Retail never silently overwrites your data. When a record can’t be synced cleanly, it’s recorded as a conflict for you to look at: sometimes the record still comes across and you decide what to do with it, sometimes the change is held until you act. Review conflicts under Sync health (managing them is owner-only).

Every conflict is Open until you act on it:

• Resolve — you’ve fixed the underlying problem (or it no longer applies).
• Ignore — the difference is intentional and you don’t want to be reminded again.

The conflicts you might see

Edited on both sides

The same record was changed in both Loyverse and Swann Retail between syncs. Swann Retail doesn’t overwrite either side — both records are left exactly as they are, and nothing syncs for that record until you decide. Check it, and if your Swann Retail change was the one you wanted, re-save it to push it across. Then resolve the conflict.

Can’t be fully represented

A Loyverse item uses a feature Swann Retail doesn’t model yet. The item is still imported — but that one feature isn’t carried across. This happens with:

• Variable / open pricing (price entered at sale time)
• Composite or bundle items (an item made of other items)
• More than one tax on a single item
• Modifiers (add-ons or options)
• Sold by weight
• Fractional stock counts

If you need that item represented exactly, simplify it in Loyverse; otherwise ignore the conflict — the item itself is there and selling.

Change rejected by Loyverse

Loyverse refused a change you made in Swann Retail — usually a duplicate SKU or a value Loyverse won’t accept. Fix the data in Swann Retail and save again. (Temporary network hiccups retry on their own; this conflict only appears when Loyverse actively said no.)

Duplicate customer

Two customer records share the same customer code, so they can’t be matched one-to-one. Use Merge customers to combine them — pick the one to keep, and the other’s details fold into it. See Importing your data.

Deleted customer couldn’t be detected

Loyverse doesn’t report when a customer is deleted, so Swann Retail can’t remove them automatically. If a customer was deleted in Loyverse, delete them in Swann Retail by hand to match.

If conflicts keep appearing

A steady trickle is normal during a busy side-by-side run. A sudden burst of the same kind usually points at one root cause — for example, a batch of Loyverse items that all use weight or modifiers. Fix the source and the new conflicts stop.