On a site without WooCommerce the plugin now stays quiet instead of showing an empty screen. The\ndisplay name changed to "Merchlint - Catalog Audit for WooCommerce"; the plugin, its settings and\nits saved audits did not.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3676536,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3676536,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3676536,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3676536,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3676536,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.2.0","0.2.1","0.3.0","0.3.1","0.3.2","0.3.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3705632,"resolution":"1","location":"assets","locale":"","width":1280,"height":440},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3705632,"resolution":"2","location":"assets","locale":"","width":1280,"height":713},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3705632,"resolution":"3","location":"assets","locale":"","width":1280,"height":997},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3705632,"resolution":"4","location":"assets","locale":"","width":1280,"height":1737},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3705632,"resolution":"5","location":"assets","locale":"","width":1280,"height":466}},"screenshots":{"1":"The result of the last audit on the first screen you see after logging in: the revenue sitting\nin products that can no longer be bought, and how many findings are waiting behind it.","2":"Where to start: the three products with the largest amount at stake, one row per product with\neverything that is wrong with it, before the full list.","3":"One rule up close: what it checks, what to do about it, and every item with the evidence behind\nit \u2014 the fields read, the values found, and the money at stake.","4":"Every rule with its count, split into what came from your own data and what came from your theme\nor plugins \u2014 including the rules that found nothing, which say \"clean\" rather than staying silent.","5":"What changed since the previous audit \u2014 here, findings that disappeared because the store itself\nwas fixed. When a number moves because a rule of ours got smarter, the screen says so separately."}},"plugin_section":[262246],"plugin_tags":[279555,282711,282712,282713,282714],"plugin_category":[45,55],"plugin_contributors":[278694],"plugin_business_model":[],"class_list":["post-360163","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-autoloaded-options","plugin_tags-catalogue-audit","plugin_tags-duplicate-gtin","plugin_tags-missing-gtin","plugin_tags-sku-audit","plugin_category-ecommerce","plugin_category-seo-and-marketing","plugin_contributors-baltano","plugin_committers-baltano"],"banners":{"banner":"https:\/\/ps.w.org\/merchlint\/assets\/banner-772x250.png?rev=3676536","banner_2x":"https:\/\/ps.w.org\/merchlint\/assets\/banner-1544x500.png?rev=3676536","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/merchlint\/assets\/icon.svg?rev=3676536","icon":"https:\/\/ps.w.org\/merchlint\/assets\/icon.svg?rev=3676536","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/merchlint\/assets\/screenshot-1.png?rev=3705632","caption":"The result of the last audit on the first screen you see after logging in: the revenue sitting\nin products that can no longer be bought, and how many findings are waiting behind it."},{"src":"https:\/\/ps.w.org\/merchlint\/assets\/screenshot-2.png?rev=3705632","caption":"Where to start: the three products with the largest amount at stake, one row per product with\neverything that is wrong with it, before the full list."},{"src":"https:\/\/ps.w.org\/merchlint\/assets\/screenshot-3.png?rev=3705632","caption":"One rule up close: what it checks, what to do about it, and every item with the evidence behind\nit \u2014 the fields read, the values found, and the money at stake."},{"src":"https:\/\/ps.w.org\/merchlint\/assets\/screenshot-4.png?rev=3705632","caption":"Every rule with its count, split into what came from your own data and what came from your theme\nor plugins \u2014 including the rules that found nothing, which say \"clean\" rather than staying silent."},{"src":"https:\/\/ps.w.org\/merchlint\/assets\/screenshot-5.png?rev=3705632","caption":"What changed since the previous audit \u2014 here, findings that disappeared because the store itself\nwas fixed. When a number moves because a rule of ours got smarter, the screen says so separately."}],"raw_content":"\n
Merchlint reads your WooCommerce catalogue and tells you where it is losing you money. Every\nfinding comes with the value it was based on, so you can check it yourself instead of taking our\nword for it.<\/p>\n\n
It changes nothing. No product, no price, no stock level, no order. The audit reads and reports;\nevery fix is yours to make, in your own admin.<\/p>\n\n
Seventeen checks, in six groups:<\/p>\n\n
Seventeen checks, seventeen pages \u2014 linked from the audit screen, next to the rule they belong to.\nEach page says what the problem costs, which fields the rule reads and which thresholds it\ncompares them against, how to fix it, and when the finding is not<\/strong> a problem in your store.<\/p>\n\n That last part is why the pages exist. A rule you cannot argue with is a rule you end up ignoring\nwholesale, so every page names the cases where the right answer is \"hide this and move on\":\nseasonal goods, spare parts, products sold only by phone.<\/p>\n\n The free version works entirely on your server. No account, no sign-up, no phoning home: the\nplugin makes no outbound connections at all, and an automated check enforces that on every build.<\/p>\n\n The links to merchlint.com are ordinary links. They open in your browser when you click them, and\nthe plugin sends nothing along the way \u2014 not your store's address, not its version, not an\nidentifier of any kind. The only thing in the address is the language your admin is set to, so\nthat a Polish store gets the Polish page. Without a click, nothing leaves your store at all.<\/p>\n\n\n The audit reads your catalogue and writes only to its own tables. Removing the plugin removes them.<\/p>\n\n Short PHP time limit?<\/strong> Nothing to do \u2014 the audit reads your host's own limit and sizes each chunk\nto fit inside it, then books the next one itself. A shorter chunk means more of them, not less work:\nthe audit still finishes, and it still resumes from where it stopped.<\/p>\n\n If your host reports a limit it does not actually enforce, you can set the chunk yourself in\n wp-config.php:<\/p>\n\n No. It reads your catalogue and reports what it finds. Every change is made by you, in your own\nadmin. This is enforced in the code, not just promised: an automated check refuses to build the\nplugin if it calls any function that would modify products, categories, media or orders.<\/p><\/dd>\n The scan runs in the background, in short slices, and it only touches the admin side. Your\nstorefront is not involved. If the scan is interrupted \u2014 a server restart, a deployment \u2014 it picks\nup where it left off and gives the same result as an uninterrupted run.<\/p><\/dd>\n Yes. A scan of 50 000 products completes in about 90 seconds and the results are paginated, so\na rule with twelve thousand findings still opens instantly.<\/p><\/dd>\n Because a stalled queue fails quietly. WP-Cron and Action Scheduler are what WooCommerce and its\nextensions book later work on \u2014 order emails, the end of a scheduled sale, stock released from\nabandoned carts, subscription renewals \u2014 and neither your storefront nor your order list will tell\nyou they stopped. The store keeps selling. It just stops doing everything that was meant to happen\nlater.<\/p>\n\n The two queues are reported as separate findings, because they stop for different reasons and are\nfixed in different places. What the rule measures is the age of the oldest overdue action, not how\nmany are waiting: a store with no visitors always has a queue full of them and is perfectly\nhealthy, because the first visitor clears it. Anything overdue by more than a day is not quiet, it\nis broken \u2014 and that threshold is yours to move.<\/p><\/dd>\n Everything the seventeen checks touch, not only product fields: the catalogue and its categories, the\nmedia library and the files behind it, the size of your autoloaded options, and the versions of PHP,\nWordPress and WooCommerce you are running. A store can have faultless product data and still be\nlosing money to a stalled queue or to an unsupported PHP version, so the report covers both.<\/p><\/dd>\n Yes. Translations of one product are counted as one product: their SKU is shared deliberately, and\ntheir stock is one physical stock, so we never report the same goods twice or double the amount at\nstake. Polylang is tested with the plugin itself; WPML is recognised through its translation table,\nwhich we test against the same data it produces.<\/p><\/dd>\n Yes, with HPOS on and off. Both modes give identical results, amounts included.<\/p><\/dd>\n Then hide them. Every rule's page explains when the finding is NOT a problem \u2014 seasonal goods,\nspare parts, products sold only by phone \u2014 and hiding is one click. The decision survives future\nscans, and the hidden items stay visible as a count, so nothing disappears silently.<\/p><\/dd>\n\n<\/dl>\n\n\n The plugin no longer does anything at all when WooCommerce is not active.<\/strong> Until now it\ncreated its own tables on every page load, registered the audit screen and added its WP-CLI\ncommand even on a site with no WooCommerce - and then showed an empty screen without a word\nof explanation. It now checks first, says so in one sentence on the dashboard, and touches\nnothing. Saved results are left exactly as they were: activate WooCommerce and everything\ncomes back.<\/p><\/li>\n New display name: Merchlint - Catalog Audit for WooCommerce.<\/strong> Only the displayed name\nchanged: same plugin, same directory address, same settings, same saved audits. Nothing in\nyour shop needs doing, and the screen in your admin menu is where it was.<\/p><\/li>\n The identifier checks now say when your numbers are kept in another plugin's field.<\/strong> Both\nchecks read WooCommerce's own GTIN, UPC, EAN or ISBN field. When products hold their number only\nin a field of EAN for WooCommerce, Germanized for WooCommerce, Trusted Shops Easy Integration,\nGoogle for WooCommerce, Customer Reviews for WooCommerce or Product Feed Manager for WooCommerce,\nthe audit now says how many, names the field and\nsays plainly which check cannot see those numbers \u2014 on the results screen, on the check's own\npage, in WP-CLI and in the CSV export. Germanized passes its numbers through WooCommerce's own\nfield when that field is empty, so with Germanized active only the duplicate check is affected.\nNothing is counted differently: no finding appears or disappears, and earlier scans stay\ncomparable.<\/p><\/li>\n A check's own page now shows what that check could not see.<\/strong> Notes about gaps were only on\nthe main results screen, above the list of checks \u2014 not next to the findings they explain.<\/p><\/li>\n \"What this audit could NOT check\" no longer says \"these rules found nothing\" about rules that\nran.<\/strong> A rule that missed only part of what it looks at is now listed separately, with a sentence\nof its own.<\/p><\/li>\n Invisible characters in product codes now show in the evidence.<\/strong> Two codes that differ only\nby a non-breaking space or a zero-width character look the same on screen, so a pair of\nduplicates could show one value twice, with no way to tell which product carries the extra\ncharacter. The evidence now writes each such character as \u27e8U+00A0\u27e9 and similar, on the screen and\nin the CSV export. Clean codes look exactly as before.<\/p><\/li>\n Three WP-CLI commands now stop on bad input instead of guessing.<\/strong> With a mistyped check code,\n\"findings\" listed and \"export\" exported every finding instead of none; an invalid separator in\n\"export\" ended in a critical error; \"cancel\" reported success for a scan that does not exist.\nEach of them now says what was wrong.<\/p><\/li>\n Two WP-CLI outputs now keep gaps apart from findings.<\/strong> The message after \"export\" counted the\nrows about gaps \u2014 what the audit could not check \u2014 as findings, so a check that never ran was\nreported as one saved finding. It now counts findings only and names the gap rows separately.\n\"status --format=json\" now lists the gaps the same way \"rule --format=json\" does; until now a\ncheck that did not run simply disappeared from its counts.<\/p><\/li>\n The advice for missing sales data now points to a button that exists.<\/strong> When WooCommerce's\norder summary table was empty, the audit told you to run \"Regenerate the order lookup tables\" in\nStatus \u2192 Tools, and WooCommerce has no such tool. It now sends you to Analytics \u2192 Settings \u2192\n\"Import historical data\", and the WP-CLI warning gives the same advice instead of naming a script\nthat is not part of the plugin.<\/p><\/li>\n One request for a review, under the results.<\/strong> It appears once per user after a finished\naudit and goes away for good when you open it or choose \"Don't ask again\". No reward is offered\nand no rating is suggested.<\/p><\/li>\n<\/ul>\n\n On WooCommerce older than 9.2 the two identifier checks now say they did not run, instead of\nreporting numbers.<\/strong> That WooCommerce has no field for a product identifier at all. If the\nfield had been written straight into the database - after moving back from a newer version, or\nby an import - the plugin used to treat the store as one that keeps identifiers while reading\nevery one of them as empty: the duplicate check then reported nothing even when duplicates\nwere there. Both checks now stay quiet and say why, naming the WooCommerce version that first had the field.<\/p><\/li>\n The evidence column no longer shows a Polish word on an English screen.<\/strong> Where a check reads\na field and finds it empty, the value now reads \"(empty)\". It had been coming straight from the audit\nengine, which has no access to translations, so the Polish \"(puste)\" appeared for anyone reading the\nscreen in English - in the one column whose whole job is to let you verify us.<\/p><\/li>\n The duplicate-identifier check now says when it had nothing to compare.<\/strong> On a catalogue where\nnot one product carries an identifier, it used to report \"nothing found - this check is clean\" - a clean\nbill of health for a field nobody fills, and two different sentences about the same field one under the\nother, because the missing-identifier check said so correctly. Both checks now give the same answer,\nwith the same reason.<\/p><\/li>\n A finding on a variation now links straight to the tab where you fix it.<\/strong> The link in\nthe list opened the parent product at the top of the page; on a product with twenty\nvariations that is a long way from the one you were sent to. The export file had carried\nthe right link all along - only the screen did not.<\/p><\/li>\n<\/ul>\n\n\n
Your data stays yours<\/h4>\n\n
\n
define( 'MERCHLINT_BUDGET_SECONDS', 8 );\n<\/code><\/pre>\n\n\n\n
Does it change anything in my store?<\/h3><\/dt>\n
Will it slow my store down?<\/h3><\/dt>\n
Can I audit a store with tens of thousands of products?<\/h3><\/dt>\n
Why does it check WP-Cron and Action Scheduler?<\/h3><\/dt>\n
What does \"store health\" cover here?<\/h3><\/dt>\n
Does it work with multilingual stores?<\/h3><\/dt>\n
Does it work with HPOS (High-Performance Order Storage)?<\/h3><\/dt>\n
Some of the findings do not apply to my store.<\/h3><\/dt>\n
0.3.3<\/h4>\n\n
\n
0.3.2<\/h4>\n\n
\n
0.3.1<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
0.2.1<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n