Scan now<\/strong>. A store with 50 000 products takes about a minute and a half on the hardware\nwe measure on; a slower host takes longer. You can stop the scan at any point.<\/li>\n<\/ol>\n\nThe 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\nIf your host reports a limit it does not actually enforce, you can set the chunk yourself in\n wp-config.php:<\/p>\n\n
define( 'MERCHLINT_BUDGET_SECONDS', 8 );\n<\/code><\/pre>\n\n\n\nDoes it change anything in my store?<\/h3><\/dt>\nNo. 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
Will it slow my store down?<\/h3><\/dt>\nThe 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
Can I audit a store with tens of thousands of products?<\/h3><\/dt>\nYes. 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
Why does it check WP-Cron and Action Scheduler?<\/h3><\/dt>\nBecause 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
What does \"store health\" cover here?<\/h3><\/dt>\nEverything 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
Does it work with multilingual stores?<\/h3><\/dt>\nYes. 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
Does it work with HPOS (High-Performance Order Storage)?<\/h3><\/dt>\nYes, with HPOS on and off. Both modes give identical results, amounts included.<\/p><\/dd>\n
Some of the findings do not apply to my store.<\/h3><\/dt>\nThen 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
0.3.2<\/h4>\n\n\nOn 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>\nThe 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>\nThe 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>\nA 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\n0.3.1<\/h4>\n\n\n- Both duplicate checks now see codes stored on variations, not only on products.<\/strong> Until now the\ncomparison ran over products alone, so a code repeated between one product and another product's\nvariation was invisible \u2014 even though an export file treats every variation as a separate item.\nOn a store with variable products the numbers can go up after this update.<\/li>\n
- The identifier check also reports a product that shares its number with its own variation. The\nSKU check does not<\/strong> \u2014 and that difference is deliberate. WooCommerce shows the parent's SKU on a\nvariation that has none, so for SKU that pair is how the platform behaves, not a fault. For the\nidentifier there is no such inheritance: WooCommerce requires it to be unique across products and\nvariations, yet never notices when an import writes the pair straight to the database, so this is\nthe only place it surfaces. It matters when an export file carries the parent alongside its\nvariations \u2014 then two items go out with one number.<\/li>\n
- One pair is still left out and the knowledge pages now say so: two variations of one product\nsharing a code while the product itself carries none. A finding belongs to a product, and there\nis nothing to attach it to there.<\/li>\n
- The three checks whose behaviour changed carry a new version number, and that is deliberate.<\/strong>\nThe \"Changes since the previous audit\" screen reads those numbers to tell you when a movement\ncomes from us rather than from your store, and anything you hid under the old version is marked\nfor a second look \u2014 your decision was an answer to a question that is now worded differently.\nNothing is un-hidden behind your back; it is only flagged.<\/li>\n
- Variations sitting in the trash no longer count \u2014 anywhere.<\/strong> A variable product whose living\nvariations all carried an identifier could still be reported as missing one, because a trashed\nvariation had none; the same ghost could make a code look duplicated. Nothing in the shop shows\nthose variations, and WooCommerce's own uniqueness check ignores the trash as well \u2014 now so do we.\nThis one was in the previous release too, not only in the change above.<\/li>\n
- Two additions to the identifier check's knowledge page.<\/strong> What to do when the check is clean\nand the export file still shows no identifier \u2014 an export plugin may read the field through a\ncached list of fields, which a product save does not refresh. And why a number copied onto\nvariations while a file is being built hides the gap rather than closing it: a shopping service\nexpects each variation to carry its own, and this check reports what WooCommerce holds.<\/li>\n<\/ul>\n\n
0.3.0<\/h4>\n\n\n- Two new checks, both free and with no product cap: a product with no GTIN, UPC, EAN or ISBN,\nand two products sharing the same one.<\/strong> Shopping services use that identifier to match your\noffer to the same product sold elsewhere, so an empty or duplicated one is the usual reason an\nitem quietly drops out of a feed. WooCommerce has had the field since 9.2, on the Inventory tab,\nand nothing in the admin ever points at it. The check reads WooCommerce's own field; identifiers\nkept in a plugin's field or in a product attribute are not read.<\/li>\n
- The missing-identifier check stays quiet in shops that do not use identifiers at all.<\/strong> If not\none product has the field filled, you get a single sentence saying so instead of a list of your\nentire catalogue \u2014 handmade goods, services and your own production carry no manufacturer's\nbarcode and need none.<\/li>\n
- On a variable product the identifier belongs on each variation, so such a product gives one<\/strong>\nfinding with the evidence \"6 variations without a GTIN\" \u2014 not six separate rows.<\/li>\n
- Translations of one product are not reported as a duplicate, exactly as with SKU.<\/li>\n
- After an update, \"Changes since the previous audit\" now names the checks that are new.<\/strong>\nTwo checks arriving at once means findings arriving at once, and the screen showed the\nmovement without saying where it came from \u2014 so it read as if something had broken in your\nstore overnight. A check that is new and found nothing stays out of the way.<\/li>\n
- A check that could not run no longer reads as a clean one \u2014 on every screen, not just some.<\/strong>\nThe audit screen has always had a section saying what could not be checked and why. Two places\ndid not: the dashboard tile counted such a check among the rules it had gone through, and\n\"Changes since the previous audit\" showed its findings dropping to zero exactly as it shows a\nreal fix. On a store that keeps no product identifiers at all, that meant being congratulated\nfor something nobody had measured. The tile now says how many checks could not run, and the\ncomparison says plainly that a drop there is not a fix.<\/li>\n
- An empty catalogue is no longer reported as a clean one.<\/strong> A store with no products got a row\nof zeros and a tile saying nothing needed fixing \u2014 which is what a fresh WooCommerce install\nlooks like before the first product is added. The audit now says plainly that there was nothing\nto check.<\/li>\n
- Ready since 0.2.2 and shipping here: the audit engine no longer assumes every store can answer\nevery question.<\/strong> A rule now says what it needs, and a store that cannot provide it gets a plain\nnote saying the rule was not applicable \u2014 instead of a silent zero that reads like a clean\nresult. On WooCommerce every rule still applies, so every check you already had gives exactly\nthe same result as it did under 0.2.1.<\/li>\n
- The list of rules moved into the audit engine itself.<\/li>\n<\/ul>\n\n
0.2.1<\/h4>\n\n\n- New display name: Merchlint \u2013 Store Audit for WooCommerce.<\/strong> Same plugin, same address, same\nsettings \u2014 the name now says what it does, for people who find plugins by searching for the job\nrather than for a brand.<\/li>\n
- Every rule now links to its own page<\/strong>, which explains what the finding costs, exactly how the\nrule decides, how to fix it, and when it is not a problem worth fixing. The link opens in your\nbrowser and carries nothing but the language of your admin; the plugin itself still makes no\noutbound connections at all.<\/li>\n
- The plugin's name on your plugins list is now a link to its home page. Until now it led nowhere.<\/li>\n
- No change to what the audit checks or reports. A scan of an unchanged store gives exactly the\nsame result as it did under 0.2.0.<\/li>\n<\/ul>\n\n
0.2.0<\/h4>\n\n\n- First public release.<\/strong> Versions 0.1.0 and 0.1.1 below were pre-release: they were reviewed but\nnever published, so this is the first version you can install from the directory. Everything the\naudit does is listed under 0.1.0.<\/li>\n
- Two extension points so add-ons can build on the audit: an action when a scan finishes and\na filter over the scan settings, plus the scan history behind both.<\/li>\n
- Rules the current scan did not run are now marked \"not in this audit\" instead of \"clean\".<\/li>\n
- A scan now keeps its settings even if an add-on hands it a value that cannot be stored \u2014 before,\none such value silently dropped every threshold the scan was running with, and the second half of\nthe scan used the defaults.<\/li>\n
- Comparing two audits no longer writes a PHP notice to the log when a setting holds a list rather\nthan a number.<\/li>\n
- No change to what the audit checks on its own.<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- Translations now come from translate.wordpress.org instead of files bundled in the plugin.<\/li>\n
- No change to what the audit checks or reports.<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- First release. Fifteen checks, resumable scanning, CSV export, per-rule knowledge pages,\npermanent \"hide\", English and Polish.<\/li>\n<\/ul>","raw_excerpt":"Read-only WooCommerce product audit: goods that sold but are out of stock, duplicate SKUs, missing prices \u2014 each with the money at stake.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/360163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=360163"}],"author":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/baltano"}],"wp:attachment":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=360163"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=360163"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=360163"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=360163"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=360163"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=360163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}