About this plugin
A dry run with a receipt. Point it at a supplier feed, a marketplace export,
or the CSV you were about to import, and get a line-by-line account of the
difference between that file and your WooCommerce catalogue: which SKUs are
missing on each side, where the quantity disagrees, where the price disagrees,
and what the file does not let us decide. Nothing is written to your store.
It exists because the usual way to discover a failed inventory sync or a bad CSV
import is by accident — a customer asks why something shows out of stock, a
product quietly disappeared, or a charge turns up on a card statement weeks
later. After a sync error or an import error it tells you what actually changed;
before the next one runs, it tells you what would. It is built for checking a
supplier feed, a dropship price list or an ERP export before you trust it with
your live stock levels.
What it finds
- Missing SKUs — rows that exist in the file but not in your store, and
products in your store that the file never mentions.
- Quantity mismatch — stock levels that disagree between the two sources.
- Price mismatch — prices that disagree, compared as regular price, sale
price, or “effective” price (sale price where present, otherwise regular).
- Silent reversion — a value that is back to something it held in an earlier
run of the same audit, which is what a half-applied or rolled-back sync
usually looks like afterwards.
- Rows that cannot be decided — reported as undecidable, never guessed.
When to use it
- Before a product import from a supplier CSV, to see what that import would
change.
- After a stock sync that looks wrong, to see what actually differs right now.
- When a product feed or marketplace export starts overwriting your prices.
- When stock levels drift, to get the exact list of SKUs that disagree instead
of just knowing something is off.
- As a recurring stock reconciliation: run the same inventory audit every month
as part of your inventory management routine, and let the revert detection tell
you whether anything moved back.
What it refuses to do
These are deliberate, and they are the point:
- It never silently skips a row it cannot parse. A value that is present but
unreadable — abc where a number belongs — is listed under FAILURES and the
run is marked as untrustworthy.
- It never picks a winner when a SKU is duplicated. Choosing one would hide
exactly the corruption you went looking for.
- It never claims a row is “missing” when the other side failed to load
completely. Those rows are reported as cannot be asserted.
- It never invents a number. An empty quantity or price means unknown: the
row is still matched by SKU, it is not compared on that field, and the count
is stated under Notes. Absent data and damaged data are different things, and
treating the first as the second would quietly disable the findings that
matter most.
- It assigns no score, no rating, no red/green light, and gives no advice.
It states differences; you decide what they mean.
Why not just read the sync log?
Because the sync log tells you what the sync tried to do. This tells you what
is true right now on both sides, computed from the data itself.
Development notes
The comparison engine is deliberately free of WordPress dependencies so it can
be tested on the command line:
php # admin layer against function stubs, 23 checks
And inside a real install (from the WordPress root):
php
The real-WordPress suite covers plugin loading, the Tools menu (registered for an
administrator, absent for a subscriber), the capability gate, a valid nonce being
accepted and a forged one rejected, the snapshot option, revert detection across
runs, and a read-only proof that no posts, post meta or other options are
written. 26: 20/20.
The WooCommerce suite covers the catalogue path: it creates products, then audits
the catalogue against a CSV and checks that the matching product is not reported
as drift, that quantity drift is found, that a CSV-only SKU is reported as
missing, that variations are read, that a product with no SKU is never silently
matched, and that a catalogue containing untracked-stock or container rows still
reports the genuinely missing SKU. Run on
0: 24/24.
php uses stand-in WordPress functions; the real-WP
suites are the ones that prove behaviour inside WordPress itself.