Merchlint
Available now
Next, in this order
  • DeutschDE
  • EspañolES
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install

For agencies

The chapter your audit report does not have—what the catalog itself is costing the client. Free version, no account, and it never changes the store.

A WooCommerce audit you sell today is mostly infrastructure: speed, plugin conflicts, versions, checkout, payment gateways, security, error logs. Merchlint does almost none of that and is not trying to—of its twenty-three checks, about three would belong in that report at all.

It does the part those audits leave out: the catalog as the thing that sells. Which products sold last year and cannot be bought today. Which sale prices expired in March and are still running. Which SKUs are duplicated, so imports and feeds can mix up two different products. None of it shows up as an error, which is exactly why technical audits miss it.

So this is a chapter you can add to a report you already sell. On a store with 5,000 products, twenty-three checks take under a minute, and every finding comes with the field and value it was based on, so writing it up means filtering a list, not re-checking every product.

Everything here works in the free version

There is no agency tier to buy. The plugin is GPL, the twenty-three checks have no product cap, and nothing on this page needs a license key.

wp plugin install merchlint --activate
wp merchlint scan
wp merchlint export > audit-clientname-2026-09.csv

Nine commands are available — scan, status, cancel, findings, rule, export, hide, unhide, hidden. Everything you can do in the admin, you can also do without a browser, which is what makes this usable across twenty stores instead of one.

Over a set of sites you manage, that becomes a loop:

for site in client-a client-b client-c; do
  wp --path="/srv/$site" merchlint scan
  wp --path="/srv/$site" merchlint export > "reports/$site.csv"
done

Why this is safe to run on a client’s production store

It changes nothing in the store. No product, price, stock level, order, option or media file is modified. The only thing it writes is its own results table. That is enforced by an automated gate on every build, not by convention—the reasoning is on why there is no “Fix it” button.

It sends nothing anywhere. Nothing about your client’s catalog leaves their server. The only requests it makes go to the store itself: during an audit it opens up to three of the store’s own product pages, the way a visitor would. There is no account, no sign-up and no telemetry, which also means there is nothing to put in a data processing agreement.

It works in small batches and resumes if interrupted. Scanning runs in batches through Action Scheduler with a hard time limit per batch; a 50,000-product catalog completes in about eight minutes and survives the PHP process being killed halfway.

What you get that a checklist does not

Ranking by revenue. Findings are ordered by what each product actually earned over the past twelve months, read from the store’s own order data. On a client call, “these three products earned $12,400 last year and cannot be bought today” is a different conversation from “you have 247 issues”.

Deterministic results. Two scans of an unchanged store produce the same list, item for item. A separate screen shows what changed between scans and whether the difference came from the store or from a rule of ours getting smarter. You can show a client a clear before-and-after.

Evidence per finding, which is what survives a client saying “that is not true”.

What does not exist yet, stated plainly

  • No central panel. Each store is scanned on its own; the CSV export is how you aggregate today.
  • No white-label. Reports carry no branding at all, yours or ours, but there is nothing to rebrand either.
  • No scheduled scans or email alerts in the free version.

A central panel and white-labeling are on the agency roadmap, and we are deliberately not building them yet. The plugin has been public since September 1, 2026; building a multi-store panel before knowing whether agencies want one is how a solo project spends its entire budget on a guess.

Which is where you come in

If you manage WooCommerce stores, we want to hear how you audit them now, what you charge for it, and what would have to be true for a tool to be worth paying for. Not a sales call—there is nothing to sell yet, and that is exactly why the answers are useful.

contact@merchlint.com—replies usually within one business day, from the person who wrote it.