The pages that sell
Home, category, product, search, cart, checkout and account. B2B screens too if the shop is not for anonymous consumers.
Service
A headless storefront in Next.js
Headless means something concrete here: Medusa stays the commerce engine, Next.js renders the pages. You get a storefront with your own design and real URLs. You do not automatically get better product data or a smarter offer. That is still human work.
At a glance
- The pages that sell
- Server-side rendered
- Connected to Medusa
- Evolving without touching the backend
Custom quote after a free intro call
What we do
What is included
Server-side rendered
Pages arrive at the browser and the search engine with their content. We do not build a storefront that only exists after a client-side fetch.
Connected to Medusa
Prices, stock and cart run through the Medusa API. The storefront does not invent a second stock level.
Evolving without touching the backend
A campaign page or a new template can live in the storefront, as long as the commerce rules stay in Medusa.
Who it is for
Who this fits
- Teams with a Medusa backend that have outgrown the starter storefront.
- Brands where design and content matter as much as the checkout.
- Organisations with several brands or languages on one commerce engine.
- Companies that want to be able to follow the frontend in-house, in a stack many developers know.
Honest advice
When we advise against it
- A project where a Medusa starter theme already looks right and there is no frontend team or budget.
- The hope that 'headless' fixes a slow assortment or thin product copy.
Price
What determines the price
A custom quote after a free intro call. These factors determine the price, not a menu.
- Number of templates
- A product page is one template. Landing pages, brands, languages and account screens make up the rest of the count.
- Design
- A finished design you supply is different from a design that still has to be created in the project.
- B2B screens
- Login, custom prices, quick order and quotes are extra surfaces on top of a consumer checkout.
- Content source
- Copy from Medusa, from a CMS, or both. Two sources mean an agreement on which field wins.
Process
The process
- 01
What the storefront must do
We list the screens and every state: guest, logged in, B2B, empty, error.
- 02
Sketch on real data
A product page with real products as early as possible, not just a static composition.
- 03
Build
Next.js App Router, connected to Medusa. SEO basics (titles, canonicals, hreflang, sitemap) are included, not extra work afterwards.
- 04
Handover
The storefront is a repository you can host and develop further. We document how to add a new template.
Insights
Further reading
From this service to the articles, and from each article back again.
- ArticleWhat a headless Next.js storefront does and does not solveMedusa stays the engine, Next.js becomes the shop window. When that difference matters, and when a theme is simply enough.Read more
- ArticleShopify vs Medusa: costs, flexibility and when to choose whichShopify and Medusa compared on subscription, revenue fees, apps, hosting, three-year cost and B2B. Prices as of 5 November 2026, and honest about where Shopify wins.Read more
- ArticleWooCommerce vs Medusa: when WordPress holds the shop backWooCommerce and Medusa compared on extensions, hosting, three-year cost, B2B and multiple shops. With real extension prices and our Shingyo project.Read more
- All articlesPlatform comparisons and the migration guide, with sources.To the articles
Why Next.js and not the standard Medusa theme?
The standard theme is a good starting point to learn Medusa. A custom Next.js storefront makes sense when the design, the SEO or the B2B screens are yours and not the starter project's. If the theme is enough, we tell you.
Is a headless shop worse for SEO?
Only if the page arrives empty and JavaScript fills it in later. We render the important pages on the server, with a real URL and metadata. Then headless is no disadvantage.
Can we supply the design ourselves?
Yes. We prefer finished screens for product, listing, cart and account over a homepage alone. Missing states (empty, error, long product name) we discuss; every shop has them.
Who hosts the storefront?
You do. New projects run on Medusa Cloud in Frankfurt by default, in an account in your name. We set the project up so it is not tied to our account, and so you can also host it yourself with any provider that runs Next.js.
Can you do only the frontend?
Yes, if the Medusa backend already exists and the API provides the data the screens need. If a price rule or a field is missing, that is backend work, not storefront work. We flag it straight away.
Free intro call
What is your challenge?
Twelve shops that need to become one, an ERP that sets the price, or a checkout that does not do what you want. Tell us in one call. You will hear honestly whether Medusa fits.
Based in Nijmegen, the Netherlands, working with companies across Europe. How we work with European teams.