:quality(75))
Adobe Commerce 2.4.6 arrived in March 2023. It is not a headline-feature release — it addresses over 300 reported issues, adds PHP 8.2 support, and makes bulk imports considerably faster. For anyone running a live store, that combination is more useful than a new feature.
300 quality fixes
The 300 fixes are the things you and your developers hit on an ordinary Tuesday: edge cases in checkout flows, catalogue synchronisation problems, inventory management inconsistencies, and payment gateway integrations. They span the administration interface, GraphQL API reliability, database query optimisation and module compatibility.
If you run a large catalogue or a high transaction volume, that is fewer support tickets and fewer unexplained half-hours.
PHP 8.2 support
PHP 8.2 brings performance improvements and stricter type checking, which pays off over the life of the platform rather than on day one. The important part is that 2.4.6 removes the compatibility blocker — if PHP 8.2 was the reason your infrastructure modernisation stalled, it no longer is.
100,000 product records per minute
The bulk import engine in 2.4.6 processes 100,000 product records per minute. If you import from suppliers, update inventory across warehouses, or synchronise with an ERP, import windows go from hours to minutes.
The engine handles:
large CSV and JSON files with a streaming architecture
parallel batch processing
error handling with detailed reporting
memory-efficient operation on smaller server configurations
Before you upgrade
The upgrade itself is straightforward for most merchants. Two things need attention: custom extensions need verifying against PHP 8.2, and custom code should be reviewed for deprecated PHP features. Then benchmark an import, so you know the new throughput is actually being used rather than assumed.
What this means for you
Plan the upgrade for a quiet period and test it properly in staging. If you are on managed Adobe Commerce Cloud hosting, most of the operational side is handled for you — the work left is extension compatibility and benchmarking.