:quality(75))
Adobe Commerce (Magento) 2.4.8 landed on 8 April 2025. For anyone running a decoupled front end, the interesting part is not the infrastructure support — PHP 8.4, MariaDB 11.4 — but the GraphQL surface.
Richer order data
The CustomerOrder type gained fields including date_of_first_order, is_virtual and granular custom attributes on addresses. There is also an available_actions field, which tells the front end which controls belong on a given order — reorder, cancel — instead of your code inferring it from order state.
Guest flows improved too. A confirmCancelOrder mutation covers guest cancellation, and guest orders can now be merged into a customer account where the email addresses match.
Prices you can explain
Responses now expose original, pre-discount prices and any applied store credit or rewards. A headless front end can render an order summary that adds up on screen, and a customer service agent looking at the same order sees the same numbers. Fewer surprises, faster resolution.
Why the API and not the front end
With PWA Studio moved to maintenance, Adobe's position is clear enough: invest in the APIs and let you choose the front-end path — a traditional theme, Hyvä, or fully decoupled with the framework your team actually knows. 2.4.8 is the strongest version of that surface so far.
Building on it
Model capabilities, not screens. Drive UI logic from available_actions so features degrade gracefully.
Cache with intent. Design your GraphQL caching and edge keys around stable resources, and keep account-specific data out of shared caches.
Instrument the API layer from day one — error codes, latency, resolver hot-spots — so optimisation follows evidence rather than instinct.
Release in slices. Migrate the high-impact journeys first (PLP, PDP, checkout), then iterate.
2.4.8 is a quality-heavy release underneath all this, bundling hundreds of fixes that smooth out daily development. Not exciting — but it is the sort of thing you notice by not noticing it.