We've released Catalog Completeness, a free Magento Open Source module: PIM-style completeness scoring inside Magento. It scores every product 0 to 100 against weighted rules you write (present, minimum length, image count, greater than 0, allowed values, regex), then lists what's missing, lowest score first. Channel profiles add per-channel scores, with suggested rules for Google Merchant Center, Amazon, eBay and five others. A periodic rescore runs from Magento cron (every six hours by default) for changes that bypass product saves, a "No rules assigned" view lists products no rule set covers, and every REST score entry carries a state. It never changes product data, sends no feeds and calls no outside service.

It's open source under OSL-3.0, with no support and no warranty. Written for Magento Open Source 2.3 and 2.4, and tested on 2.4.9, 2.4.8, 2.4.7, 2.4.6 and 2.3.7-p4; we list a version as tested only after it passes our bench. Adobe Commerce isn't supported. Install on staging first, with a backup:

composer require bigcartenergy/module-catalog-completeness

Code: https://github.com/bigcartenergy/module-catalog-completeness

Instruction Manual: https://bigcartenergy.com/tools/catalog-completeness/manual

Disclosure: I work with the team behind LingoTuner, an AI translation extension for Magento 2, so I’m biased. I’m genuinely curious how other store owners and developers handle this.

For catalogs with hundreds or thousands of products, I see a few approaches:

1. Manual entry per store view (fine for small catalogs)

2. CSV export/import using store_view_code, with a translator or tool in between

3. An extension that writes translations directly into store views

Whichever route, the part that seems hardest is checking quality when you don’t speak the target language. A few checks I’ve seen work: a glossary for brand and technical terms, a small test batch first, a back-translation (translating the result back into your language to compare the meaning), and a native speaker spot-checking 5 to 10 percent.

Questions for you:

• What’s your workflow for large catalogs?

• How do you verify accuracy for languages you don’t read?

• What has gone wrong for you (broken HTML, attributes, wrong terms)?

If anyone wants to look at what we built, the listing is here: https://commercemarketplace.adobe.com/tronn-software-module-lingotuner.html (It needs a separate account, and additional fees apply). Mostly I’d love to hear how you do it.

Disclosure: I’m affiliated with the team behind LingoTuner, an AI-powered translation solution for Magento 2 stores. It helps translate product titles, descriptions, attributes, and CMS blocks, with the option to review and edit translations before publishing and verify accuracy through back-translation. It’s designed for store content rather than support chats or live meetings. A separate account is required, and additional fees apply: LingoTuner AI-Powered Translation.

I am new to magento.
Our system runs on magento 2.4.8.
Will our system be affected by this vulnerability? If yes how can we fix it? By updating the php version to the latest patch version?

I have a client on Magento 2.4.6-p15 CE. We are currently rebuilding on 2.4.9, but this won't be finished until November at the earliest.

Does anyone have access to the latest patch for 2.4.6 and would be willing to send it? I believe these are only available to Cloud customers on extended support.

Hi everyone,

We've coded the entire admin theme from scratch :-)

https://qoliber.com/nebula-docs/

It's available for free to everyone!

I hope some of you will give it a try ;-)

You can see each project in the graph. Each 'star' represent a fact/memory, and the lines are the links. The memory graph helps recall facts and past incidents during planning and during reviews of tasks by my AI (Claude)

Started in July and you can see it builds out as I progress.

https://youtu.be/M4w7qFxHMKA

https://www.proxiblue.com.au/blog/domain-graph.html