Amazon changed your report schema. Your dashboard just doesn't know it yet.
SP-API's flat-file reports have no OpenAPI spec — a differ can't see a column disappear. sp-api-drift can.
[BREAKING] column-removed: column "Status" is present in the lockfile but missing from the current report [warning] whitespace-changed: column "Merchant Shipping Group" whitespace fingerprint changed from clean to present 1 breaking, 1 warning finding(s) for GET_MERCHANT_LISTINGS_ALL_DATA
That's not hypothetical output — it's the shape of a real regression pattern from
amzn/selling-partner-api-models#5131
(buyerEmail dropped from the Orders API, open six months, zero release-note entry). Repricers,
FBA analytics, and accounting sync tools all pull the same flat files and none of them find out until
something downstream breaks.
Free today
A CLI that fingerprints a report's column set, order, type, and whitespace, locks it, and fails the next run if any of it silently moved. Point it at report files you already pull — it never touches your Amazon credentials.
npm install -g sp-api-drift sp-api-drift init --report-type GET_MERCHANT_LISTINGS_ALL_DATA --file ./reports/listings.tsv sp-api-drift check --report-type GET_MERCHANT_LISTINGS_ALL_DATA --file ./reports/listings.tsv
What's not built yet
The CLI only sees drift you've already hit, on files you already have. The next piece is a hosted feed built from opted-in fingerprints across accounts: is this column gone for everyone, or just you? That turns a lockfile check into an early warning — "column X vanished for 41% of observed accounts on Tuesday" before your own pull ever runs.
Not built. Not priced. If enough people want it, it gets built next.
Want the cross-tenant feed when it exists?
One email, no spam, no charge — just a note when it's ready to try.
Got it — you're on the list.