Merchlint – Catalog Audit for WooCommerce

Nothing. All twenty-three checks are free, on every product, with no cap, no time limit and no account. Twelve more checks are being prepared as a paid add-on; the free plugin does not depend on it.

No. It reads your catalog (catalogue, in British spelling) and reports what it finds. Every change is made by you, in your own admin. This is enforced in the code, not just promised: an automated check refuses to build the plugin if it calls any function that would modify products, categories, media or orders.

The scan runs in the background, in short slices, on the admin side. On the storefront it only opens up to three of your product pages per scan, the way a visitor does. If the scan is interrupted—a server restart, a deployment—it picks up where it left off and gives the same result as an uninterrupted run.

Then hide them. Every rule's page explains when the finding is not a problem—seasonal goods, spare parts, products sold only by phone—and hiding takes two clicks, with an optional reason. The decision survives future scans, and the hidden items stay visible as a count and in a list you can restore them from, so nothing disappears silently.

Yes. Live Preview on this page opens a demo store in your browser with an audit already run: 24 products, orders from the last twelve months and the findings they produce. Nothing is installed on your site.

Yes. A scan of 50,000 products completes in about eight minutes and the results are paginated, so a rule with twelve thousand findings still opens instantly.

Yes. Translations of one product are counted as one product: their SKU is shared deliberately, and their stock is one physical stock, so we never report the same goods twice or double the amount at stake. Polylang is tested with the plugin itself; WPML is recognized through its translation table, which we test against the same data it produces.

Yes, with HPOS on and off. Both modes give identical results, amounts included.

Because a stalled queue fails quietly. WP-Cron and Action Scheduler are what WooCommerce and its extensions book later work on—the end of a scheduled sale, the cancelling of unpaid orders that hold stock, subscription renewals, follow-up emails—and neither your storefront nor your order list will tell you they stopped. The store keeps selling. It just stops doing everything that was meant to happen later. The two queues are reported as separate findings, because they stop for different reasons and are fixed in different places. What the rule measures is the age of the oldest overdue action, not how many are waiting: a store with no visitors always has a queue full of them and is perfectly healthy, because the first visitor clears it. Anything overdue by more than a day is not quiet, it is broken. A developer can change that threshold with the merchlint_scan_settings filter.

Yes. wp merchlint scan runs the audit, wp merchlint status --format=json gives the counts per check, wp merchlint findings and wp merchlint export the results. wp help merchlint describes the commands in English; their output is in Polish for now. With WP-CLI aliases, wp @all merchlint scan audits every store you manage in one go.

In the support forum. Every finding shows the field and value it rests on, so paste them with your question.

Only if you connect one yourself. On WordPress 6.9 or later Merchlint registers two read-only abilities through the WordPress Abilities API: the audit summary and the list of findings. An AI assistant you connect to your store, for example through an MCP plugin, can call them as a logged-in user with the manage_woocommerce permission, and gets the same results as the Store audit screen. Merchlint itself sends your data nowhere and changes nothing in your store.