Driftgauge Sync Auditor
by dirkdigger 1 (0 reviews)

Driftgauge Sync Auditor

Compare your WooCommerce inventory against any supplier feed, CSV import or marketplace export, and see every difference before you trust it.

Driftgauge Sync Auditor ranks #56,800 among WordPress.org plugins with 1+ active installations, is #7,179 of 13,811 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Oct 11, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v0.1.0 Current Version v0.1.0
Updated 1 week ago Last Update on 11 Oct, 2026
Refreshed 7 hours ago Last Refreshed on
#7,179 of 13,811 in E-commerce Downloads -69.1% this week Actively maintained
View on WordPress.org
Rank
#56,800
— No change
Active Installs
1+
-2%
KW Avg Position
N/A
— No change
Downloads
94
+2 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 10

Total Progress 30%
0+ 10+
43,863
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 7 more installs to reach 10+

Rank Changes

51,424 56,146 60,868 65,589 70,311 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026
51,184 56,425 61,666 66,906 72,147 09-10-2026 10-10-2026 11-10-2026 12-10-2026 13-10-2026 14-10-2026 15-10-2026 16-10-2026 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026
Current #56,800
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026
0 10 20 30 40 09-10-2026 10-10-2026 11-10-2026 12-10-2026 13-10-2026 14-10-2026 15-10-2026 16-10-2026 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Driftgauge Sync Auditor

Run the audit with the file you imported (or a fresh export from the other side) as one side, and your catalogue as the other. Every SKU that disagrees on quantity or price, every row present on only one side, and every value that reverted since the previous run is listed explicitly. Running it changes nothing.
Yes. Run the same comparison on a schedule and keep the reports: each run is compared against the previous one, so a value that silently moved back is called out as a reversion instead of looking like a fresh difference.
No. It reads, compares and reports. There is no write path to products, orders or any other store data. The only thing it saves is its own small snapshot option, which is what lets it tell you that a value reverted.
Common headers are recognised automatically in English and Chinese — for example SKU, Item Code, Variant SKU, 货号, Qty, On Hand, 库存, Price, Regular price, 单价. For anything else the audit stops rather than guessing, and the failure message names the field it could not find.
Yes. Shopify's variant export and WooCommerce's own product export are recognised as formats, including the parent/variation rows those exports write without a SKU — those are structure, not errors. Any other CSV is read by its headings.
If one side failed to load some rows, a row that appears only on the other side
difference.
The comparison is linear. A 20,000-row pair is processed in well under a second on a normal machine; the practical limit is your upload and memory limits.
They are read and matched by SKU, but their quantity is unknown — there is no number to compare — so the row is not compared on quantity and the count of such rows is listed under Notes. It is deliberately not treated as zero: that would invent a quantity and then report a confident, false "quantity disagrees" against every matching row in the other file. It is also not treated as damaged data, because that would make the whole side untrustworthy and suppress the "missing on the other side" findings — the most useful thing this tool reports.

Sign In / Register

You need to sign in or register to use this feature.