Changelog
Every release, what changed in it, and what is next. The most reasonable worry about a new plugin is that it quietly dies, so here is the evidence either way.
Add-on for Google Sheets 1.1 in the Marketplace — November 20, 2026
- Google approved version 1.1 of GTIN & EAN Check, and the Marketplace now installs it. Besides codes, it checks a whole product export for the data Google Shopping disapproves, and it speaks German and Spanish.
- The add-on’s page describes Check product data: what it finds, how it reads variations and which exports it recognizes.
Add-on for Google Sheets: privacy policy and terms for version 1.1 — November 12, 2026
- Privacy policy and section 14 of the terms describe version 1.1 of GTIN & EAN Check: Check product data reads the whole sheet you check and reports prices of 0, missing names, descriptions, images and brands, and repeated SKUs. It still sends nothing anywhere and needs no new permission.
- Version 1.1 is waiting for Google’s review; until then the Marketplace installs version 1.
0.3.11 — November 4, 2026
- Disabled variations are judged the way your shop treats them. A variation with Enabled cleared cannot be bought or picked, so Variation the customer can never pick, Variations with no price or code and No GTIN, UPC, EAN or ISBN no longer report it. Every variation sold out now reports a product whose only variations in stock are disabled.
- Product with no category recognizes the default category on every store. Where WooCommerce saved the default category under a different ID than the category itself, which can happen after a migration, products that sat only in that category were not reported.
- Clearer wording on the audit screen and the check pages, and
wp help merchlintis in English.
0.3.10 — October 31, 2026
- New check: Product pages send Google no product data. The
audit opens up to three of your product pages, the way a visitor does, and reads the structured data
Google uses to show a product with its price. A template that skips WooCommerce’s product summary still
shows the page, but sends Google nothing. Requests go only to your own store; when a page cannot be
opened, the check says why. The
merchlint_open_product_pagesfilter turns them off. - New check: Your store asks Google not to show it. The WordPress setting “Discourage search engines from indexing this site”, or Yoast SEO or Rank Math hiding every product from search.
- New check: No public refund and returns policy page. From WooCommerce 11.3 the selected returns policy page tells search engines where to find it, but only once it is published, and WooCommerce creates it as a draft. The three new checks are free, which makes twenty-three checks in the free version.
- A check your WooCommerce does not support yet is a note, not a gap. Below WooCommerce 11.3 (returns page) or 9.2 (product identifiers) the audit names the version the check needs instead of calling it not checked.
- A sale that will not stop no longer reports sales that ended on schedule, and Unsupported PHP, WordPress or WooCommerce follows WooCommerce’s security policy, with a PHP warning 60 days before its security fixes end.
- Privacy policy updated on November 1, 2026: the requests the audit makes to your own product pages, and the filter that turns them off.
0.3.9 — October 21, 2026
- New check: Photo too small for Google. From January 31, 2027 Google Merchant Center requires product images of at least 500 × 500 pixels, and a product whose photo is smaller will not appear on Google. The check reports the main photo of every published product, and the photo of each variation that has its own, when its width or height is below 500 pixels; the evidence gives the size it found. A photo used by many products is one finding, because replacing the file fixes all of them. Gallery photos are not checked. The check is free, which makes twenty checks in the free version.
- The identifier checks also say when numbers are kept in
hwp_product_gtinorhwp_var_gtin. A GTIN plugin that is no longer in the WordPress.org directory stored numbers in these two fields, and a store that used it keeps them there after removing it. When products hold their number only in one of those fields, the audit says how many and names the field, as it already does for other plugins’ fields. Nothing is counted differently. How to move those numbers into WooCommerce. - Under the audit results, a short note about Merchgain, a free profit report from the same author. It appears only on the audit screen, only if Merchgain is not installed, and “Don’t show again” hides it for good.
GTIN & EAN Check in the Google Workspace Marketplace — October 16, 2026
- The add-on for Google Sheets is published. Google approved it on October 16, and its page now links to the Marketplace listing. Free, no account with us.
- The check digit formula and the GTIN validator now point to the add-on for codes kept in Google Sheets.
Add-on for Google Sheets: privacy policy and terms — October 15, 2026
- New section in the privacy policy: the add-on for Google Sheets. What GTIN & EAN Check reads and writes in your spreadsheet—only the cells you select, and a report in a new sheet—and that it sends nothing anywhere.
- Terms: new section 14 for the add-on: free, no account with us, provided as it is.
- The add-on is in Google’s review; its page will get the install link.
Terms and privacy policy: what the scanner reads beyond the API — October 15, 2026
- The description of what is read now matches what the scanner has done since October. Since October 5 the check—free and full—fetches the full page of at most two products when the API has an image with no alternative text, to see what the store shows in its place. Since October 9, when a store has no public API, it asks for the headers of the home page to tell which platform it runs on. Until now the terms mentioned only the headers of three product pages. Terms, section 2, privacy policy.
- Full scan: image-weight requests now described in the terms too. The full scan has asked for the headers of the main image files of 40 products from the start; the privacy policy said so, and now section 13 of the terms does as well.
0.3.8 — October 14, 2026
- An AI assistant can read the audit. 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, most expensive first. An assistant you connect to your store yourself, for example through an MCP plugin, calls them with the same permission as the Store audit screen and gets the same numbers. They read the last finished audit and never start a new one; Merchlint sends nothing anywhere.
- Site Health shows what the last audit found. Tools → Site Health gets a Merchlint item. When the last audit found products that were selling and can no longer be bought, the item is a recommended improvement that says how many there are and how much they brought in; other “Important” findings make it one too. An audit older than 30 days gets a warning, because the store may have changed since. The item only reads the saved audit and never starts a new one.
- Works on SQLite. Two queries used MySQL syntax that SQLite-based WordPress—WordPress Playground, for example—rejects, so there the “Where to start” list stayed empty and SKUs and GTINs with a stray space at the start or end were not compared as equal. Both queries now run on SQLite too; on MySQL and MariaDB the results are exactly as before.
0.3.7 — October 12, 2026
- New check: Published, but the store doesn’t show it. Since WooCommerce 11.1, a product whose parent points to an entry that doesn’t exist or isn’t published disappears from the shop page, categories and search, and a simple product can’t be added to the cart—while the admin shows it as published and visible. CSV imports and tools that create products through the REST API sometimes write such a parent. WooCommerce itself decides, in the version you run, and the check follows it: from 11.3 a parent that isn’t a product no longer hides anything. Free, like the check before it.
- On a phone, the full list of a check shows the evidence again. Since 0.3.6 the “What we read” column was hidden on narrow screens with no way to open it; each row now has the button that shows it.
0.3.6 — October 11, 2026
- Every check that found something has its own card on the audit screen, under “What we found, check by check”: the first five items with a thumbnail, the evidence and the amount, and what to do about them. “Show all” opens the full list, and the check names in “Where to start” and in the list of checks lead to their cards.
- The evidence reads as “field: value”, in the words WooCommerce uses—“Out of stock” rather than “outofstock”, “Uncategorized (#15)” rather than “15”—on the screen and in the CSV export. Amounts follow the number format of the admin language. WP-CLI output has not changed.
- “Hide from report” takes an optional reason, and everything hidden has its own list. The “Hidden items” button shows each item with the date and the reason, and restores any of them—also items the latest audit no longer finds.
- The summary gives the size of the catalog: “Products in the catalog”, counted when the audit ran.
- On the “Why did this change?” screen each example links to its item, the checks stand in code order, and the screen says how many items were hidden since the earlier audit.
- Fixed the way back after hiding or restoring an item in a store installed in a folder, with an address such as example.com/shop.
- “When this is NOT a problem” no longer suggests hiding where hiding is the wrong answer—under Two products share the same SKU, Variation the customer cannot select and Sold out, but its variations are in stock. These checks have practically no exceptions; the answer is to fix the product.
0.3.5 — October 7, 2026
- The audit screen starts with a summary. Above the full list: the revenue sitting in products that sold but can no longer be bought, and four tiles—Important, Worth fixing, Clean, Not checked—each with the number of checks in it. “Everything we checked” opens with a bar per area of the catalog, “Where to start” shows each product’s photo and a bar for its amount, and the dashboard widget shows the same four counts.
- New check: a product marked sold out while its variations are in stock. The store and search results say out of stock while the product page still sells a variation—one of the two is wrong, and the advice starts with finding out which. Sold out, but its variations are in stock. The check for products that sold and can no longer be bought no longer lists them, because they can be bought.
- Fewer false findings. Checks based on sales skip products that earned nothing in the period—sold only at a price of 0, or every sale refunded. Product with no price no longer lists products that are out of stock or gift cards, and the GTIN check skips gift cards.
- SKUs and GTINs are compared the same way on every database. An invisible character or a non-breaking space no longer makes a different code; until now, on MySQL 8, such a duplicate was missed or only one product of the pair was listed.
- Image with no alt text also counts a file name, a random code or digits only, and the advice says what WooCommerce 9.5 and later show in place of an empty field.
- “Where to start” counts each product’s amount once, and evidence on an English screen is in English.
After updating, some counts change because the checks changed, not your store—the Changes screen says which.
0.3.4 — October 2, 2026
- The evidence gives its reason in words, in the language of your admin—“excluded from the catalog” instead of an internal code in Polish. WP-CLI keeps the code, because scripts read it.
- Amounts and counts in the Polish admin read “7 740,00”, not “7,740,00”.
- The notes about identifiers kept in another plugin’s field give advice that can be followed: for EAN for WooCommerce they name that plugin’s own copy tool, and on WooCommerce 9.0 and 9.1 they no longer send you to a field that is not there.
wp merchlint status --format=jsonalso gives the counts the table shows —visible_countsandhidden_countsnext tocounts.
Storefront Scan: product pages that do not open, and editing in the admin — September 30, 2026
- A warning when product pages do not open. The check—free and full—asks for the headers of three product pages from different parts of the catalog. When each one redirects to the same address—for example to the home page, because the store shows products only in a menu—the result says so above the lists, instead of leaving links that silently lead to the home page. Terms, section 2.
- “Edit in admin” next to every item of the full scan. Each product or category name has a link to edit it in the store admin, also in the CSV file (a new, last column). It works once you are logged in, and also when the product page is switched off. Terms, section 13, Privacy.
Terms: longer access with offer codes — September 30, 2026
- A group or partner code may give longer access than 30 days if its offer says so; a purchased code still gives 30 days. The end date of access is shown on the full-scan result page. Terms, section 13. The privacy policy says the same about how long a full-scan result lives. Privacy.
Storefront Scan: the full scan with a code — September 30, 2026
- A full scan with a code. A code opens a check of up to 2,000 products, complete lists instead of five examples, image weights, a CSV export and a result kept for 30 days, compared with the previous full scan. You activate the code on a separate page; it is tied to the store only at the first successful scan. The free check works as before.
- Terms: new section 13—kinds of code, validity, activation, offers with a group code (places go by order of activation, not by chance), withdrawal and refunds. The “one check of a store per day” limit now counts separately for the free and the full check.
- Privacy policy: what we record when a code is activated or sold (a transaction number—no buyer data), how
long a full-scan result lives, a counter of visits through short addresses
merchlint.com/o/…(no IP address) and failed checks in the journal. Privacy.
Privacy policy — September 29, 2026
- New section: free catalog audit. What happens to a plugin export if you send it to us for the free audit (offered on the Polish side of the site): who reads it, how long we keep it and what we don’t do with it. The plugin still makes no connections. Privacy.
0.3.3 — September 25, 2026
- New display name: Merchlint – Catalog Audit for WooCommerce. Only the displayed name changed: same plugin, same directory address, same settings, same saved audits.
- The identifier checks now say when your numbers are kept in another plugin’s field—EAN for WooCommerce, Germanized for WooCommerce, Trusted Shops Easy Integration, Google for WooCommerce, Customer Reviews for WooCommerce or Product Feed Manager for WooCommerce. The audit says how many products, names the field and says which check cannot see those numbers. Nothing is counted differently: no finding appears or disappears. How to move the numbers across.
- The plugin no longer does anything at all when WooCommerce is not active. It says so in one sentence on the dashboard and touches nothing; activate WooCommerce and everything comes back.
- Invisible characters in product codes now show in the evidence, as ⟨U+00A0⟩ and similar—on the screen and in the CSV export. Clean codes look exactly as before.
- A check’s own page now shows what that check could not see, and “What this audit could NOT check” no longer says “these rules found nothing” about rules that ran.
- The advice for missing sales data now points to a button that exists: Analytics → Settings → “Import historical data”.
- WP-CLI: three commands now stop on bad input instead of guessing, and two outputs keep gaps apart from findings.
- One request for a review, under the results—once per user, gone for good when you open it or choose “Don’t ask again”.
0.3.2 — September 19, 2026
- On WooCommerce older than 9.2 the two identifier checks now say they did not run, instead of reporting numbers.
- The evidence column no longer shows a Polish word on an English screen—an empty field now reads “(empty)”.
- The duplicate-identifier check now says when it had nothing to compare, with the same reason as the missing-identifier check.
- A finding on a variation now links straight to the tab where you fix it.
0.3.1 — September 18, 2026
- Both duplicate checks now see codes stored on variations, not only on products. On a store with variable products the numbers can go up after this update.
- The identifier check also reports a product that shares its number with its own variation. The SKU check does not—WooCommerce shows the parent’s SKU on a variation that has none, so for SKU that pair is how the platform behaves, not a fault.
- Variations sitting in the trash no longer count—anywhere.
- The three checks whose behavior changed carry a new version number, so “Changes since the previous audit” can tell you when a movement comes from us rather than from your store.
- Two additions to the identifier check’s knowledge page: what to do when the check is clean and the export file still shows no identifier, and why a number copied onto variations while a file is being built hides the gap rather than closing it.
0.3.0 — September 2026
Two new checks, both free and with no product cap: a product with no GTIN, UPC, EAN or ISBN, and two products sharing the same one. Shopping services use that identifier to match your offer to the same product sold elsewhere, so an empty or duplicated one is the usual reason an item quietly drops out of a feed. WooCommerce has had the field since 9.2 and nothing in the admin points at it.
- The missing-identifier check stays quiet in stores that do not use identifiers at all—one sentence instead of a list of the whole catalog. Handmade goods and services carry no barcode and need none.
- On a variable product the identifier belongs on each variation, so such a product gives one finding with the evidence “6 variations without a GTIN”, not six rows.
- Translations of one product are not reported as a duplicate, exactly as with SKU.
- On WooCommerce older than 9.2 the check says so by name, rather than reporting every product.
- After the update, “Changes since the previous audit” names the checks that are new. Two checks arriving at once means findings arriving at once, and the screen showed the movement without saying where it came from—so it read as if something had broken in your store overnight. A check that is new and found nothing stays out of the way.
- Seventeen checks now, in six groups. Why products drop out of your feed walks through the requirements one at a time, with a query for each.
0.2.1 — September 7, 2026
- New display name: Merchlint – Store Audit for WooCommerce. Same plugin, same address, same settings—the name now says what it does.
- Every rule links to its own page here, explaining what the finding costs, how the rule decides, how to fix it, and when it is not worth fixing.
- No change to what the audit checks or reports.
0.2.0 — September 1, 2026
First public release, on the WordPress.org plugin directory.
Fifteen checks, in five groups, with no product cap and no trial. Full list on the checklist page.
- Findings ranked by the revenue behind them, read from the store’s own order data
- Evidence on every finding—the field read, the value found, the threshold compared against
- “Start here”: the three items with the largest amount at stake, above the full list
- Deterministic results, with a screen showing what changed between two scans and why
- Per-currency revenue figures; never summed across currencies
- Permanent hiding of individual findings, surviving rescans and plugin updates
- Dashboard widget with the last audit result
- Nine WP-CLI commands:
scan,status,cancel,findings,rule,export,hide,unhide,hidden - Streaming CSV export, with spreadsheet formula injection disarmed
- Resumable scanning: 50,000 products in 91 seconds, surviving a killed PHP process
- No account, no sign-up, no telemetry, no outbound connections of any kind
Reviewed and approved by the WordPress.org plugin team on August 31, 2026, six days after submission.
In progress
Merchlint for Shoper—the same audit engine on a second platform, as a hosted app. The rules, the evidence and the “no writes” rule are identical; what differs is where the data comes from.
What is next, without dates
Dates on a one-person project are guesses, so there are none here. The order, however, is decided:
- Pro add-on—more checks (among them variation prices, dead stock, expired coupons, duplicate descriptions, variations a customer can’t select, and invalid GTINs), scan history, scheduled scans, email reports, and a report you can print or save as a PDF. The add-on is built and works, but you can’t buy it yet.
- New checks, in both the free and paid versions. What gets built is largely decided by what people ask for—see contact.
- A multi-store panel for agencies—only if agencies ask for it. See for agencies for why that condition is written down rather than assumed.
Where the authoritative list lives
The plugin’s own readme.txt in the WordPress.org directory is the canonical changelog; this page
follows it. If the two ever disagree, the directory is right and this page has a bug—tell us.