ChatGPT Headless Adobe Commerce & Magento 2026
Summary
Key takeaways
- Headless Adobe Commerce separates the storefront from the commerce backend, allowing frontend teams to release and scale independently through GraphQL and REST APIs.
- Adobe now directs new storefront projects toward Edge Delivery Services, while PWA Studio remains supported primarily through maintenance and compatibility releases.
- Edge Delivery Services is the strategic storefront for Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer, using commerce drop-ins for account, cart, checkout, payment, discovery, and B2B workflows.
- A custom Next.js, Vue, Nuxt, or similar frontend is better suited to merchants that need full rendering control, multiple commerce backends, native apps, or highly customized digital experiences.
- Hyvä is not headless, but it can be a lower-risk alternative when the real business problem is a slow Luma storefront rather than a need for architectural decoupling.
- Magento Open Source can run a custom GraphQL-based headless frontend, but it does not support the Edge Delivery Services commerce drop-in path.
- Headless architecture does not automatically improve SEO or performance; canonical content, product data, prices, specifications, and structured data still need to reach crawlers efficiently.
- Extensions become a major migration concern because every storefront-facing customization must expose its data through GraphQL, REST, Catalog Service, or API Mesh.
- B2B stores with complex quotes, approvals, and customized checkout flows should usually migrate progressively rather than replacing the entire storefront in one release.
- The architecture decision should begin with the Adobe Commerce backend, license, business requirements, existing customizations, and operating model rather than with a preferred JavaScript framework.
When this applies
This applies when an Adobe Commerce or Magento merchant needs independent frontend releases, multiple customer-facing channels, custom rendering, shared APIs for web and mobile applications, or tighter integration between commerce, CMS, PIM, ERP, and other systems. It is particularly relevant when moving to Adobe Commerce as a Cloud Service, adopting Adobe Commerce Optimizer, replacing a heavily customized PWA Studio storefront, or building multi-brand and multi-region experiences. A custom headless architecture is strongest when the organization already has experienced frontend engineers and the long-term roadmap justifies owning a separate frontend application.
When this does not apply
This does not apply when the main problem is simply poor Luma performance, the business operates one straightforward storefront, and the frontend team is small. In those situations, Hyvä may deliver the required speed and UX improvements with substantially less architectural complexity. Headless can also be the wrong choice when the organization is not prepared to own frontend hosting, API orchestration, monitoring, additional deployment pipelines, and ongoing framework upgrades. A decoupled architecture should solve a concrete business or technical constraint rather than be adopted because headless is perceived as more modern.
Checklist
- Identify whether the backend is Adobe Commerce as a Cloud Service, Adobe Commerce on Cloud, on-premises Adobe Commerce, or Magento Open Source.
- Define the business reason for moving away from the current storefront architecture.
- Inventory all active extensions and document the storefront data each one provides.
- Check whether every required extension exposes its data through GraphQL, REST, Catalog Service, or another supported API.
- Decide between Edge Delivery Services, Adobe Commerce Optimizer Headless, a custom frontend, Hyvä, or maintaining the existing PWA Studio implementation.
- Map catalog, cart, checkout, customer-account, pricing, and B2B API requirements.
- Identify ERP, PIM, CMS, search, and other data that may need to be aggregated through API Mesh.
- Document custom checkout, quote, approval, and account workflows before selecting the migration approach.
- Establish baseline Core Web Vitals, conversion rate, organic traffic, and crawl statistics before migration.
- Ensure important product names, prices, specifications, and structured data are available in the initial HTML where required.
- Map all indexable URLs and prepare redirects before changing storefront routing.
- Model frontend hosting, Adobe licensing, API usage, content-request metering, and ongoing engineering costs.
- Use a progressive rollout for stores with complex B2B functionality or heavily customized transactional flows.
- Launch content and high-value catalog pages before moving checkout and account functionality where a phased migration is appropriate.
- Compare each migration phase against the original performance, SEO, conversion, and stability baselines before expanding the rollout.
Common pitfalls
- Choosing a frontend framework before deciding which Adobe Commerce architecture and licensing model the business actually needs.
- Starting a new PWA Studio implementation despite Adobe directing new storefront development toward Edge Delivery Services.
- Assuming Hyvä is headless simply because it provides a modern, high-performance frontend.
- Expecting headless architecture alone to solve Core Web Vitals, SEO, or conversion problems.
- Discovering late that important Magento extensions do not expose the APIs required by the new storefront.
- Moving a complex B2B checkout to a new frontend in one release without a progressive migration and rollback strategy.
- Rendering critical product information only in client-side JavaScript and reducing visibility for non-JavaScript crawlers and AI systems.
- Underestimating the ongoing cost of owning a custom React or Vue frontend, hosting, monitoring, and framework upgrades.
- Migrating URLs without a complete redirect and canonicalization plan.
- Adopting headless when a simpler Hyvä rebuild would solve the actual performance and UX problem with less risk.
SHORT ANSWER
Headless Adobe Commerce (Magento) is a storefront that runs separately from the commerce backend and reads data through GraphQL or REST APIs. In 2026, PWA Studio gets only maintenance releases, and Adobe directs new storefronts to Edge Delivery Services. Elogic Commerce recommends Edge Delivery Services on Adobe’s SaaS products, a custom Next.js frontend for multi-backend stacks, and Hyvä when a fast theme is enough.
Key takeaways
- PWA Studio is not deprecated, but its releases from May 2024 to May 2026 contain bug fixes and compatibility updates. Version 14.5.1 (May 2026) adds PHP 8.5 support.
- Adobe’s recommended storefront is Adobe Commerce Storefront powered by Edge Delivery Services (EDS). Its drop-in components need an Adobe Commerce as a Cloud Service (ACCS) or Adobe Commerce Optimizer (ACO) license.
- Adobe Commerce on Cloud (PaaS) and on-premises stores can use EDS from version 2.4.8, but only with an ACO license. Magento Open Source is not supported on this path.
- Adobe says that the AEM CIF storefront is in maintenance mode and must not be used for new projects.
- The Hyvä Theme is free and open source since November 10, 2025. It is not headless, but it is often the fastest way to fix a slow Luma store.
- Adobe notes that the LLM crawlers behind AI answers do not execute JavaScript. Product names, prices and specifications must be in the initial HTML of each page that you want AI answers to cite.
This guide is for Adobe Commerce and Magento teams that must select a storefront architecture in 2026. The headless ecommerce development team at Elogic Commerce, an Adobe Commerce Silver Solution Partner, wrote it from Adobe’s current documentation, product descriptions and release notes.
What is headless Adobe Commerce?
Headless Adobe Commerce is an architecture in which the storefront runs separately from Adobe Commerce and gets products, prices, carts and orders through APIs. The backend keeps the commerce logic. The frontend team can release, test and scale on its own schedule. Elogic Commerce uses the term for any Adobe Commerce or Magento store that does not render pages with the Luma or Blank theme.
In a classic Magento store, PHP renders each page with the Luma or Blank theme. In a headless store, a separate application renders the pages. This application can run in the browser, on a Node.js server or on an edge network.
Adobe Commerce gives a headless storefront three API layers:
- The core GraphQL and REST APIs for catalog, cart, checkout, customer accounts and B2B features.
- Catalog Service, Live Search and Product Recommendations. Catalog Service is a fast, read-only GraphQL API for product data.
- API Mesh for Adobe Developer App Builder, which combines several APIs into one GraphQL endpoint.
Headless is an architecture decision, not a product. You still select a frontend technology, a hosting model and a license. Make these three decisions before you select a framework.
Is “Adobe headless commerce” the same as AEM headless?
No. Adobe Experience Manager (AEM) headless is a content API that sends Content Fragments to any frontend. Adobe headless commerce is a decoupled storefront on Adobe Commerce APIs. The two often work together: AEM manages the content and Adobe Commerce runs the transactions. Adobe now names Edge Delivery Services as the reference architecture for both.
Adobe states that the AEM CIF storefront and its CIF Core Components are in maintenance mode and must not be used in new projects. Existing CIF sites can move to Edge Delivery Services page by page. They can also replace CIF components with Commerce drop-in components.
What happened to Magento PWA Studio?
PWA Studio is still maintained, but it is not where Adobe invests. Adobe shipped nine PWA Studio releases from May 2024 to May 2026. Most of them contain bug fixes and compatibility updates, such as PHP 8.4 and PHP 8.5 support. Elogic Commerce advises merchants to keep a stable PWA Studio store, but not to start a new build on it.
PWA Studio is Adobe’s open-source toolkit for React progressive web app (PWA) storefronts. Venia is its reference storefront. It works with Adobe Commerce and Magento Open Source through the GraphQL API. The release notes show the direction:
- Version 14.5.0 (February 2026) lists bug fixes and documentation updates.
- Version 14.5.1 (May 2026) lists PHP 8.5 support, an Axios security update and bug fixes.
- The same known issue, a guest cart ID that stays after logout, appears in the release notes from 14.0.1 (July 2024) to 14.5.1 (May 2026).
- Adobe publishes Lighthouse lab scores for Venia with each release. For 14.5.1, desktop performance is 98 on all four tested page types. Mobile performance is 67 to 75.
There is also a hosting constraint. Adobe Commerce on Cloud does not run Node.js processes, so a PWA Studio storefront on Cloud uses the UPWARD PHP connector instead of UPWARD-JS.
| Version | Released | Main content |
|---|---|---|
| 14.0.0 | May 2024 | Accessibility improvements and bug fixes |
| 14.0.1 | July 2024 | PREX compatibility; Node.js 18 minimum |
| 14.1.0 | September 2024 | Release tag without published highlights |
| 14.2.0 | March 2025 | PHP 8.4 support, Cash on Delivery payment, bug fixes |
| 14.3.0 | July 2025 | Node.js 20, multistore setup, Product Recommendations package |
| 14.3.1 | August 2025 | PWA Live Search package |
| 14.4.0 | October 2025 | Add to Cart and cart fixes; CSP nonce fix |
| 14.5.0 | February 2026 | Fixes for robots meta tags and canonical tags; documentation |
| 14.5.1 | May 2026 | PHP 8.5 support; Axios security update |
Table 1. PWA Studio releases, 2024 to 2026. Source: magento/pwa-studio release notes on GitHub, reviewed by Elogic Commerce in September 2026.
What should you do if you run PWA Studio today?
- If the store is stable and meets your KPIs, keep it. Budget compatibility work for each Adobe Commerce release, and put the store under a Magento support and maintenance plan with a named owner.
- Stop new feature work in Venia code that will not move to the next storefront.
- Move shared logic into APIs, such as GraphQL queries and API Mesh, so the next frontend can use it again.
- Plan the next storefront now: Edge Delivery Services with an ACO license, a custom frontend or Hyvä.
What are the headless options for Adobe Commerce in 2026?
Elogic Commerce sees six storefront options for Adobe Commerce in 2026. Three are headless builds: Edge Delivery Services with drop-ins, Optimizer Headless with your frontend, and a custom frontend on Adobe Commerce GraphQL. The other three are PWA Studio, Hyvä, and a hybrid of Luma and Edge Delivery Services. Only the three headless builds are strategic for a new project.
| Option | Headless | Backends | License | Best fit | Main risk |
|---|---|---|---|---|---|
| Edge Delivery Services storefront with drop-ins | Yes | ACCS; ACO; PaaS and on-premises 2.4.8+ with ACO | Included with ACCS and ACO. A PaaS license alone does not include drop-ins. | New storefronts on Adobe SaaS; content-heavy catalogs | Custom checkout logic needs APIs and drop-in extensions |
| ACO Headless with your own frontend | Yes | Adobe Commerce and other engines through catalog ingestion | ACO Headless base package, without the EDS storefront | Multi-brand catalogs; teams that own a React or Vue frontend | You own the frontend and the checkout integration |
| Custom frontend on Adobe Commerce GraphQL (Next.js, Nuxt, Alokai) | Yes | PaaS, on-premises, Magento Open Source, ACCS APIs | No extra Adobe license; you pay for frontend hosting and the team | Full control of rendering; several backends; native apps | You own the frontend life cycle and each API gap |
| PWA Studio (Venia) | Yes | PaaS, on-premises, Magento Open Source | Open source | Existing PWA Studio stores | Maintenance releases only |
| Hyvä Theme (server-rendered) | No | PaaS, on-premises, Magento Open Source; not ACCS | Theme free since November 10, 2025; Hyvä Enterprise and Hyvä Checkout are commercial | Luma stores that need speed without a new architecture | Not API-first |
| Luma and EDS hybrid with Luma Bridge | Partly | PaaS and on-premises with ACO | ACO | Phased migration away from Luma | Two storefronts to maintain in parallel |
Table 2. Elogic Commerce Headless Architecture Map 2026. Sources: Adobe Commerce Storefront documentation, Adobe product descriptions, PWA Studio release notes, Hyvä.
Your hosting model limits your storefront choice. If you have not decided between SaaS and PaaS, read our Adobe Commerce SaaS vs PaaS decision guide first.
How does the Adobe Commerce storefront on Edge Delivery Services work?
Adobe Commerce Storefront powered by Edge Delivery Services sends HTML, CSS and JavaScript from an edge network. Drop-in components then load commerce data from Adobe Commerce APIs in the shopper’s browser. Authors edit pages as documents. Elogic Commerce treats it as the default storefront for Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer.
A project starts from the Adobe Commerce boilerplate, a Git repository with a working storefront. Developers push code to GitHub, and Edge Delivery Services builds and publishes the site.
A drop-in component is a package of UI and logic for one commerce task, for example the cart or the checkout. Adobe lists 11 B2C drop-in packages: account, auth, cart, checkout, order, payment services, product details, recommendations, wishlist, personalization and product discovery. B2B drop-ins cover company accounts, quotes, purchase orders and requisition lists.
You change drop-ins with CSS variables, label overrides, slots and extension hooks. You do not edit the package source.
Adobe states that a project that starts from the boilerplate gets a stable Lighthouse score of 100 on mobile and desktop. The AEM GitHub bot fails a pull request if the score falls below 100, with a small buffer.
Which limits must you plan for?
- Up to 1 million pages per site and 50,000 URLs per sitemap file.
- Up to 100,000 redirects per site. EDS does not support wildcard or query-parameter rules, so put pattern rules on your CDN.
- 200 requests per second for each shopper on each aem.page or aem.live host name.
- Lowercase routes only. Default Adobe Commerce email links, such as /customer/account/forgotPassword, break until you edit the email templates.
- Product pages need prerendering or bring-your-own-markup. Without it, they return 404 errors.
Which pages should move first?
Adobe recommends a phased launch in this sequence:
- Home and content pages with high acquisition traffic.
- Catalog pages, which are product listing pages and product detail pages, with high conversion traffic.
- Checkout and account pages.
Adobe recommends a progressive implementation when B2B modules, a heavily customized checkout or many transactional integrations exist. A full implementation fits a store with few checkout integrations and no B2B modules.
Can Adobe Commerce on Cloud (PaaS) or on-premises use Edge Delivery Services?
Yes, from Adobe Commerce 2.4.8, but a PaaS license alone does not include drop-in components. You must add an Adobe Commerce Optimizer license, install the Storefront Compatibility Package and connect Catalog Service. Magento Open Source is not supported. Elogic Commerce recommends that you confirm these prerequisites before you estimate the build.
| # | Requirement | Why it matters |
|---|---|---|
| 1 | Adobe Commerce 2.4.8 or later (2.4.9 became generally available on May 12, 2026) | Adobe lists 2.4.8 as the minimum version for this storefront path |
| 2 | Adobe Commerce Optimizer license | A PaaS license alone does not include drop-in components |
| 3 | Storefront Compatibility Package (PHP) | Adds the GraphQL schema that the cart, checkout, account and order drop-ins need |
| 4 | Storefront Compatibility B2B Package | Needed for B2B drop-ins after you configure Adobe Commerce B2B |
| 5 | Services Connector and Catalog Service, then Live Search and Product Recommendations | Drop-ins read catalog data from these services |
| 6 | Storefront events through the Adobe Client Data Layer | Live Search and Product Recommendations need these events |
| 7 | Luma Bridge (optional) | Shares cart and sign-in sessions between Luma and EDS during a migration |
| 8 | Adobe Commerce Optimizer Connector | Syncs catalog and pricing from PaaS into ACO |
Table 3. PaaS checklist for Edge Delivery Services. Source: Adobe Commerce Storefront “Backend options”, updated September 11, 2026.
On this path, part of the effort is backend Adobe Commerce development: the compatibility package, API access for your extensions and the catalog sync.
When is a custom headless frontend the better choice?
Select a custom frontend, such as Next.js or Alokai, for full control of server-side rendering, several backends, a native app or Magento Open Source. You own the frontend code, the hosting and the upgrades. Elogic Commerce recommends it for teams with senior React or Vue engineers and a roadmap that needs frequent frontend releases.
A custom frontend usually combines three data sources. It uses Adobe Commerce GraphQL for cart, checkout and account. It uses Catalog Service or ACO Merchandising Services for fast catalog reads. It uses API Mesh to add CMS, PIM or ERP data through one endpoint, which is systems integration work.
- Performance on PaaS. The GraphQL Application Server (Adobe Commerce 2.4.7 and later) keeps the application state between requests. Adobe says that it cuts GraphQL response time by up to 30%. It is not available for Magento Open Source and does not work with AWS S3 remote storage.
- Metering on SaaS. ACCS licenses Storefront Content Requests. One request is one page view or five API calls, and JSON calls from a headless frontend count. Model this before you design a client that makes many API calls.
- Licensed path on Adobe SaaS. The Adobe Commerce Optimizer Headless package includes Merchandising Services, Product Visuals and App Builder, but not the EDS storefront.
- Frameworks. Alokai (formerly Vue Storefront) has a framework-agnostic Magento 2 integration with an SDK and middleware. GraphCommerce is a React and Next.js storefront for Adobe Commerce. Check the maintenance status of any community PWA theme before you commit to it.
A custom frontend also needs backend work when an extension has no API. A custom GraphQL query or a small Magento extension development task exposes the data. A native app uses the same pattern: mobile commerce development on the same GraphQL layer lets one API serve the web store and the app.
Hyvä vs PWA Studio: is Hyvä a headless alternative?
Hyvä is not headless. It is a server-rendered Magento theme built with Alpine.js and Tailwind CSS. It removes most of the speed problems that made merchants select PWA Studio. Since November 10, 2025, the Hyvä Theme is free and open source. For many Luma stores, Elogic Commerce, a Hyvä Bronze Partner, sees Hyvä as the lower-risk step before a headless rebuild.
- License. Hyvä relicensed the theme under OSL 3.0 and AFL 3.0. Hyvä Checkout, Hyvä Enterprise (compatibility for Adobe Commerce features) and Hyvä Commerce stay commercial.
- Where it runs. Adobe Commerce on Cloud, Adobe Commerce on-premises and Magento Open Source. ACCS does not support Luma storefronts and accepts only out-of-process extensions, so a PHP theme such as Hyvä cannot run on it.
- Evidence. Elogic Commerce’s Hyvä rebuild for DIGI, a US consumer electronics retailer, is documented as a 109% revenue growth case.
Hyvä is usually the better choice when you have one backend, content in Magento and a small frontend team, and you need results in weeks. For scope and timeline, see our Hyvä theme development service.
How does headless architecture affect SEO and AI search visibility?
Server-side rendering is not a ranking signal, but it decides what non-JavaScript crawlers see. Adobe notes that the LLM crawlers behind AI answers do not execute JavaScript. Product names, prices, specifications and structured data must be in the initial HTML. Elogic Commerce sets rendering tiers by Google Search Console crawl demand, not by SKU count.
Adobe’s guidance is to put the canonical content of a page in the initial HTML and to load non-critical elements later. Adobe also tested server-side header and footer inlining on aem.live and measured no SEO upside.
Adobe gives a warning example. A consumer brand built about six million product listing pages for SEO, but only about 18,000 of them had crawl demand. The brand spent about 18 months on the crawl backlog.
Use these rules for a headless migration:
- Tier 1 pages (product pages with demand, curated category pages, the home page and top landing pages): put the canonical content in the initial HTML.
- Tier 2 elements (recommendations, personalized modules): client-side rendering is acceptable.
- Tier 3 URLs (facets, sort orders, internal search): keep them out of the index. Use query parameters, not paths.
- Send legacy facet URLs to the canonical category page with a 301 redirect, or return 410 when no match exists.
- Plan redirects early. EDS allows up to 100,000 redirects per site and no wildcard rules.
- Check prerender limits. AEM Commerce Prerender has a cap of about 10,000 products per category path.
- Use ProductGroup and hasVariant structured data for product variants that have separate pages.
If AI answers are a channel for you, our ecommerce GEO services cover these checks for AI search.
What does a headless Adobe Commerce build cost?
Adobe does not publish list prices. Cost has four drivers: the storefront license, the frontend build, API work for extensions, and run costs. Run costs include content requests and App Builder packs. Elogic Commerce recommends that you estimate each driver separately before you compare architectures.
| Cost driver | EDS on ACCS or ACO | Custom frontend on PaaS | Hyvä on PaaS or Open Source | Keep PWA Studio |
|---|---|---|---|---|
| Storefront license | Included in ACCS and ACO | None from Adobe | Theme free; Enterprise and Checkout are paid | Free |
| Build effort | Medium: boilerplate and drop-ins | High: complete frontend | Low to medium: theme and compatibility modules | None: maintenance only |
| Extension rework | API access for each extension | APIs and frontend UI for each extension | Hyvä compatibility modules | Already done |
| Run cost | Content requests and App Builder packs | Node.js hosting, CDN and frontend team | PHP hosting as today | Node.js or UPWARD hosting and compatibility work |
| Team skills | JavaScript, EDS blocks, drop-ins | Senior React or Vue, GraphQL | Magento frontend, Tailwind CSS, Alpine.js | React and Magento GraphQL |
Table 4. Relative cost drivers by storefront option. Elogic Commerce analysis based on Adobe product descriptions, September 2026.
To size the team part of this table, use the Adobe Commerce Team Cost Calculator. If you need senior engineers for a fixed period, you can hire Magento developers from Elogic Commerce as a dedicated team.
How do you choose a headless architecture?
Start from your backend and license, not from the frontend framework. If you move to Adobe Commerce as a Cloud Service, the storefront is Edge Delivery Services. If you stay on PaaS, select Optimizer with Edge Delivery Services, a custom frontend or Hyvä. The Elogic Commerce Headless Decision Matrix 2026 maps seven common situations to one recommendation each.
| Your situation | Recommended architecture | Why | Watch out for |
|---|---|---|---|
| You move to ACCS before your Cloud deadline (June 1, 2027 or June 1, 2028) | EDS storefront with drop-ins | Included in the license. ACCS does not support Luma. | Rebuild of the custom checkout UI |
| PaaS on Luma, slow pages, healthy backend | Hyvä, or ACO with EDS for catalog pages | Fast result without a backend migration | ACO license cost; two storefronts during the hybrid phase |
| PaaS on PWA Studio with heavy customization | Keep PWA Studio short term; plan EDS with ACO or a custom Next.js frontend | Venia gets maintenance releases only | Compatibility work for each Adobe Commerce release |
| Magento Open Source | Hyvä, or a custom frontend on GraphQL | EDS drop-ins do not support Open Source | No GraphQL Application Server |
| Multi-brand or multi-region catalog, often with AEM | ACO catalog views and policies with EDS | Catalog views replace the website, store and store view model | 50 catalog sources; 100 catalog variations in the base license |
| B2B with complex quotes and approvals | Progressive: EDS for content and catalog; keep checkout and account on the current storefront | Adobe recommends a progressive path when B2B modules exist | B2B Compatibility Package on PaaS |
| Web store and native app | Custom frontend or ACO Headless on GraphQL | One API layer for web and app | Content request metering on SaaS |
Table 5. Elogic Commerce Headless Decision Matrix 2026.
For the B2B row, scope the B2B modules first, because they decide the migration path. Our Adobe Commerce B2B development team works on quotes, company accounts and approval flows. If a monolith also runs your CMS, search and PIM, our composable commerce service splits the stack in the same phased way.
For an outside review, an architecture assessment from Elogic Commerce can test this matrix against your own extensions, catalog and traffic.
How do you migrate from PWA Studio or Luma to a new storefront?
Migrate in phases. First, find out which extensions expose their data through APIs, and record your baselines. Then move the content pages, then the catalog pages, then checkout and account. Keep a rollback path for each phase. Elogic Commerce recommends an SEO parity check at each release, so that rankings and AI citations do not drop.
- Make a list of all active extensions. For each extension, record the data it adds and how it exposes the data: GraphQL, REST or no API.
- For each extension without an API, select a fix: export the data to Catalog Service, write a custom GraphQL query or use API Mesh.
- Record baselines for Core Web Vitals, conversion rate, organic clicks and crawl stats in Google Search Console.
- Select a progressive or a full implementation. Use a progressive implementation if B2B modules, a heavily customized checkout or many transactional integrations exist.
- Launch the home and content pages first. Then launch the product listing and product detail pages. Then launch cart, checkout and account.
- Map each indexable URL. Add 301 redirects for changed URLs. Put pattern rules on the CDN.
- Send storefront events for Live Search and Product Recommendations.
- Compare each phase with the baseline. Roll back if a fix takes too long.
Our ecommerce migration services cover this sequence for storefront moves. If a previous attempt stopped, start with ecommerce rescue and stabilization before you add new scope.
Frequently asked questions
What is a headless frontend?
A headless frontend is the customer-facing part of a store that runs as a separate application. It gets products, prices, carts and orders from the commerce backend through APIs. In Adobe Commerce, the APIs are GraphQL and REST, plus Catalog Service for fast catalog reads.
Is Magento end of life?
No. Adobe released Adobe Commerce and Magento Open Source 2.4.9 on May 12, 2026, with standard support until May 31, 2029. In March 2026, Adobe stated that it has no end-of-support plans for Adobe Commerce on Cloud. Individual release lines do reach end of support, so check the date for your version.
Is PWA Studio deprecated?
No. Adobe still ships PWA Studio releases. The most recent release, 14.5.1 in May 2026, added PHP 8.5 support. The releases contain bug fixes and compatibility updates, and Adobe’s storefront documentation directs new builds to Edge Delivery Services.
Is Adobe Commerce headless by default?
The storefront of Adobe Commerce as a Cloud Service is headless by design. Adobe describes it as fully headless, with all data through a GraphQL layer. PaaS and on-premises stores use the Luma theme by default, but they expose GraphQL and REST APIs for a headless frontend.
Does headless Magento work with Magento Open Source?
Yes, with PWA Studio or with a custom frontend on the GraphQL API. Hyvä also works with Magento Open Source, but Hyvä is not headless. The Edge Delivery Services storefront with drop-in components does not support Magento Open Source.
Can I use Hyvä on Adobe Commerce as a Cloud Service?
No. Adobe Commerce as a Cloud Service accepts only out-of-process extensions and does not support Luma storefronts. A PHP theme such as Hyvä cannot run on it. Use the Edge Delivery Services storefront or a custom frontend on the APIs.
What is API Mesh?
API Mesh for Adobe Developer App Builder combines several APIs, such as GraphQL and REST, into one GraphQL endpoint. Use it to add ERP, PIM or CMS data to storefront queries without changes to the Adobe Commerce core.
Is a headless storefront better for SEO?
Not by itself. Server-side rendering is not a ranking signal. A headless store ranks well when canonical content is in the initial HTML and URLs stay stable. Facet URLs must stay out of the index, and redirects must be complete.
Which Adobe Commerce version do I need for Edge Delivery Services on PaaS?
Adobe lists Adobe Commerce 2.4.8 or later for this path. You also need an Adobe Commerce Optimizer license and the Storefront Compatibility Package. Version 2.4.9 became generally available on May 12, 2026.
How long does a move from PWA Studio to Edge Delivery Services take?
It depends on three factors: the number of extensions that need new APIs, the amount of custom checkout logic, and the use of B2B modules. Adobe recommends small milestones with a rollback plan for each. Elogic Commerce gives a dated delivery plan after discovery.
How Elogic Commerce helps with headless Adobe Commerce
Elogic Commerce is an Adobe Commerce Silver Solution Partner and a Hyvä Bronze Partner. Since 2009, its 200+ specialists have delivered 500+ ecommerce projects. Clients rate Elogic Commerce 5.0 across 64 Clutch reviews, and its post-launch NPS is 70.
Result example: Benum is a Nordic B2B distributor on Adobe Commerce. Elogic Commerce increased its checkout conversion rate by 31% and reduced its average page load time by 65% (Benum case study).
Services for this topic include headless and Hyvä storefronts, Edge Delivery Services projects, Magento performance optimization and long-term support.
GET A STOREFRONT ARCHITECTURE ASSESSMENT
Sources and methodology
From September 20 to September 29, 2026, Elogic Commerce reviewed Adobe documentation, Adobe product descriptions, the magento/pwa-studio release notes and vendor sources. Search data comes from Ahrefs (US, September 29, 2026). All dates in this article are absolute. Elogic Commerce reviews this page every quarter. Next review: December 15, 2026.
- Adobe, “Backend options”, Adobe Commerce Storefront documentation, updated September 11, 2026. https://experienceleague.adobe.com/en/tools/commerce-storefront/get-started/backends/
- Adobe, “Plan your storefront project”, updated August 31, 2026. https://experienceleague.adobe.com/en/tools/commerce-storefront/setup/
- Adobe, “Drop-ins at a glance”, updated September 2, 2026. https://experienceleague.adobe.com/en/tools/commerce-storefront/get-started/architecture/drop-ins-at-a-glance/
- Adobe, “SSR and crawlability”, Adobe Commerce Storefront documentation. https://experienceleague.adobe.com/en/tools/commerce-storefront/setup/seo/ssr-and-crawlability/
- Adobe, “Frequently Asked Questions”, Adobe Commerce Storefront, updated September 10, 2026. https://experienceleague.adobe.com/en/tools/commerce-storefront/troubleshooting/faq/
- Adobe, “Performance best practices”, Adobe Commerce Storefront. https://experienceleague.adobe.com/en/tools/commerce-storefront/get-started/performance/
- Adobe, “Keeping it 100”, Edge Delivery Services documentation. https://www.aem.live/developer/keeping-it-100
- Adobe, “Content and Commerce”, AEM as a Cloud Service, updated June 5, 2026. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/content-and-commerce/introduction
- Adobe, PWA Studio release notes 14.0.0 to 14.5.1, GitHub. https://github.com/magento/pwa-studio/releases
- Adobe, “Deploy to Adobe Commerce”, PWA Studio documentation. https://developer.adobe.com/commerce/pwa-studio/tutorials/production-deployment/adobe-commerce/
- Adobe, “GraphQL Application Server”, Adobe Commerce performance best practices. https://experienceleague.adobe.com/en/docs/commerce-operations/performance-best-practices/concepts/application-server
- Adobe, “Adobe Commerce as a Cloud Service overview”, updated September 11, 2026. https://experienceleague.adobe.com/en/docs/commerce/cloud-service/overview
- Adobe, “Adobe Commerce as a Cloud Service product description”, effective October 13, 2025. https://helpx.adobe.com/be_en/legal/product-descriptions/adobe-commerce-cloud-service.html
- Adobe, “Adobe Commerce Optimizer product description”, effective October 13, 2025. https://helpx.adobe.com/legal/product-descriptions/adobe-commerce-optimizer.html
- Adobe, “Adobe Commerce Optimizer limits and boundaries”. https://experienceleague.adobe.com/en/docs/commerce/optimizer/boundaries-limits
- Adobe, “Adobe Commerce lifecycle policy”, updated September 18, 2026. https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/lifecycle-policy
- Hyvä Themes, “It’s time: we’re making Hyvä Theme Open Source and Free”, November 6, 2025. https://www.hyva.io/blog/news/hyva-is-free-open-source.html
- Alokai, “A Framework-Agnostic Magento 2 Integration”, updated January 27, 2026. https://alokai.com/blog/a-framework-agnostic-magento-2-integration-next-step-in-ecommerce-frontend-development-
- Elogic Commerce, “Hyvä Performance Rescue: 109% Revenue Growth” (DIGI case study). https://elogic.co/projects/revamping-online-electronics-store-with-hyva-theme/
About the author
Paul Okhrem is the CEO and Founder of Elogic Commerce and a member of the Forbes Technology Council. Under his leadership, Elogic Commerce received the Magento Community Engineering Award at Magento Imagine 2019.
Get in Touch
Looking for a partner to grow your business? We are the right company to bring your webstore to success.