Skip to content

Expert Answers to Your Magento, Shopify & Shopware Questions

Vendor-neutral, engineer-written explanations. Clear definitions first, then practical steps with real examples — no fluff.

Stagebit builds and maintains stores on Magento, Adobe Commerce, Shopify, Shopware, and Laravel, and this library holds the questions our own engineers get asked most often on each platform.

What is Edge Delivery Services for Commerce and does it replace my current storefront?

SB
Written by Stagebit Engineering Team
Updated September 2026 4 min read Verified by engineers

Edge Delivery Services for Adobe Commerce is Adobe’s newer storefront. Pages come from Adobe’s edge network instead of your Magento server, and prebuilt JavaScript components called drop-ins handle the cart, checkout, and product pages. So yes, it replaces your theme. It doesn’t touch the backend your team works in every day.

Adobe’s documentation calls it Adobe Commerce Storefront, and developers often shorten it to EDS.

Quick answer

Edge Delivery Services replaces the frontend only. Your Admin, catalog, and order data stay on Adobe Commerce, and you can migrate one part of the funnel at a time. It needs an Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer license. Magento Open Source can’t use it.

How does Edge Delivery Services for Adobe Commerce work?

Edge Delivery Services changes who builds the page. In a Luma or Hyvä store, your Magento server assembles every page with PHP. With Edge Delivery, the edge network sends HTML and JavaScript, and drop-ins call Adobe Commerce APIs straight from the shopper’s browser. Adobe’s storefront architecture overview walks through the full stack.

  • Merchants edit pages in a document-style workflow, so a new landing page doesn’t need a developer.
  • Developers keep the storefront code in GitHub, starting from Adobe’s Commerce boilerplate.
  • Drop-ins read and write data through Adobe Commerce GraphQL, which keeps cart contents and prices current.
  • On catalog pages, Catalog Service and Live Search answer read-only queries from Adobe-hosted endpoints, so your server handles fewer requests.

Does Edge Delivery Services replace Luma or Hyvä?

Edge Delivery Services replaces the storefront theme, whichever one you run today. Luma, Hyvä, and custom PHP themes all stop rendering shopper pages once you switch. Commerce Admin and the PHP logic in your modules keep working.

The catch is the frontend half of your extensions. A payment widget or delivery-date picker lives inside your current theme, and that code won’t carry over.

 Edge Delivery ServicesHyväLuma
Who renders the pageAdobe’s edge network, with drop-ins calling Commerce APIs in the browserYour Magento server (PHP, Tailwind CSS, Alpine.js)Your Magento server (PHP, RequireJS, Knockout)
Runs on Magento Open SourceNoYesYes
LicenseCloud Service, Optimizer, or PaaS with OptimizerCore theme free and open source since November 2025; Hyvä Checkout and Enterprise are paidBundled with Magento

Can you migrate to Edge Delivery Services in phases?

Yes, Edge Delivery Services supports a phased move. Adobe’s storefront planning guide describes two routes. A full implementation rebuilds everything and retires the old storefront in one go. A progressive implementation moves selected parts of the funnel and leaves the rest on your current theme.

Luma stores get extra help here. Adobe’s Luma Bridge module shares the cart and sign-in session between Luma and the drop-ins, so a shopper who moves between old and new pages keeps the same cart. Adobe documents this bridge for Luma only.

What license and version do you need for Edge Delivery Services?

Edge Delivery Services only works with specific Adobe Commerce products. As of September 2026, Adobe’s storefront prerequisites set out these requirements:

  • License: Adobe Commerce as a Cloud Service, Adobe Commerce Optimizer, or Commerce PaaS with Optimizer added.
  • Version: Adobe Commerce 2.4.8 or later on PaaS, per Adobe’s backend options page. Magento Open Source isn’t supported.
  • PaaS setup: The Storefront Compatibility package, Services Connector, and Catalog Service go on first. Cloud Service includes them already.

Count your frontend extensions first

Before you budget anything, list every extension that shows something to shoppers. Payment, shipping, in-store pickup, and tax modules are the usual suspects. For each one, check whether the vendor offers frontend APIs or its own drop-ins. Custom product attributes need a look too, since Catalog Service may need exporter changes before drop-ins can display them.

Should you move to Edge Delivery Services?

On Magento Open Source, Edge Delivery Services isn’t an option yet. Hyvä is the closer fit there, since it runs on Open Source and the core theme is now free. On licensed Adobe Commerce, the deciding number is how many extensions render on the frontend, because each one turns into rebuild work. A short list makes a full move realistic. A long one usually points to a phased rollout. Our Magento development team can run that count against your store.

Was this answer helpful?

Your feedback helps us improve our answers.

Still need help?

Talk to our Adobe Commerce experts

Not sure how many of your extensions would need rebuilding for Edge Delivery? We can take a look.

Talk to Magento / Adobe Commerce Experts