Two products with the same SKU throw off stock levels, integrations and every export file your store\nproduces. Two products with the same GTIN tell a shopping service they are the same item, so one of\nthem quietly disappears from search. A product with no identifier at all usually drops out of the\nfeed altogether.<\/p>\n\n
None of this breaks your store, which is why it goes unnoticed for years. Nothing in the WooCommerce\nadmin points at any of it.<\/p>\n\n
This plugin checks three things and nothing else:<\/p>\n\n
It never writes to your catalogue<\/strong>. There is no \"Fix it\" button, and there will not be one: a\nbulk change to product data is not something a report should do on your behalf. Every finding shows\nthe value that was read, so you can check the claim before you act on it.<\/p>\n\n It reads no order data, which makes the scan far cheaper than a full audit. The scan still runs\nin a single request, so on a very large catalogue it can run into your host's time limit \u2014 the\nscreen says so when that becomes likely, and the WP-CLI command has no such limit.<\/p>\n\n Every finding shows the field that was read and the value found, with a link straight to the product\nin your admin. A rule that could not run says so by name \u2014 on WooCommerce older than 9.2 the\nidentifier field does not exist at all, and the report says that rather than reporting every product\nas faulty.<\/p>\n\n The scanning engine is the one behind Merchlint, a full WooCommerce catalogue audit from the same\nauthor. This plugin carries its own copy with its own class names, so both can run side by side.<\/p>\n\n\n For large catalogues there is a WP-CLI command: No. It reads the catalogue and writes nothing back. The only thing it stores is the last result, so\nthat reloading the page does not require another scan.<\/p><\/dd>\n No. Translations of one product share an SKU on purpose, and the check treats one translation group\nas one product. Polylang and WPML are both read.<\/p><\/dd>\n No. If not one product in the catalogue has the field filled, the check stays quiet and tells you\nwhy, in one sentence.<\/p><\/dd>\n\n<\/dl>\n\n\nEvidence, not adjectives<\/h4>\n\n
Where the audit engine comes from<\/h4>\n\n
\n
wp merchlint-duplicate-sku-finder scan<\/code>.<\/p>\n\n\n\n
Does it change anything in my shop?<\/h3><\/dt>\n
My shop is multilingual. Will translations be reported as duplicates?<\/h3><\/dt>\n
I do not use GTINs at all. Will I get a list of every product?<\/h3><\/dt>\n
0.1.1<\/h4>\n\n
\n
scope<\/code>, and each Edit link says which product it\nedits, so a screen reader no longer reads eight links called only \"Edit\".<\/li>\n0.1.0<\/h4>\n\n
\n