Stock Sync Auditor

Find the inventory-sync bugs that don't throw errors — before your accountant does.

What it does

You connected your ERP to Shopify/Amazon/Lazada. It's been running for months. It looks fine.

Then you oversell an item you had none of. Or month-end revenue doesn't match the settlement report and nobody can say why. You search the logs for the SKU and find nothing at all — not a failure, not a success. It simply never appears.

That's not a bug you can find by reading your code, because the code looks correct. This Skill finds it two ways:

1. Data audit — hand over three CSV exports (ERP stock, your SKU mapping, your channel listings). Get back the specific SKUs that are silently mis-syncing right now, ranked by severity, each explained.
2. Design review — a 13-point audit of your sync's architecture against the failure modes that survive code review: pagination that silently caps at page one, retries that duplicate invoices, reconciliation that structurally cannot see cancelled orders.

Who it's for

Ops leads, finance ops, and engineers running an ERP (Cin7 Core, NetSuite, Odoo, Unleashed, QuickBooks Commerce) against one or more sales channels — especially anyone who has ever had an accountant find something their integration didn't.

Why it's different

Every one of the 13 failure modes was found in a running production pipeline that had been "working" for months, then root-caused and fixed. This isn't a summary of vendor documentation — vendor docs are where several of these bugs come from.

The headline: an item's absence from an API response is not "no change", it is an unknown — and every integration that treats it as a no-op is lying to you right now. Nine of the thirteen traps are that one mistake wearing different clothes.

What you need

Three CSV exports. That's it.

No API keys. No credentials. No write access to anything. The Skill is read-only by design and never asks for a secret — if you paste one, it tells you to rotate it.

What you get

• Ranked findings naming the exact SKUs at risk, with the mechanism behind each
• The specific code change that fixes each class of bug
• A month-end reconciliation runbook — both directions, including the cancellation check that most gatekeepers structurally cannot perform
• Honest scope: findings are flagged as suspected, with the evidence that would confirm them. No invented findings to look busy.