It writes the fix. And it knows when not to.

A normal day

The day it goes wrong

Your warehouse API has a bad minute and returns an empty list. Nothing is broken in your business — the response is just wrong.

An ordinary sync tool cannot tell that empty list apart from a warehouse that sold everything, so it zeroes your shop. That has happened to real merchants across thousands of products at once. It is why most reconciliation tools stop at an email nobody reads — and it is the entire reason this one exists.

Everything it refuses to do

Eleven rules. Each has a code, so a refusal is something your systems can react to, not a note in a log. Five of them cannot be switched off — not by you, not for any price.

Refusals that stop the whole run

Refusals that stop one write

Setting it up

1. Tell it which system to believe. Your ERP, your warehouse, whatever holds the real number. Any endpoint that returns JSON.
2. Point it at Shopify. Four fields: your shop, an access token, a location, and where the quantity sits in your data.
3. Watch it for a few days. It starts in watch-only mode and repairs nothing. You read what it would have done. When you trust it, send the same call with "repair": true.

# 1. The system you believe
curl -X POST https://YOUR-HOST/api/v1/sources \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{ "key": "warehouse",
        "url": "https://wms.example/api/stock",
        "secret_headers": { "Authorization": "Bearer ..." },
        "records_pointer": "/items", "key_pointer": "/sku" }'

# 2. Shopify, the repair and the schedule, in one call
curl -X POST https://YOUR-HOST/api/v1/connectors/shopify \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{ "key": "stock-sync",
        "shop": "acme-supplies",
        "access_token": "shpat_...",
        "location_id": "12345678",
        "authoritative_source": "warehouse",
        "quantity_pointer": "/quantity" }'

# => { "mode": "watch_only", ... }

Being told

Nothing here expects you to sit watching a screen. Give it one URL and it calls you when a refusal saved you, when a source is unhealthy, when a check paused itself, and when a repair failed.

curl -X POST https://YOUR-HOST/api/v1/notifications \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{ "url": "https://ops.example/hooks/failclosed" }'

Signed with HMAC-SHA256 so you can verify the call came from us. Deduplicated per subject, so a source that has been broken since Tuesday is one message, not one every time the check runs.

When you do want to read a week yourself, the report page renders it from the key you already hold: how often the two systems disagreed, on which records, and whether anything was written.

Price

A 5,000-product catalogue checked daily, repairing 300 lines a month, costs about €16.50: €1.50 of watching and €15.00 of repairs. Prepaid from €25.00. No subscription, no seat fee.

What it cannot do

• It only knows what your endpoints say. If both systems agree on something wrong, it reports agreement.
• It compares snapshots. Two systems read seconds apart can disagree because something changed in between. A very short interval produces more of this.
• The repair is your request, sent by us. We do not know whether it is the right fix, only that you configured it and the rules allowed it.
• Only public https endpoints are reachable, by design.

API