The pitch for product-sync automation is always speed. The reason shops hesitate is always the same quiet question: what happens when the feed is wrong? Supplier files break in mundane ways — a truncated export, a price column shifted one to the left, a decimal point in the wrong place. A fast sync without guardrails turns any of those into a store-wide incident.

These are the checks OhoSync runs on every sync, on every plan — they are not an upgrade.

1. The empty-feed stop

If a feed suddenly loses a large share of its products, the sync does not dutifully delete or hide most of your catalogue. The whole run stops and tells you why. Normal supplier churn — a few products coming and going — passes; a collapse does not.

2. Price guards

Two separate checks watch every price before it is written:

Change bands. A price that moves further than you allow in one step is held back. A €39 product that a broken export prices at €3.90 does not go live at €3.90.
Margin floor. A price that would fall below your minimum margin is held back, whatever the feed says. You never sell at a loss because of someone else's spreadsheet error.

Held-back products are reported with the reason, so a real price change you do want is one click from being accepted.

3. Preview before publish

Any sync can run as a test that produces the complete list of what would change — created, updated, hidden, held back — without touching the store. First runs can also be limited to ten or fifty products, so you check the result on a sample before committing the catalogue.

4. Locks around your own work

Fields you edited by hand — a rewritten description, a deliberate price, a better photo — can be locked, and updates flow around them. Publishing a product locks its content fields automatically. Your work is not an acceptable casualty of an update.

5. A record of every run

Every sync leaves a history entry: what ran, what changed, what was skipped or held back, and why. When something looks odd in the store, the answer is in the history, not in guesswork. A tool that writes to your live store should be answerable for every write.

What this adds up to

None of these checks is exotic. Together they change the failure mode: a broken supplier file becomes a stopped run and a plain-language explanation, instead of a store full of wrong prices. That is the difference between automation you have to watch and automation you can leave alone.

Written by OhoSync. Questions about your own supplier feed? Send it to us and we will tell you honestly whether it fits.