commercetools Now Sells Core Commerce and Product Catalog as Standalone Modules: What That Means for…
From Luma to Edge Delivery: The Migration Decision for Your Adobe Commerce Shop
From Luma to Edge Delivery: The Migration Decision for Your Adobe Commerce Shop
If your Adobe Commerce shop is still running on the classic Luma theme, or you invested in PWA Studio over the past few years, you are at a concrete decision point right now: Adobe is clearly pushing new reference storefronts toward Edge Delivery Services, Luma is showing its age, and Adobe itself no longer markets PWA Studio as the forward path. The question isn't whether you migrate anymore. It's where you migrate to: Adobe's own Edge Delivery stack, or a backend-agnostic frontend layer that keeps Adobe Commerce as your backend while avoiding the next lock-in.
The Luma and PWA Studio sunset moment
Luma is the original Magento 2 default theme: PHTML templates, Knockout.js widgets, server-side rendering. It works, but it shows its age. Core Web Vitals scores that no longer hold up against modern storefronts, a frontend stack that fewer new developers are trained on, and maintenance overhead that grows with every Adobe Commerce patch. PWA Studio was Adobe's first attempt at a React-based headless frontend for Magento. Adobe has since shifted its focus to Edge Delivery Services, and PWA Studio barely receives new reference features anymore. If you're sitting on either setup, you don't have the luxury problem of "which option is more elegant." You have a real decision, on a real timeline.
The problem many Adobe Commerce teams face right now
The reflex at a sunset trigger point is often: "Let's just take Adobe's new path, it's the official one." That's understandable, but it skips over an important fact: moving from Luma or PWA Studio to Edge Delivery Services is itself a full frontend rebuild, just in a new proprietary rendering model. You'd be trading an outdated lock-in for a fresh one. If you have to make this move anyway, it's worth using the moment to ask: do you really want to build another frontend that only works with Adobe Commerce, or do you want this migration to be your last one, regardless of what happens to your backend in three or five years?
Adobe's own path: Edge Delivery Services
Edge Delivery Services (EDS, also referenced on Adobe.com as Adobe Commerce Storefront) is built on Adobe's Franklin/Helix architecture: content comes from Google Docs or SharePoint, rendering runs through an edge delivery pipeline with strong out-of-the-box performance numbers. For teams deeply invested in Adobe Experience Manager, or that want to run Adobe as a full ecosystem, that's a coherent offer. The tradeoff: you're committing to another Adobe-native rendering model, and your content pipeline and component logic stay inside the Adobe world. For a detailed technical comparison of EDS against alternative Magento frontend frameworks, see our piece on Adobe Commerce Storefront (Edge Delivery) vs. Hyvä. If you want a generic side-by-side of all four common options (Edge Delivery, PWA Studio, custom headless, FMP), you'll find that broader overview in our decision hub, Adobe Headless in 2026. This piece deliberately doesn't repeat that comparison. It stays focused on the concrete Luma/PWA Studio sunset case.
The alternative: A backend-agnostic FMP layer on top of Adobe Commerce
The second path puts a Frontend Management Platform (FMP) directly on top of your existing Adobe Commerce APIs. Product catalog, pricing, cart, and checkout stay in Adobe Commerce. The frontend runs as a component-based layer, decoupled from the backend. The practical difference: if you ever want to move off Adobe Commerce, or connect a second backend for a different market segment, your frontend investment stays intact. You're not building into another Adobe-native model. You're building into a layer that supports 50+ backends, including Shopware, Shopify, commercetools, and Adobe Commerce itself. Migrations with founder support run at a median under 14 days, storefronts hit a field LCP median of 1.2 seconds, and WCAG 3.0 is ready out of the box instead of a retrofitted accessibility sprint.
Edge Delivery Services vs. a backend-agnostic FMP layer
| Dimension | Edge Delivery Services (Adobe's path) | Backend-agnostic FMP layer |
|---|---|---|
| Backend commitment | New, Adobe-native rendering model | Adobe Commerce stays your backend, frontend is decoupled |
| Future backend switch | Requires another frontend rebuild | Frontend stays intact through a backend switch |
| Time to market | Fast within the Adobe ecosystem | Migration typically under 14 days (median) |
| Content pipeline | Google Docs/SharePoint-based | Studio editor with live preview, no PR review for marketing content |
| Best fit for | Teams staying fully inside the Adobe ecosystem | Teams minimizing replatforming risk and frontend lock-in |
How to make the call
Three questions help you prioritize. First, is Adobe Commerce a long-term settled decision for you, or is a backend switch realistic within the next three to five years? Second, how much of your marketing organization should be able to build landing pages and campaigns on its own, without a developer ticket? Third, how much does it matter to you that your frontend investment keeps paying off if you build a second brand segment on a different backend. If you're unsure on question one, or answer "very important" to two and three, it's worth running the backend-agnostic path against Edge Delivery Services in a real comparison before you start migrating.
FAQ
Is PWA Studio dead? Adobe still maintains PWA Studio, but it clearly prioritizes Edge Delivery Services in its communication and new reference features. It's no longer a recommended starting point for new projects.
Do we have to give up Adobe Commerce as our backend to go FMP? No. The FMP layer sits directly on top of your existing Adobe Commerce APIs. Product data, pricing logic, and checkout stay unchanged in the backend.
How long does a move like this typically take? Migrations with founder support run at a median under 14 days, depending on your data and theme complexity.
Next steps
If your Luma theme or PWA Studio instance is hitting its limits, it's worth running the comparison before you commit to either path. See the Headless Frontend for Adobe Commerce, or book a 30-minute strategy call where we walk through your current Luma or PWA Studio situation in detail.
More from the Laioutr platform
About the author: Marcel Thiesies is Co-Founder of Laioutr. He works with Adobe Commerce teams moving off sunsetting Luma and PWA Studio setups onto a frontend that stays independent of the backend.
*All data is based on publicly available information, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of July 2026. Adobe Commerce and PWA Studio features may have evolved since.*