A fast Adobe Commerce storefront marketing can update

Adobe Commerce Storefront on Edge Delivery Services serves pages from the edge and lets your team publish content like documents, while drop-in components handle cart, checkout and account.

Explore an EDS storefront What’s included

Free · No obligation · Reply within one business day

Built from Adobe’s storefront boilerplate
Drop-in components for commerce flows
Content authored without developers

Edge Delivery Services serving a storefront with commerce drop-in components

Stores we have built and run

By the Mistri engineering team · Updated 1 November 2026

Adobe Commerce Storefront on Edge Delivery Services is Adobe’s newer way to build storefronts: pages are served by Edge Delivery Services, content is authored in document tools, and drop-in components handle cart, checkout and account by calling Adobe Commerce APIs.

How an Edge Delivery storefront works

A simplified view of Adobe’s architecture.

AuthorContent written in document tools or Adobe’s editor.

Edge DeliveryPages served fast from the edge.

Drop-insCart, checkout and account components in the browser.

Adobe CommerceAPIs for products, cart and orders.

Why it matters

What Edge Delivery changes for marketing and sales

Served from the edgePages are delivered by Adobe’s Edge Delivery Services, close to shoppers.

Easy content authoringMarketing teams edit content in familiar document tools or Adobe’s editor.

Drop-in commercePre-built components for cart, checkout, account and product details.

How it fits together

Edge Delivery Services serves the HTML and JavaScript. Drop-in components run in the shopper’s browser and call Adobe Commerce APIs for cart, checkout and account.

Adobe Commerce stays the system of record
Content and commerce on one storefront
Components update as Adobe’s APIs evolve

How it works

What’s included

Storefront designBrand design on the Adobe boilerplate.

BlocksCustom blocks for campaigns and content.

Drop-insCart, checkout, account and product drop-ins configured.

Commerce APIsConnected to your Adobe Commerce back end.

Author trainingYour team learns to publish pages.

PerformanceLighthouse and field data checked at launch.

Is EDS right for you?

Your situation	Recommendation
New build, content-heavy brand	Edge Delivery storefront
Existing Luma store, limited budget	Breeze or Hyvä
Fully custom app experience	Headless with Next.js

Is this right for you?

A good fit if

You run or plan Adobe Commerce and want Adobe’s latest storefront
Marketing publishes a lot of content and campaigns
You want commerce and content on one storefront
You are planning a new build

Probably not the right fit if

Your licence does not include the storefront: check with Adobe first
You need a quick win on an existing Luma store

What you receive

Storefront design and blocks
Configured drop-in components
Author training and documentation
Launch and performance check

How it works

You see the findings, the scope and the price before any code changes.

AuditWe review code, extensions, hosting and speed.
Plan & priceA fixed scope and price, or a retainer.
Build on stagingTested on a copy of your store, never live.
Launch & supportA planned release, rollback ready, then monitoring.

For your technical team

How we build it

The stack, standards and handover your developers can expect.

Architecture

Adobe Commerce storefront boilerplate
Pages served by Edge Delivery Services
Adobe Commerce stays the system of record

Commerce

Drop-ins for cart, checkout and account
Adobe Commerce APIs called from the browser
Custom blocks for your design

Authoring & quality

Document-based authoring or Adobe’s editor
Core Web Vitals checked before launch
Author training and documentation

Related guides

In-depth articles from the Mistri blog.

Questions before you book

Frequently asked questions

Do I need Adobe Commerce, or does Magento Open Source work?

The Edge Delivery storefront and its drop-ins are part of Adobe’s commerce offering. Check your Adobe licence and edition for eligibility.

Can marketing edit pages without developers?

Yes. Content is authored in document tools or Adobe’s editor and published to the storefront; developers build the blocks once.

What happens to our existing extensions?

Extensions that change the Luma frontend do not apply to an Edge Delivery storefront. We list which features need a drop-in, a custom block or a backend API.

Who maintains the storefront code after launch?

Blocks and configuration live in a Git repository you own. Your developers, us on a retainer, or both can maintain them.