:quality(75))
Adobe Commerce 2.4.3 landed in August 2021 with over 370 bug fixes, a round of security work and three features worth planning around.
Live Search
The headline is Live Search, a SaaS search service that replaces the MySQL-based search engine. It runs on Elasticsearch and is built around relevance ranking and merchandising control rather than keyword matching.
What you get:
Typo tolerance. Fuzzy matching and auto-correct, so a misspelled query still finds the product.
Category and attribute filtering. Faceted search on colour, size, price and your own attributes.
A search analytics dashboard. What people are actually typing, which is the cheapest product and inventory research available to you.
A merchandising rules engine. Promote best-sellers for a season or push slower stock, without a deployment.
Live Search is an optional SaaS add-on rather than part of the core 2.4.3 release. That separation is deliberate: adopt it when you are ready, or stay on native Elasticsearch or MySQL.
Rate limiting for the Web APIs
The more storefronts decouple, the more traffic hits the APIs, and not all of it is yours. 2.4.3 adds configurable rate limiting for REST and GraphQL, aimed at:
integrations that retry without backoff logic,
scraping and product data extraction,
denial-of-service attempts from a single IP or customer account.
Limits are set per endpoint and per user type: guest, customer, admin. The defaults are sensible but generic, so tune them against your own traffic profile and integration list. If you run high-volume API consumers such as a PIM sync or an order import, rate limits are not a blocker. They are the contract you were already meant to be keeping.
PayPal Pay Later
2.4.3 adds PayPal Pay Later as a native payment method, letting customers split a purchase into interest-free instalments. Higher average order values, fewer carts lost at the payment step. PayPal runs the regulatory and creditworthiness checks, so that risk does not sit with you.
370+ fixes
Behind the features, 2.4.3 clears a large backlog:
Elasticsearch security configuration.
Inventory sync and stock management under load.
Asynchronous order processing and queue handling.
Database query performance on large catalogues.
Hundreds of small admin fixes.
A release this size is not a one-afternoon job. Three things catch people out:
Elasticsearch. If you self-host search, plan the infrastructure upgrade first rather than last.
Extensions. Third-party modules will not all declare 2.4.3 compatibility on day one. Staging exists for this.
Custom search. If you have custom search logic, decide early whether it coexists with the new engine or whether this is the moment to move to Live Search.
What this means for you
2.4.3 moves three things at once: what customers experience (Live Search), what your infrastructure will absorb (rate limiting) and how people pay (PayPal Pay Later). If you are already on 2.4.x this is a straightforward upgrade. If you are on 2.3, it is a reasonable business case for the major-version move you have been deferring.
Staying current on minor versions is unglamorous and it compounds. Skip four of them and the upgrade stops being routine work.