Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Merchlint – Catalog Audit for WooCommerce

开发者 baltano
更新时间 2026年10月21日 16:40
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

ean abilities-api catalogue audit duplicate gtin missing gtin

下载

0.2.1 0.2.0 0.3.1 0.3.0 0.3.2 0.3.3 0.3.4 0.3.5 0.3.7 0.3.6 0.3.8 0.3.9

详情介绍:

Merchlint reads your WooCommerce catalogue and tells you where it is losing you money. Every finding comes with the value it was based on, so you can check it yourself instead of taking our word for it. It changes nothing. No product, no price, no stock level, no order. The audit reads and reports; every fix is yours to make, in your own admin. https://www.youtube.com/watch?v=0JRXpF6y1U0 What it looks for Twenty checks, in six groups: What makes it different Every check has a page that explains it Twenty checks, twenty pages — linked from the audit screen, next to the rule they belong to. Each page says what the problem costs, which fields the rule reads and which thresholds it compares them against, how to fix it, and when the finding is not a problem in your store. That last part is why the pages exist. A rule you cannot argue with is a rule you end up ignoring wholesale, so every page names the cases where the right answer is "hide this and move on": seasonal goods, spare parts, products sold only by phone. Your data stays yours The free version works entirely on your server. No account, no sign-up, no phoning home: the plugin makes no outbound connections at all, and an automated check enforces that on every build. The links to merchlint.com are ordinary links. They open in your browser when you click them, and the plugin sends nothing along the way — not your store's address, not its version, not an identifier of any kind. The only thing in the address is the language your admin is set to, so that a Polish store gets the Polish page. Without a click, nothing leaves your store at all. An AI assistant can read the audit only if you connect one to your store yourself; see the FAQ. From the same author Merchgain is a free profit report for WooCommerce from the same author. This audit shows the revenue at stake; Merchgain shows how much of what you sell you actually keep: gross profit and margin per product, category and period, from the cost of goods field built into WooCommerce 10.3 and newer. Like Merchlint, it only reads. If Merchgain is not installed, a short note about it appears at the very bottom of the audit screen, below the results. "Don’t show again" hides it for good, and it never appears anywhere else in your admin.

安装:

  1. Install and activate the plugin. WooCommerce must be active first — WordPress enforces this for you.
  2. Open Store audit in the admin menu.
  3. Press Scan now. A store with 50 000 products takes about a minute and a half on the hardware we measure on; a slower host takes longer. You can stop the scan at any point.
The audit reads your catalogue and writes only to its own tables. Removing the plugin removes them. Short PHP time limit? Nothing to do — the audit reads your host's own limit and sizes each chunk to fit inside it, then books the next one itself. A shorter chunk means more of them, not less work: the audit still finishes, and it still resumes from where it stopped. If your host reports a limit it does not actually enforce, you can set the chunk yourself in wp-config.php: define( 'MERCHLINT_BUDGET_SECONDS', 8 );

屏幕截图:

  • The top of the audit screen: the revenue from products that can no longer be bought, the checks
  • Every check that found something has its own card on the audit screen: what to do about it,
  • Everything we checked: a bar for each area of the store, then every rule with its count, split
  • What changed since the previous audit — here, findings that disappeared because the store itself

升级注意事项:

0.3.9 A new check finds product photos smaller than 500 × 500 pixels, which Google Merchant Center stops showing on 31 January 2027. The identifier checks also say when numbers are left in the fields of a GTIN plugin that is no longer in the directory. 0.3.8 An AI assistant you connect to your store can read the audit (WordPress 6.9 or later), and Tools → Site Health shows what the last audit found. 0.3.7 A new check finds published products that WooCommerce keeps out of the shop because of their parent - since WooCommerce 11.1 also when the parent doesn't exist. Also brings back the evidence in a check's full list on phones. 0.3.6 Each check that found something gets a card with its first five items on the audit screen, and the evidence uses WooCommerce's own words. Hidden items get an optional reason and a list where you can restore them. Also fixes the way back after hiding an item in a shop installed in a folder. 0.3.5 A summary at the top of the audit screen, a new check for products marked sold out while their variations are in stock, and fewer false findings in several checks. Some counts change after updating because the checks changed, not your shop - the Changes screen says which. 0.3.4 Small fixes: the evidence gives its reason in your language, amounts in the Polish admin read "7 740,00", and the notes about identifiers kept in another plugin's field give advice that can be followed. Nothing in your shop changes.

常见问题:

Does it change anything in my store?

No. It reads your catalogue 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.

Will it slow my store down?

The scan runs in the background, in short slices, and it only touches the admin side. Your storefront is not involved. 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.

Can I audit a store with tens of thousands of products?

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

Why does it check WP-Cron and Action Scheduler?

Because a stalled queue fails quietly. WP-Cron and Action Scheduler are what WooCommerce and its extensions book later work on — order emails, the end of a scheduled sale, stock released from abandoned carts, subscription renewals — 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 — and that threshold is yours to move.

What does "store health" cover here?

Everything the twenty checks touch, not only product fields: the catalogue and its categories, the media library and the files behind it, the size of your autoloaded options, and the versions of PHP, WordPress and WooCommerce you are running. A store can have faultless product data and still be losing money to a stalled queue or to an unsupported PHP version, so the report covers both.

Does it work with multilingual stores?

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 recognised through its translation table, which we test against the same data it produces.

Does it work with HPOS (High-Performance Order Storage)?

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

Some of the findings do not apply to my store.

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.

Can an AI assistant read my audit?

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 nothing anywhere and changes nothing in your store.

更新日志:

0.3.9 0.3.8 0.3.7 0.3.6 0.3.5 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.2.1 0.2.0 0.1.1 0.1.0