Your Magento (Adobe Commerce) store moved to Hyvä, a lighter storefront theme, and Google’s free PageSpeed Insights test turned green on the first run. Then the complaints kept coming: the store still feels slow after Hyvä, and the real-visitor data in that same report has barely moved. So which part of the store didn’t get faster?

When a Magento store is still slow after Hyvä, whoever signed off the migration budget has an awkward question to answer: was the money well spent, and what should the next project be? Before anyone books another frontend sprint, it pays to find out where the wait happens.

Why is a Magento store still slow after Hyvä?

A Magento store stays slow after Hyvä when the time is lost before the browser gets the page, or on pages Hyvä doesn’t render. Every page load has two steps: the server builds the page, then the browser draws it. Hyvä makes the second step lighter and leaves the first, server response time, where it was.

What Hyvä changes in the page load

Hyvä changes what the browser loads after the page arrives. Its pages load Tailwind CSS and Alpine.js, while pages on Luma, Magento’s default theme, load RequireJS, Knockout, and jQuery, the older JavaScript libraries Luma is built on. Our study of 12 eCommerce platforms analyzed September 2026 data from the Chrome UX Report, Google’s record of real Chrome visits. In it, the median Magento store on Hyvä loaded 767 KB of JavaScript on mobile, against 1,270 KB for Magento overall.

That shows in Core Web Vitals, Google’s three page-experience measures: how soon the main content appears (LCP, within 2.5 seconds), how fast the page reacts to a tap (INP, 200 milliseconds or less), and how much the layout jumps (CLS, 0.1 or less), each judged at the 75th percentile of visits. A page passes when all three are good. In that data, 66.4% of Magento stores on Hyvä passed all three on mobile, against 44.6% for Magento overall. Good LCP was 77.2% against 58.1%, good INP 90.2% against 84.4%, and good CLS 89.5% against 70.9%. That is the Hyvä performance gain.

What Hyvä leaves as it was

Before the browser receives anything, Magento’s server builds the page: it runs the layout XML, renders each block through its PHP template, and queries the database for products, prices, and stock. Hyvä is still a Magento theme made of layout XML and PHP templates, so that work happens the same way under Hyvä.

The wait this produces is time to first byte (TTFB), how long the server takes to start sending the page. Google’s TTFB guidance calls 0.8 seconds or less good and more than 1.8 seconds poor. It is measured before any script runs, so the amount of JavaScript a theme carries has no effect on it.

The September 2026 data shows this. 23.2% of Magento stores on Hyvä had a good mobile time to first byte, against 23.0% for Magento overall. At the 75th percentile, the median Hyvä store took 1,100–1,199 ms to send the first byte, against 1,200–1,299 ms for Magento overall, and both are above the 0.8-second line. A lighter theme can’t make the first byte arrive sooner.

Why a green PageSpeed score can sit next to a slow store

A green PageSpeed Insights score comes from one simulated visit to one page, so it can look perfect while real shoppers wait. Google’s documentation says good lab data “does not necessarily mean real-user experiences will also be good.” The field data in the same report, from real Chrome visits over 28 days, shows what shoppers actually get.

Lab data vs field data on a Hyvä store

We get this question after many Hyvä launches, and the answer starts with what the score measures. The PageSpeed Insights score is lab data: Lighthouse, the tool behind it, loads one page once on a simulated Moto G4 phone. That page is often the homepage, which the full page cache (Magento’s store of finished pages) usually already holds, so the server step looks quick. The PageSpeed Insights documentation says lab data is collected in a controlled environment and may not capture real-world bottlenecks.

Field data comes from real Chrome users over the previous 28 days, reported at the 75th percentile, on their own devices and networks. Google’s note on why lab and field data can disagree puts it plainly: lab data can say a site performs great while field data says it needs work.

The lab gain from Hyvä is real: the median Hyvä store scores 48 in Lighthouse against 35 for Magento overall. Shoppers, though, feel the field numbers, on every page they open. Magento Core Web Vitals are judged on that field data, so test a filtered category page, a search result, and the checkout as well as the homepage. Our guide on how to read PageSpeed Insights goes further.

What “Server responded slowly” means after a Hyvä launch

“Server responded slowly” is a line in the Document request latency insight in PageSpeed Insights, and it appears when the main HTML document takes more than 600 ms to arrive from the server. The insight measures the server step alone, so a Hyvä launch can’t clear it. Lighthouse 13 folded the older initial-server-response-time audit into this insight, so the warning may carry a different label than in your last report.

The fix is on the server: serve more pages from the full page cache, and make the pages it misses faster to build. The section on fixing slow server response below covers both, and our guide on how to reduce initial server response time walks through the measurements step by step.

How to tell whether the server or the browser is slow

Split the wait into its two steps first. Read the field data for time to first byte and Core Web Vitals, time the server on a cached page and on one the cache misses, and check which pages still load Luma. Poor server time points to the server. Good server time with a slow page points to the browser.

1. Read the field data in PageSpeed Insights for one key URL and for the origin. In the field section, note time to first byte, LCP, INP, and CLS at the 75th percentile, both for the page you tested and for the origin, meaning every page Chrome users opened on your domain, since one URL can look fine while the store as a whole doesn’t.
2. Compare TTFB with LCP. LCP’s budget is 2.5 seconds, so if the first byte uses most of it, the server is the step to fix first, and browser-side work alone won’t bring LCP under the line.
3. Time the server on a cached page, then on one the cache misses. Run curl or open the Network panel in DevTools on a category page and note the time to first byte, then add a throwaway query parameter to the URL so the full page cache can’t answer and the server has to build the page, as our guide to audit Magento performance shows. The gap between the two is the build time the cache hides.
4. Check which pages still load Luma. Open the page source of the checkout, the customer account pages, and any page an extension adds, and search for RequireJS, or read the list of routes under HYVA THEMES > Fallback theme > General Settings in the admin, where Hyvä’s Luma theme fallback hands chosen routes to a Luma-based theme. Anything on that list runs on Luma’s code, whatever the rest of the store uses.
5. List the third-party tags on the slowest page and when each was added. Compare the list with the launch date: a tag added after launch loads on top of Hyvä’s lighter baseline and is a browser-side suspect on every page it runs on.

If none of the five explains why your Magento store is still slow after Hyvä, the cause is somewhere else in the stack, and our guide on why a Magento site is slow covers the rest.

How to fix slow server response on a Hyvä store

Fix the server step in two ways: serve more pages from the full page cache, and make the pages the cache misses faster to build. A theme can’t help with either, because both happen before the browser receives anything. Then profile the pages that are still slow, since one extension or integration call can add time to every uncached page.

Serve more pages from the full page cache

The full page cache returns a finished page on the next request without rebuilding it, and Hyvä pages are cached like any other Magento page. Coverage is the issue. Catalog pages for logged-in customers are cached separately for each customer group, and search results for each search term, so those requests miss more often, and one block marked cacheable="false" in the layout makes the whole page uncacheable.

Most Magento 2 Hyvä performance tuning on the server starts with the hit rate, so check it before anything else. Our guides on the Magento full page cache, Varnish configuration (Varnish is the caching server that holds those pages in front of Magento), and running a cache warmer cover how to raise it.

Make the page build faster with Expedio Theme

Caching only skips the build for pages it has already stored. For every other request, the build itself has to get faster, and that is server-side work a storefront theme can’t do.

Expedio Theme is #2 in our ranking of the best Magento themes, the one pick that works under Hyvä instead of replacing it. Expedio Theme speeds up how Magento builds each page on the server. It works under Hyvä, Luma, or a custom theme, and it doesn’t change your theme, design, or data. As the Expedio page puts it, “Hyvä is the frontend, Expedio is the backend, and a store can run both.”

Expedio Theme makes Magento at least 2x faster, and the same server handles 3x more traffic before response times start to rise. Those results come from scandiweb’s benchmark on one merchant’s Hyvä store, with about 1,000 categories and 20,000 products, measured as server response time rather than full page load. With all caches empty, a category page took a median of 57 ms to build instead of 181 ms. Cart and checkout aren’t part of the comparison. It doesn’t change the browser side, which stays Hyvä’s job.

Profile the pages that are still slow

A profiler is a tool that records where the time goes while Magento builds a page: layout, blocks, templates, and database queries. Run it on the pages that stay slow after the cache and build work, because one extension or integration that calls another system while the page builds adds that wait to every uncached request. Bigger hosting helps only when CPU or memory is at its limit, so profile before you buy more of either. Our guide shows how to profile an uncached page step by step.

Which Hyvä pages still load Luma, and how to fix them

Pages on Hyvä’s Luma theme fallback load Luma’s RequireJS, Knockout and jQuery instead of Hyvä’s Tailwind CSS and Alpine.js, so they keep Luma’s weight on a Hyvä store. The usual ones are a Luma-based checkout and pages from extensions without a Hyvä compatibility module. Third-party scripts added after launch slow the browser step on every page.

The checkout on the Luma fallback

A Luma-based checkout, Magento’s default one included, runs on a Hyvä store through Hyvä’s Luma fallback module. On those pages the browser loads Luma’s CSS and JavaScript, RequireJS, Knockout, and jQuery, instead of Hyvä’s Tailwind CSS and Alpine.js, so a shopper who browsed a light storefront lands on a heavier page at the moment they pay.

Hyvä’s own documentation on running a Luma checkout recommends its paid Hyvä Checkout as the option with the best performance, built for Hyvä stores and free of the Luma frontend stack, and it notes that a Luma-based checkout needs extra styling work to match the Hyvä storefront. If step 4 above found RequireJS in your checkout, moving the checkout onto Hyvä Checkout is the fix for that page.

Extensions without a Hyvä compatibility module

Hyvä’s documentation on compatibility modules says modules built for Magento’s Luma or Blank themes need a compatibility module, a small add-on that re-implements the parts of the extension that don’t work out of the box on a Hyvä storefront. Without one, the extension’s storefront features may not work on a Hyvä page.

Check which Hyvä-compatible modules already exist in the Compatibility Module Tracker or ask the extension’s vendor. The other options are a custom module, or sending that extension’s pages to the Luma fallback as a stopgap. Treat the fallback as temporary, because every page on it keeps Luma’s weight, a point our guide on how to work with Hyvä makes as well. The Hyvä Theme core has been free and open source since version 1.4.0 on November 10, 2025, and compatibility modules come with the free license key.

As a Hyvä Platinum Partner, scandiweb’s Hyvä theme development team checks extension compatibility before launch, so you know in advance which pages, if any, need the fallback.

Third-party scripts added after launch

Hyvä starts from a lighter JavaScript baseline, 767 KB on the median mobile page against 1,270 KB for Magento overall, and every tag added afterward loads on top of it: the chat widget, the review widget, the heatmap, the A/B test script, the second analytics tag. A theme change removes none of them. Google’s guidance on third-party JavaScript notes that it is “usually outside your control” and recommends a performance budget and a regular audit.

Set that budget, load tags after the main content, and remove the ones nobody has looked at in a quarter. If images are the other weight on the page, our list of speed optimization extensions covers compression and lazy loading.

Frequently asked questions about Magento speed after Hyvä

Hyvä speeds up the browser step and leaves server response time where it was, a lab score can be green while field data isn’t, and pages on the Luma fallback keep Luma’s code. The answers below cover the questions merchants ask most after a Hyvä launch.

Does Hyvä improve server response time (TTFB)?

Not in the field data. In scandiweb’s analysis of Chrome UX Report data for September 2026, 23.2% of Magento stores on Hyvä had a good mobile time to first byte (800 ms or less), almost the same as 23.0% for Magento overall. Hyvä changes what the browser loads after the first byte arrives. The time the server takes to build the page needs server-side work.

Why does my PageSpeed score look high when my Hyvä store still feels slow?

The score is lab data: Lighthouse loads one page once, on a simulated mid-range phone, often a page the cache already holds. Shoppers load many pages on their own devices and networks, including pages the cache misses. Google’s PageSpeed Insights documentation says good lab data doesn’t necessarily mean real users get a good experience, so read the field data in the same report.

Does Hyvä make the Magento checkout faster?

Only if the checkout runs on Hyvä. A Luma-based checkout, including Magento’s default one, works on a Hyvä store through Hyvä’s theme fallback, and on those pages the browser loads Luma’s CSS and JavaScript (RequireJS, Knockout and jQuery) instead of Hyvä’s. Hyvä’s own documentation says its paid Hyvä Checkout “delivers the best performance, compatibility, and user experience.”

What happens to an extension without a Hyvä compatibility module?

Hyvä’s documentation says modules built for the Luma or Blank theme “require a Compatibility Module to work with Hyvä”, which re-implements the parts that don’t work out of the box. Until one exists, the options are a ready module from Hyvä’s Compatibility Module Tracker or the vendor, a custom one, or sending that extension’s pages to the Luma fallback, where they load Luma’s heavier code.

How long does field data take to show the effect of a Hyvä launch?

Up to four weeks. PageSpeed Insights reports real Chrome users’ experiences “over the previous 28-day collection period”, so in the first weeks after launch the field data still mixes visits to the old storefront with visits to the new one. Compare field numbers from before the launch with numbers from at least 28 days after it, and use lab tests in the meantime.

Can a Magento store run Hyvä and Expedio Theme together?

Yes. Hyvä speeds up what the browser does, and Expedio Theme speeds up how Magento builds each page on the server, under Hyvä, Luma or a custom theme, without changing the design or data. The two work on different steps of the same page load, so one doesn’t replace the other. The benchmark behind its claims ran on a Hyvä store.

Fixing a Magento store that is still slow after Hyvä

A Magento store that is still slow after Hyvä usually has a server step that never got faster, a few pages still on Luma, or scripts added since launch. Measure with field data first, then fix the step that is losing the time.

If field time to first byte is poor, start with the server: cache coverage, the page build, and profiling. If the server responds quickly and a page is still slow, look for the Luma fallback and the tag list. If only the lab score has moved, wait for 28 days of field data before judging the launch. The Hyvä performance gain was real and stayed in the browser step, and the server step needs a project of its own. For the full list of fixes from the server to the browser, see our guide on how to speed up Magento.

scandiweb is a Hyvä Platinum Partner with 894+ Adobe certifications and 23+ years in eCommerce, and we measure both steps before we recommend either project.

If your Hyvä store scores well in the lab and still feels slow to shoppers, ask our Hyvä and Magento team to look at which step is losing the time.

The post Why Your Magento Store Is Still Slow After Hyvä appeared first on scandiweb.

Teams on Magento Open Source, the free edition of Magento, and on Adobe Commerce running on their own servers read every Adobe AI announcement with the same question: will this work on our store? Adobe Commerce AI features have arrived quickly since Adobe Summit, Adobe’s yearly conference, in April 2026, and the announcements say much more about what each feature does than about which edition or license it needs.

Each feature below was checked on Adobe’s own pages on November 2, 2026, in Experience League (Adobe’s documentation site) and on Adobe’s blog. Where Adobe names an edition or a price, we quote it. Where Adobe doesn’t say, we say that too, instead of guessing.

Adobe Commerce AI features at a glance

Adobe Commerce AI features fall into four groups: AI search and recommendations that come with the license, features in beta, AI that runs on other Adobe products, and agents and tools for developers. Adobe’s setup guide says Live Search and Product Recommendations require Adobe Commerce and aren’t available for Magento Open Source.

Adobe now sells Adobe Commerce on-premises, on Adobe Commerce on Cloud (Adobe-managed PaaS hosting), as Adobe Commerce as a Cloud Service (a SaaS platform), and as Adobe Commerce Optimizer, a SaaS layer that runs in front of an existing backend. We compared the four Adobe Commerce editions in a separate post, so this one stays on the AI features.

Statuses, editions and costs are quoted from Adobe’s documentation and blog as of November 2, 2026. “Adobe doesn’t say” means no Adobe page we read states it.

AI search and recommendations included with Adobe Commerce

Two Adobe AI features come with an Adobe Commerce license: Live Search, which Adobe describes as AI-powered faceting and re-ranking of search results and says is included in your license, and Product Recommendations, built on Adobe AI and machine learning. Both run as Adobe services connected to Adobe Commerce 2.4.4 or later.

Live Search and semantic search

Live Search replaces the standard catalog search in Adobe Commerce and runs as a SaaS service. Adobe’s install guide lists Adobe Commerce on Cloud and Adobe Commerce on-premises from version 2.4.4, and Adobe Commerce as a Cloud Service uses the same Live Search.

Semantic search, a newer part of Live Search, matches the meaning of a search, so “warm jacket for hiking” finds insulated outdoor coats even when the product copy uses none of those words. Adobe made it generally available on June 8, 2026. Adobe’s semantic search documentation says it works on English catalogs only, is on by default on Cloud Service, and has to be enabled manually on Adobe Commerce on Cloud and on-premises.

Many teams search for “Magento Live Search,” and Adobe’s setup guide says Live Search requires Adobe Commerce, so a Magento Open Source store can’t use it. On a Hyvä storefront, Hyvä’s own Live Search module comes with a Hyvä Enterprise license.

Product Recommendations

Adobe Commerce Product Recommendations are storefront widgets such as “frequently bought together,” powered by Adobe AI and machine learning trained on shopper behavior and catalog data. Adobe’s current pages say Adobe AI where older ones said Adobe Sensei. They are part of Adobe’s Commerce SaaS services, and Adobe’s tutorial page labels them an exclusive feature only in Adobe Commerce. Adobe’s pages say you need the correct entitlements but don’t give a price.

AI features in beta or on other Adobe products

Several Adobe Commerce AI features are still in beta or run on a separate Adobe product. Catalog enrichment rewrites product names and descriptions for AI assistants and is in beta. The Merchant Productivity AI Assistant adds chat to the Admin as a public beta. Brand Concierge and Adobe Brand Visibility are Adobe products in their own right.

Catalog enrichment with the Catalog Agent

Adobe’s generative AI features for Commerce start with catalog copy. The Catalog Agent finds gaps in product names and long descriptions and proposes improvements, so that AI assistants such as ChatGPT describe the product accurately. Approved changes go back into the catalog and can be rolled back at any time.

Adobe’s catalog enrichment documentation applies to Adobe Commerce on Cloud and on-premises projects only. The feature is in beta, so you ask your Adobe account manager for access. Setup needs an Admin user who signs in through Adobe IMS with access to the Adobe Admin Console, and it checks that your company has signed the GenAI rider, Adobe’s contract terms for its AI services. Adobe doesn’t say what it costs.

Merchant Productivity AI Assistant in the Admin

The Merchant Productivity AI Assistant is a chat panel inside the Adobe Commerce Admin. In Adobe’s description it can manage promotions and update product catalog information, and it can pull operational data such as the last ten orders or current inventory status. It is a public beta, open to Adobe Commerce customers and partners, and Adobe’s beta releases page explains how to join. That page names no supported hosting setups, and it gives no release date or price.

Brand Concierge for shopping chat

Adobe Brand Concierge is an AI chat for brand websites, and at Adobe Summit in April 2026 Adobe introduced an Adobe Commerce integration for it. Shoppers in the chat see live catalog data with current prices and stock, and Adobe marks checkout inside the conversation as coming soon. Brand Concierge is a separate Adobe product built on Adobe Experience Platform, and its setup guide asks for an Experience Platform sandbox and a datastream. Adobe doesn’t say which Adobe Commerce editions the integration supports or what it costs.

Adobe Brand Visibility, formerly LLM Optimizer

Adobe Brand Visibility, sold as Adobe LLM Optimizer before the rename, tracks how AI answers present your brand and helps your team put fixes in place. It also powers catalog enrichment in Adobe Commerce behind the scenes. It is a separate Adobe product with no price on Adobe’s product page. For what this kind of monitoring measures, see our guide to tracking brand mentions in AI answers.

Adobe Commerce AI agents for developers

Adobe’s AI agent for developers is the Commerce Developer Agent, generally available since September 25, 2026. It turns a written requirement into a plan developers approve, then generates App Builder app code. Adobe says it is available to Adobe Commerce customers only and needs App Builder access. Developer MCP servers bring Adobe Commerce documentation into developers’ own AI coding tools.

Commerce Developer Agent

The Commerce Developer Agent writes App Builder apps from a plain description. App Builder is Adobe’s platform for apps that extend Adobe Commerce from outside the core code. A developer describes the requirement, the agent writes a blueprint, the developer edits and approves it, and the agent then scaffolds the project, generates the code, and validates the build. Adobe’s example is a cart-limit rule built as a webhook, with the limits exposed as settings in the Commerce Admin.

Adobe’s getting started page lists an Adobe Commerce entitlement, App Builder access, and an Adobe IMS identity as prerequisites, and says the agent is available to Adobe Commerce customers only. The allocated capacity is provided at no additional charge currently, with pricing to follow at a later date. Adobe’s pages name Adobe Commerce as a Cloud Service projects and existing implementations of Adobe Commerce on Cloud, and don’t mention on-premises. Generated code still needs a developer’s review before production use.

Developer MCP servers and agent skills

MCP, the Model Context Protocol, is a standard way for AI tools to connect to other systems. Adobe’s developer MCP servers bring Adobe Commerce documentation, sample code, tutorials, and project rules into coding tools such as Cursor or Claude Code. The set is a Commerce Developer MCP Server, an App Builder MCP Server, and a pack of agent skills, installed and updated with one command, aio commerce extensibility tools-setup. Adobe writes them for developers on Adobe Commerce as a Cloud Service and related Adobe SaaS products, and its pages don’t state a price.

Adobe Commerce agentic AI still on the roadmap

The main Adobe Commerce AI feature still on the roadmap is the Commerce MCP server, which would let developers build shopping agents on live catalog and checkout data. Adobe’s documentation labels it Coming Soon. Checkout inside Brand Concierge chats is also marked as coming soon, and Adobe has committed to the UCP and ACP agentic commerce standards.

At Adobe Summit in April 2026, Adobe introduced a Commerce MCP server that gives developers real-time access to catalog, cart, pricing, inventory, promotions, checkout, and order data, so they can build shopping assistants and upsell agents. The Commerce MCP overview in Experience League carries a Coming Soon badge as of its October 8, 2026 update, and Adobe doesn’t say which editions the Adobe Commerce MCP server will support, or at what price. Adobe’s AI commerce page describes an Adobe Commerce Storefront MCP server for the same jobs (catalog search, prices, cart, and checkout) with no status label, and Adobe doesn’t say whether the two names describe one product.

Adobe has also committed to supporting the Universal Commerce Protocol (UCP) from Google and the Agentic Commerce Protocol (ACP) from OpenAI, standards that let AI assistants such as ChatGPT or Gemini find and buy products for a shopper. Adobe’s architecture guidance, updated October 21, 2026, describes a commitment with no released feature and no edition named. Our explainer on agentic commerce covers what these protocols change for a store.

Which Adobe AI features work on Magento Open Source and on-premise Adobe Commerce

Magento Open Source can’t use Adobe’s commerce AI services: Adobe says Live Search, Product Recommendations and Catalog Service require Adobe Commerce, and the Developer Agent is for Adobe Commerce customers only. Adobe Commerce on-premises can use Live Search and Product Recommendations on version 2.4.4 or later, and catalog enrichment applies to on-premises and Cloud projects.

Magento Open Source

Adobe’s guide to setting up Commerce services says Catalog Service, Live Search, and Product Recommendations require Adobe Commerce and are not available for Magento Open Source. The Developer Agent is for Adobe Commerce customers only, and catalog enrichment applies to Adobe Commerce on Cloud and on-premises projects. For Brand Concierge, the Commerce MCP server, and the UCP and ACP work, Adobe doesn’t say which editions they will support. For everything else that differs between the editions, see Adobe Commerce vs Magento Open Source, and if a move down is on the table, our post covers what a store loses when it moves to Magento Open Source.

Adobe Commerce on-premises

Live Search and Product Recommendations support on-premises stores from version 2.4.4, and semantic search is available once someone switches it on, for English catalogs only. Catalog enrichment applies to on-premises projects as a beta.

The Developer Agent is the open question. Adobe’s pages name Adobe Commerce on Cloud and Cloud Service projects and don’t mention on-premises, and Adobe’s on-premise product description, effective July 31, 2023, lists App Builder as an add-on licensed per pack per year. If your store runs a version older than 2.4.4, the first step is an upgrade, and our guide on how to upgrade Magento covers that path.

How to check which Adobe AI features your store can use

1. Find your edition. Search composer.lock for magento/product-enterprise-edition, the Adobe Commerce package. magento/product-community-edition means Magento Open Source.
2. Check your version. Run bin/magento --version, as Adobe’s check version guide describes. Adobe Commerce Services support 2.4.4 and later.
3. Know where you’re hosted. Semantic search is on by default only on Adobe Commerce as a Cloud Service, and catalog enrichment applies to Cloud and on-premises.
4. Check your catalog language. Semantic search works on English catalogs only.
5. Ask Adobe about betas and terms. Catalog enrichment is a beta through your account manager and needs the GenAI rider. The Admin AI Assistant is a public beta, and the Developer Agent needs an Adobe Commerce entitlement and App Builder access.

AI options for Magento Open Source stores

Magento Open Source stores get AI from third parties. AI search services replace the default catalog search, extensions add AI content writing and shopper chat, MCP connectors let your own AI assistant work with store data, and AI agents take on store changes. Most support both editions, so the choice depends on the job you need done.

Third-party search services replace the default catalog search on either edition: Algolia’s Magento 2 extension, in its own description, does so on Magento Open Source and Adobe Commerce.

Extensions for product copy generation or shopper chat install like any other Magento extension, and they usually bill the AI use to your own API key.

MCP connectors work with an assistant you already use. scandiweb’s open-source Magento MCP server lets an assistant such as Claude or ChatGPT edit catalog and CMS content within Magento’s admin roles, on Magento 2.4.4 and later. You give the instructions, and the assistant carries each one out.

Ari, the AI agent for Magento, is one agent of this kind, and it works on Magento Open Source and Adobe Commerce. A store team asks for a change in chat, Ari builds it on a copy of the store with customer data removed, and the team checks it on a preview store before a person approves and releases it as a pull request. Plans start at €99 a month per store.

Frequently asked questions about Adobe Commerce AI features

Does Magento Open Source have AI features?

No Adobe AI service runs on Magento Open Source. Adobe’s setup guide says Catalog Service, Live Search and Product Recommendations require Adobe Commerce, and the Commerce Developer Agent is available to Adobe Commerce customers only. Open Source stores add AI through extensions, third-party search services, MCP connectors and AI agents that work on both editions.

Is Live Search included in the Adobe Commerce license?

Yes. Adobe describes Live Search as a SaaS service that is included in your license, for Adobe Commerce 2.4.4 and later on Cloud and on-premises, and Adobe Commerce as a Cloud Service uses the same Live Search. Adobe says semantic search, which matches the meaning of a query, comes at no additional cost as part of Live Search.

Can on-premise Adobe Commerce use Adobe’s AI features?

Partly. Live Search and Product Recommendations support Adobe Commerce on-premises from version 2.4.4, and catalog enrichment applies to on-premises and Cloud projects. Semantic search has to be switched on manually. For the Developer Agent, Adobe doesn’t name on-premises, and Adobe’s on-premise product description lists App Builder, which the agent needs, as an add-on.

What is the Adobe Commerce Developer Agent?

The Commerce Developer Agent is Adobe’s AI agent for developers, generally available since September 25, 2026. A developer describes a requirement, approves the plan the agent writes, and the agent generates and validates App Builder app code. Adobe says generated code must be reviewed before production use, and the agent is for Adobe Commerce customers only.

Is there an MCP server for Adobe Commerce?

Adobe has two kinds. Developer MCP servers, available now, bring Adobe Commerce documentation and App Builder tasks into AI coding tools such as Cursor or Claude Code. The Commerce MCP server for building shopping agents on live store data is marked Coming Soon in Adobe’s documentation. Open-source MCP modules also exist for Magento 2 stores.

Does Adobe Commerce have an AI assistant like Shopify Sidekick?

Adobe’s closest match is the Merchant Productivity AI Assistant, a chat panel in the Adobe Commerce Admin that can manage promotions, update catalog information and pull store data such as recent orders. It is a public beta, and Adobe’s beta page gives no release date or price. For Shopify’s built-in assistant, see our guide to Shopify Sidekick.

How to plan around Adobe’s AI for your edition

Adobe Commerce AI features depend on your edition first and the feature second. Check which edition and version you run, match it against what Adobe’s documentation says, and treat anything marked beta or Coming Soon as a plan until Adobe makes it generally available. Then fill the gaps with third-party tools that run on your edition.

Several statuses in the table can change any week, so re-read Adobe’s pages before you tie a budget, a renewal, or an edition decision to one of them. If an edition change is on the table partly because of Adobe’s AI, scandiweb’s AI strategy consulting for eCommerce can map which of these features your store would use first and what the alternatives on your current edition cost.

If you want a second pair of eyes on this for your own store, send us your edition and version and we will check it against Adobe's documentation.

The post Adobe Commerce AI Features by Edition: What’s Included and What Open Source Can Use appeared first on scandiweb.

In February 2016, a store owner asked on Magento Stack Exchange how to stop showing the paid flat rate to shoppers who already qualified for free shipping, because seeing both “may confuse some customers.” The question has been viewed more than 15,000 times since, and its eight answers still don’t agree on a fix. That small checkout problem is part of a bigger job: Magento 2 shipping rules, the settings that decide which delivery options a shopper sees and what each one costs by weight, destination or cart value. So which of those rules can your team set up in the Magento (Adobe Commerce) admin, and which need something added to the store?

Every admin setting below was checked against Adobe’s documentation, and every extension price was read on the vendor’s own page on November 3, 2026.

What Magento 2 shipping rules can do without an extension

Without an extension, Magento 2 gives you four delivery methods that need no carrier account: Free Shipping, Flat Rate, Table Rates and In-Store Delivery. Built-in integrations add live UPS, USPS, FedEx and DHL rates. Every method can be limited to specific countries, and table rates set prices by weight, order subtotal or item count for each destination.

These are the Magento shipping methods you get on both Magento Open Source and Adobe Commerce, with the same settings on each.

Every method also has Ship to Applicable Countries (All Allowed Countries or Specific Countries), Show Method if Not Applicable, and Sort Order, so the Magento 2 shipping methods list at checkout is yours to trim and order.

Set the shipping origin first, under Stores > Configuration > Sales > Shipping Settings > Origin. Rates are calculated from that address, and it also sets the tax rate for the products you sell.

Live rates from UPS, USPS, FedEx and DHL

With a commercial account at the carrier, Magento downloads live rates from the four built-in carriers at checkout, and UPS and FedEx cover more than 220 countries. Check which USPS integration your store runs. USPS retired its Legacy Web Tools APIs on January 25, 2026, and Adobe Commerce 2.4.6, 2.4.7, and 2.4.8 use those APIs out of the box, so USPS requests fail until you upgrade to the latest version or apply the USPS REST API Migration quality patch. Ignore older guides that use Magento Shipping, since Adobe removed it in 2.4.0. For aggregators, label printing and 3PLs, see our guide to connecting a carrier or 3PL.

How to set up flat rate shipping in Magento 2

Flat rate charges one fixed shipping price, per order or per item. You set it under Stores > Configuration > Sales > Delivery Methods > Flat Rate: choose the Type, enter the Price, add an optional fixed or percentage handling fee and pick the countries it covers. Per Item multiplies the price by every item in the cart.

Per Order charges the Price once per cart. Per Item charges it for every item, so a $5 Per Item rate on a 3-item cart comes to $15.

Type None shows the method at a rate of zero. The default method name is “Fixed,” so rename it to something like “Standard.”

One Flat Rate section with one Price field means a second flat price, such as express, needs table rates or an extension.

How to set up Magento 2 table rates

Magento 2 table rates price shipping from a spreadsheet you import. Each row pairs a destination (country, region and ZIP code) with a weight, an order subtotal or an item count, and a price. You choose one condition for the whole table, export the CSV at website scope, fill it in and import it back.

Magento shipping table rates handle “it costs more to send there.” Adobe’s own example is a Los Angeles warehouse that pays less to ship to San Diego than to Vermont.

1. Go to Stores > Configuration > Sales > Delivery Methods > Table Rates. Set Enabled to Yes, add a Title (the default is “Best Way”) and a Method Name, pick the Condition, add an optional handling fee, and set Ship to Applicable Countries.
2. Switch the scope selector in the top left to your website, otherwise the Export and Import fields don’t show. Click Export CSV.
3. Fill in the file with three-letter country codes (USA, AUS), * for “all,” one ZIP code per row (no ranges), and weights with up to four decimal places. Put specific regions above the wildcard rows.
4. Import the file at the same website scope and click Save Config.
5. Test checkout with several addresses, including one that should land on the wildcard row.

Keep the header row from your own export. The rows below follow the column order of Adobe’s Example 2, a Weight v. Destination table for Australia.

Adobe’s table rate guide lists every setting, including how virtual products count.

Where native table rates stop

Native table rates give you one active table, one condition, no ZIP code ranges, and no dimensional weight. A rule that needs weight and subtotal together, two table-based methods, rates per customer group, or Magento 2 dimensional weight shipping is extension territory, covered below. One native trick still works for regions. Adobe’s Example 3 uses Price v. Destination with the method named Free Shipping, Ship to Specific Countries set to the United States, and Show Method if Not Applicable set to No, so free shipping applies to the continental US only.

How to offer free shipping over a set amount

Magento 2 offers free shipping in three ways: the Free Shipping method with a Minimum Order Amount, a cart price rule that gives free shipping when conditions such as subtotal, weight or destination are met, and a carrier’s free method, such as UPS Ground over a threshold. When the method setting and a cart rule both apply, the setting wins.

With the Free Shipping method

Go to Stores > Configuration > Sales > Delivery Methods > Free Shipping. Set Enabled to Yes and enter the Minimum Order Amount. Include Tax to Amount decides what that minimum is compared with: Yes means Subtotal + Tax – Discount, No means Subtotal – Discount. Set Ship to Applicable Countries, then set Show Method if Not Applicable to No so the method appears only when the cart qualifies.

With a $50 minimum, a $55 cart and a $10 coupon, Magento free shipping compares $45 with $50, and the shopper pays for delivery.

With a cart price rule

Use a rule when free shipping depends on more than a cart total. Conditions can use Subtotal, Total Items Quantity, Total Weight, the Shipping Postcode, Region, State or Country, the Shipping Method, and the Payment Method. In the actions, set Free Shipping to “For matching items only” or “For shipment with matching items,” which needs the Free Shipping method enabled.

If the method’s own Minimum Order Amount and a rule both apply, the method setting wins, so Adobe’s tip for running rules next to table rates is to set that minimum so high it is never met. Test holiday rules before the Black Friday code freeze.

With a carrier’s free method

In the UPS settings, set Free Method to UPS Ground or another service, set Enable Free Shipping Threshold to Enable, and enter the Free Shipping Amount Threshold. Adobe’s documentation says to check each carrier’s configuration for settings free shipping may need.

Why paid options still show next to free shipping

Magento’s delivery-method settings have no option that hides paid methods once free shipping applies. The eight answers to the 2016 Stack Exchange question come down to three routes. The accepted answer drops the Free Shipping method and gives free shipping through a cart price rule, so the flat rate falls to zero instead of a second option appearing (test it on your version). The others are a restrictions extension that hides paid methods above the same cart value, or a small plugin written by a developer.

How to add a free shipping bar in Magento 2

A free shipping bar is a message in the header or the cart that tells shoppers how much more to spend for free shipping and updates as the cart changes. Magento’s free shipping settings set the threshold but don’t show shoppers the amount left, so the bar comes from an extension or a block your developer adds to the theme.

In Baymard’s cart abandonment statistics, 40% of shoppers who left for a reason other than browsing said extra costs such as shipping were too high, and our post on why shoppers abandon carts covers the fixes. A shopper a few dollars short of free delivery has a reason to add one more item.

A Magento 2 free shipping bar extension reads the cart and updates the amount left as it changes, and two are priced in the extensions section. The other route is a static message in a CMS block or a promo bar, which states the threshold without counting down.

Either way, the bar must use the same threshold and the same tax setting as your free shipping rule, or it promises free shipping that the checkout then charges for. You can also put the terms in the checkout shipping policy, which shoppers open from the See our shipping policy link.

Magento 2 shipping restrictions and the rules that need an extension

Natively, you can limit a Magento 2 delivery method by country, and table rates add destination, weight, subtotal or item count. Hiding a method for a customer group, a product, a coupon or a heavy cart, hiding paid options once free shipping applies, and tying payment methods to shipping methods all take an extension or custom code.

Find the rule you want in the left column. Magento shipping restrictions that depend on who the shopper is, or what is in the cart, are the ones the admin can’t do on its own.

Tight Magento 2 shipping rules also mean a shorter list of methods at checkout, which helps whichever layout you run, one-page or two-step checkout alike.

Magento 2 shipping extensions worth installing

Choose a Magento 2 shipping extension by the job it does. Table rate extensions add several rate tables, ZIP code ranges and dimensional weight. Rules extensions add surcharges, discounts and per-product rates. Restriction extensions hide methods by customer, product or cart. Free shipping bar extensions show the amount left. Suites bundle these jobs in one purchase.

Prices were read on the vendors’ pages on November 3, 2026, first year, default edition. Several of these renew yearly, so read the renewal column with the price.

Amasty also bundles its table rates, rules and restrictions modules as Shipping Suite ($529).

Table rates and shipping rules

A Magento 2 shipping table rates extension covers the gaps in the decision table. Amasty Shipping Table Rates adds unlimited table rate methods, ZIP code ranges, volumetric weight, and rates per customer group, which also covers Magento 2 multiple flat rate shipping. Amasty Shipping Rules changes rates you already have, with a surcharge or a discount by product, cart, customer group, or address.

Shipping restrictions

A Magento 2 shipping restrictions extension decides who sees which method. Mageplaza’s shows or hides methods by cart subtotal, item quantity, weight, products, payment method, and location. Amasty’s blocks carrier methods by address, product attributes, order data, customer group, store view, or coupon. Hiding a paid method above a set cart value, the restriction route to the Stack Exchange problem, is a rule both can hold.

Free shipping bars

Both bars do the countdown the native settings leave out. Mageplaza’s adds a promo bar and a promo banner at the lowest first-year price in the table. Point either one at the same threshold and tax setting as your rule.

All-in-one shipping suites

MageWorx Shipping Suite Ultimate covers most of the jobs above in one module, from custom carriers and advanced table rates to delivery dates and time slots, with lifetime source code. Before you buy, check the list of Magento 2 extensions every store needs, and install a Magento 2 extension on a staging copy first, with Hyvä checked if you run it.

Have an AI agent install and set up the extension

An AI agent can take the install and the setup off your developer’s list. Ari, the AI agent for Magento built by scandiweb, installs an extension on a copy of your store with customer data removed, shows you how to set it up and builds promo bars in your theme. A person approves and releases every change.

Ari works with 1,000+ extensions, Amasty’s and Mageplaza’s among them. You can ask Ari to install a free shipping bar extension, or to build promo bars and banners that announce your threshold in your theme’s own markup, Hyvä or Luma. The release is done by your developer, your agency, or Ari engineers on the Ari Agency plan, and Ari has no access to your live store. Plans start from €99 a month per store, and your own developer or agency can do the same work by hand.

For the wider picture, see our post on other AI tools for Magento.

Frequently asked questions about Magento 2 shipping rules

How do I set shipping rates by weight in Magento 2?

Use table rates with the Weight v. Destination condition. Under Stores > Configuration > Sales > Delivery Methods > Table Rates, switch the scope to your website, export the CSV, and add one row per destination and weight band, where the weight means “and above.” Import the file and save. Magento charges the price of the row that matches the address and the cart’s total weight.

Can Magento 2 have more than one table rate?

Not natively. Adobe’s documentation says only one set of table rate data can be active at a time, and the table uses a single condition: weight, subtotal or item count. To offer two table-based methods, such as standard and express, or to combine weight with subtotal, stores add an extension such as Amasty Shipping Table Rates or MageWorx Shipping Suite Ultimate.

How do I hide other shipping methods when free shipping applies?

Magento 2 has no setting for it. The accepted answer on Magento Stack Exchange skips the Free Shipping method and gives free shipping through a cart price rule, so the flat rate drops to zero instead of a second option appearing. Otherwise, a shipping restrictions extension can hide paid methods above the same cart value, or a developer can write a small plugin that filters the rates.

Does Magento 2 have a free shipping bar?

Not in its free shipping settings. The Free Shipping method sets the threshold, the countries and an error message, but nothing tells shoppers how far they are from it. Stores add a bar with an extension, such as Amasty Free Shipping Bar ($119) or Mageplaza Free Shipping Bar & Promotions ($99 for the first year), or have a developer build a message into a CMS block.

Why is free shipping not showing at checkout in Magento 2?

Check four things. The Free Shipping method must be enabled, and the shopper’s country must be in its applicable countries. The Minimum Order Amount is compared with the subtotal after discounts, plus tax only if Include Tax to Amount is Yes, so a coupon can drop a cart below it. A cart rule set to “For shipment with matching items” also needs the Free Shipping method enabled.

Can I restrict shipping methods by country without an extension?

Yes. Every built-in delivery method has a Ship to Applicable Countries setting: choose Specific Countries, pick the list, and set Show Method if Not Applicable to No so the method stays hidden elsewhere. Table rates go further, down to a region or a single ZIP code. Limiting a method by customer group, product, category or coupon needs an extension or custom code.

Start with the shipping rules you already have

Magento 2 shipping rules already cover more than most stores use: flat and table rates, free shipping over a threshold and per-country limits. Start by writing down the rule you want in one sentence, then check it against the native settings above. Buy an extension only for the part the admin can’t do, and test it on a copy first.

Every section above follows that order, admin first and extension second, because most Magento shipping rules never need the second step. If you’d rather hand the setup to a team, our Magento support team builds and tests changes like these in a staging environment before anything reaches the live store.

Send us the shipping rule you want in one sentence and we will tell you what it takes in Magento.

The post Magento 2 Shipping Rules: Table Rates, Free Shipping and the Extensions to Use appeared first on scandiweb.

On November 2, 2026, we found 11 products that call themselves an AI agent for Magento (Adobe Commerce), and they do five different jobs. An agent is AI software that acts on a request, such as changing a product price or writing code, where a chatbot would only answer it. So the job a Magento AI agent does decides what it can touch in your store, and who checks its work before shoppers see it.

One of those jobs happens on the storefront. The other four happen behind it, for your team. Every price and version here comes from each product’s own page, read that day.

Magento AI agent types at a glance

A Magento AI agent is AI software that carries out tasks you describe in a Magento (Adobe Commerce) store. Four types work for store teams: admin chat agents that edit store data, MCP connectors that let your own assistant do it, store-change agents that build code changes on a copy of the store, and developer agents that write code.

The table lists every tool in this article by type, with prices for Magento Open Source.

Prices as listed on each vendor’s page on November 2, 2026. Adobe Commerce editions often cost more. For AI tools that do other jobs, such as content and search, see our guide to Magento AI.

Admin chat agents: ask and edit inside the Magento admin

An admin chat agent adds a chat panel to the Magento admin. It answers questions from live store data, such as last week’s sales or low-stock products, and it can edit products, prices and orders within the signed-in user’s admin role. Some confirm every change and some only the ones that can’t be undone, so check before you buy.

Shopify builds this kind of assistant into its admin as Shopify Sidekick. On Magento, it comes from extensions, and they differ most in what they ask before they act.

Magefan Magento 2 AI Agent

Magefan Magento 2 AI Agent adds an AI chat to the Magento admin that answers from live store data and works on products, categories, orders, invoices, credit memos, shipments, customers, cart price rules, CMS content, caches and indexers. Magefan names the Claude API behind it.

Best for: admin users who want answers such as “Sales summary for last week” or “Low stock products,” plus routine edits by chat.

How it limits changes: each user gets an AI integration based on their admin role, admins can restrict AI actions further, and it works only while the chat is open.

Price (November 2, 2026): €134 one-time, with 365 days of support and updates.

Works with: Magento 2.3.0 to 2.4.9, all editions, Hyvä, Breeze and Mage-OS. Version 2.1.0.

Mirasvit Copilot

Mirasvit calls Mirasvit Copilot “a Magento 2 AI agent embedded directly in the admin panel.” Its 14 tools include a read-only Database Reader and Magento’s REST and GraphQL APIs, for requests such as “Create an invoice for order #100025.”

Best for: stores where several admins share one AI provider key and need a record of every write.

How it limits changes: it acts as the signed-in admin, with tool-level permissions per role and a read-only setting per role or store. It asks before deletes and steps that can’t be undone, and every write lands in a Change Journal.

Price (November 2, 2026): $149 the first year, then $90 a year.

Works with: your own key from OpenAI, Anthropic, Google Gemini or xAI, so staff need no ChatGPT or Claude plan. Magento 2.4 to 2.4.9, Cloud, Mage-OS and Hyvä. Version 1.1.5, October 27, 2026.

Mago

Mago is an open-source AI admin assistant for Magento 2 and Mage-OS. It answers from live store data, changes settings, flushes the cache and runs reindexes. On admin forms it fills in the fields and leaves Save to you.

Best for: teams that want to choose their AI provider, including a local model through Ollama or LM Studio.

How it limits changes: separate admin permissions for read and write tools. “Nothing changes without your OK,” and irreversible actions such as refunds show their impact first.

Price (November 2, 2026): free (MIT), plus what your AI provider bills.

Works with: nine providers, including Anthropic, OpenAI, Ollama and LM Studio. Magento 2.4.8+ or Mage-OS 1.1+, PHP 8.2+. Version 1.1.0, October 22, 2026.

MageAgent

MageAgent is an “AI store operator” you chat with in the admin or over Telegram. It answers about orders, products, customers, sales and abandoned carts, and can change prices and stock, create customers and orders, and issue refunds.

Best for: small teams that want to check orders or change a price from their phone.

How it limits changes: “Every write is a two-step confirmation.”

Price (November 2, 2026): free (MIT).

Works with: Magento 2.4.6+ or Mage-OS, PHP 8.1 to 8.4. A young project, version 0.2.0, September 20, 2026.

Also in this group: the Mage-OS admin assistant (mage-os/module-admin-assist), an open-source chat for admin questions that has no published release yet.

MCP connectors: let ChatGPT or Claude work in your store

An MCP connector is a Magento module that lets an AI assistant your team already uses, such as ChatGPT or Claude, read and change store data through the Model Context Protocol. The connector does nothing on its own. Your assistant decides which tools to call, and the admin role you connect it with decides what it may touch.

To connect Magento to Claude or ChatGPT, you install one of these modules on the store and add it to your assistant. Three of the four below tie each tool to an admin role, so the assistant sees only what that role allows.

Magento 2 MCP module by scandiweb

The Magento 2 MCP module by scandiweb lets Claude, ChatGPT or any MCP client view and edit CMS pages and blocks, categories, products, Hyvä CMS content and Snowdog menus. Our guide to the Magento MCP server covers setup.

Best for: teams that already use Claude or ChatGPT and want it to edit catalog and CMS content, including Hyvä CMS pages.

How it limits changes: every tool is a permission in Magento’s admin roles, and destructive deletes need an explicit confirm=true.

Price (November 2, 2026): free (OSL-3.0).

Works with: Magento 2.4.4+, PHP 8.1 to 8.4, a public HTTPS address, with an admin token or OAuth 2.1 sign-in.

Mirasvit AI Agent Connector

Mirasvit AI Agent Connector is a Magento MCP server with 14 tools, nine that only read and five that can change data (REST API, GraphQL, media upload, cache and indexer).

Best for: teams that use several AI clients (Claude, ChatGPT, Codex, Gemini, Copilot Studio, Cursor) and want one connector.

How it limits changes: only what the admin role allows. Leave out the five write tools for a read-only role, and limit the tables it can see and the IP addresses that can connect. Every write goes into a Change Journal, and sign-in is OAuth 2.1.

Price (November 2, 2026): $149 the first year, then $90 a year.

Works with: Magento 2.3 to 2.4.9 (GraphQL 2.4.4+) and Hyvä. Version 1.2.13, October 28, 2026.

Freento MCP

Freento MCP is an all-in-one MCP server whose tools all read data, covering orders, quotes, credit memos, price rules, coupons, products, categories, prices, customers and system info.

Best for: a first test, reporting on store data from your assistant.

How it limits changes: no write tools. Admin roles pick the tool groups, and sign-in uses OAuth with a one-time password.

Price (November 2, 2026): free (MIT).

Works with: Magento 2.4.x Open Source or Commerce, PHP 8.1+. Version 1.2.1, July 14, 2026.

MageDelight AI Agent MCP Integration

MageDelight AI Agent MCP Integration connects AI assistants to Magento so you can “Execute queries, generate reports, and perform bulk actions” in plain language.

Best for: stores that want reports and bulk edits from an assistant.

Price (November 2, 2026): $149 the first year (Open Source), then $99 a year.

Works with: Magento Open Source, Adobe Commerce and Adobe Commerce Cloud.

Store-change agents: changes built on a copy of the store

A store-change agent takes a request in chat, builds the change on a copy of the store and shows it to your team before anything reaches shoppers. It works on code, themes and extensions as well as store data, and a person approves each change before it is released to the live store.

Agent for Magento (Ari) by scandiweb

Ari, the AI agent for Magento, takes a change you describe in chat and builds it on a copy of your store, a clone of your repository plus a database copy with customer data removed. Your team checks the result on a preview store. Ari then opens a pull request, and a person (your developer, your agency or Ari engineers) merges and releases it.

Best for: store teams with theme, code or extension work waiting for developer time.

What it changes: frontend and backend code, extension installs and conflict fixes, version upgrades and security patches, ERP, PIM and carrier integrations, content and merchandising, and Hyvä theme and checkout rebuilds. Its marketplace holds 1,000+ extensions, which Ari installs on the copy and shows how to set up.

How it limits changes: Ari’s security page says Ari has no access to the live store, the servers or customers’ data. A person approves and releases every change.

Price (November 2, 2026): from €99 a month per store, with 2,000 credits and unlimited seats. Ari Agency, €299 a month, adds Ari engineers who review and release.

Works with: Magento Open Source and Adobe Commerce, Hyvä.

Vortex IQ

Vortex IQ sells AI agent crews for eCommerce teams on Shopify, BigCommerce and Adobe Commerce, including Store Health, Store Development, and Migration and Recovery. Its agents watch the store and connected systems, explain “what broke in plain English” and carry out approved work.

Best for: teams that want store monitoring and diagnosis alongside approved fixes, from one service.

How it limits changes: “Changes tested in a dryrun first, approval-gated, with a way back,” on its DryRunPro test environments. Safeguards depend on the connected platform and workflow, per Vortex IQ.

Price (November 2, 2026): from $399 a month billed annually ($499 month to month), 14-day trial.

Works with: “All versions of Magento, Adobe Commerce and Adobe Commerce Cloud,” per its page.

Developer agents: AI that writes Magento code

A developer agent is an AI coding tool that writes and fixes Magento code in a developer’s editor, terminal or browser workspace, then hands the result to a developer to review and deploy. Adobe’s Commerce Developer Agent builds App Builder apps for Adobe Commerce, and general coding agents such as Claude Code work on any Magento codebase.

Adobe Commerce Developer Agent

The Adobe Commerce Developer Agent is a web workspace where a developer describes a requirement, approves a blueprint, and the agent generates App Builder app code, or plans and migrates existing module code to App Builder. Adobe calls it “a starting-point generator, not a fully autonomous developer,” and adds that “You must review all generated code before using it in a production environment.”

Best for: Adobe Commerce teams moving customizations to App Builder.

How it limits changes: blueprint approval, code review and your own deployment.

Price (November 2, 2026): not listed.

Works with: Adobe Commerce only, per Adobe, with an Adobe Commerce entitlement and App Builder access.

Claude Code with Hyvä AI Skills

Claude Code is “an agentic coding tool that reads your codebase, edits files, runs commands,” and it opens pull requests from a terminal, IDE, desktop app or browser. Hyvä AI Skills, released by Hyvä in January 2026, add 13 Hyvä-specific skills, for child themes, modules and CMS components among others, and work in Claude Code, Codex, Copilot, Cursor, Gemini, Junie and OpenCode. A May 2026 Mage-OS community recap calls Claude Code “the most common default” among Magento developers.

Best for: developers working with Hyvä who want the agent to write Hyvä-style code.

How it limits changes: the developer reviews and commits. Hyvä runs an AI and a human security review on every outside skill before its own team uses it.

Price (November 2, 2026): a Claude plan. The skills are open source (OSL-3.0).

Works with: any Magento codebase, with the skills aimed at Hyvä themes.

magento-boost

magento-boost is an open-source package that gives coding agents (Claude Code, Codex, Cursor, Copilot, Gemini CLI, Junie) Magento guidelines and skills, plus an MCP server that can flush caches, read config, check indexers and query the database through n98-magerun2.

Best for: developers who want their coding agent to check the store while it writes code.

How it limits changes: tool presets read-only, dev-safe (the default) and everything.

Price (November 2, 2026): free (MIT).

Works with: Magento 2.4.x, PHP 8.1+. Version 1.1.0, June 1, 2026.

Magento AI agents that work for shoppers

Two kinds of Magento AI agent work for shoppers. Customer support agents answer questions about orders, returns and products in a chat on the storefront. Agentic commerce modules let outside AI assistants, such as ChatGPT or Claude, search your catalog and build a cart for a shopper, who then pays at your own checkout.

eesel AI answers order, return and product questions in a storefront widget, from $299 a month for 500 chats. For what these cost and how to measure them on any platform, see our guide to AI shopping assistants.

Mirasvit’s Agentic Commerce and MageDelight’s Agentic Commerce Suite make your catalog readable to outside AI assistants through standards such as MCP, UCP and ACP, shared rules that let an AI assistant find and buy products for a shopper. ChatGPT or Claude can then search your products and build a cart that the shopper pays for at your checkout. Mirasvit’s costs $169 the first year and MageDelight’s $149. Our explainer on agentic commerce covers how that works.

How Magento AI agents limit what they change

Magento AI agents limit their changes in four ways: the admin role they act under, a confirmation step before a write, a log of what changed, and where the change lands, on live store data or on a copy of the store. Admin chat agents and MCP connectors rely on the first three, and store-change agents add the copy.

If nobody on your team reviews PHP, a Magento code audit is one way to check what an AI changed.

Which type of Magento AI agent do you need?

Pick the type by the job. For questions and quick edits to products, orders or prices, an admin chat agent is enough. If your team already works in ChatGPT or Claude, add an MCP connector instead. For theme, code and extension changes without a developer, use a store-change agent, and give developers who write modules a developer agent.

Choose an admin chat agent if:

• You want to ask about sales, stock and orders in plain words instead of building a report.
• Your team makes routine edits to products, prices, coupons or orders every day.
• You want a confirmation step before each change to live store data.

Choose an MCP connector if:

• Your team already works in ChatGPT, Claude or Cursor every day and would like it to read or update store data.
• You have someone who can install a module and set admin role permissions.
• You want to start read-only and add write tools later.

Choose a store-change agent if:

• You have a backlog of theme, code or extension changes waiting for developer time.
• You want each change built on a copy of the store and checked on a preview first.
• You want a person to approve every release, as a pull request into your own repository.

Choose a developer agent if:

• Your developers write and fix Magento modules and want to do it faster.
• You run Adobe Commerce and are moving customizations to App Builder.
• Your storefront runs on Hyvä and your developers already use a coding agent.

Frequently asked questions about Magento AI agents

Is there an AI agent for Magento?

Yes, several. On November 2, 2026, 11 products called themselves an AI agent for Magento. Most work for store teams: admin chat agents answer questions and edit store data, MCP connectors let ChatGPT or Claude do the same, store-change agents build code changes on a copy of the store, and Adobe’s Commerce Developer Agent writes code. The rest answer shoppers.

What can an AI agent do in Magento?

It depends on the type. Admin chat agents report on sales, orders and stock and edit products, prices, coupons and orders. MCP connectors give your own AI assistant similar access. Store-change agents build theme, code and extension changes on a copy of the store, including installs and upgrades. Developer agents write and fix module code for a developer to review.

Can an AI agent install extensions or upgrade Magento?

Only the types that work on code. The admin chat agents and MCP connectors in this list work on store data and settings, and some can flush the cache or reindex, but none says it installs modules. A store-change agent can install an extension or apply an upgrade on a copy of the store for a person to release. For the manual route, see how to upgrade Magento.

Is it safe to let an AI agent change my Magento store?

It can be, with limits you set. Give the agent an admin role with only the permissions it needs, start read-only where the tool allows it, and pick a tool that asks before it writes and logs what it changed. For code, theme and extension changes, have the agent work on a copy of the store and let a person review and release each change.

Do Magento AI agents work with Magento Open Source?

Most do. The admin chat agents, MCP connectors and store-change agents in this list support Magento Open Source, and several also list Mage-OS. Adobe’s Commerce Developer Agent is the exception: Adobe says it is available to Adobe Commerce customers only and needs an Adobe Commerce entitlement and App Builder access. See our comparison of Adobe Commerce and Magento Open Source.

How much does an AI agent for Magento cost?

From free to a monthly subscription. Mago, MageAgent and the scandiweb and Freento MCP modules are free and open source. Most paid admin agents and connectors cost $149 for the first year, and Magefan’s AI Agent is €134 one-time. Store-change agents are subscriptions, from €99 a month per store in this list. Most extensions also need your own AI provider key, billed by usage.

Can I build my own AI agent for Magento?

Yes. Developers can connect any agent framework to Magento through its REST and GraphQL APIs, or build your own MCP server that exposes only the store tools you want. Adobe Commerce teams can also generate App Builder apps with Adobe’s Developer Agent. If you would rather have a team build it, see our list of AI agent development companies.

Choosing a Magento AI agent

A Magento AI agent is worth adding when it takes over one job your team repeats every week. Start with that job, check where the agent makes its changes and who approves them, and test it on a copy of the store before it touches anything your shoppers see.

Prices and versions change, so open each vendor’s page again before you buy. Settle the type first, then use the controls table to compare tools within it.

If you’d rather hand that job to people, scandiweb’s Magento support team takes on store changes, extension installs and upgrades.

Tell us the job your team repeats every week, and we'll say which type of agent fits it, or whether a person should do it instead.

The post Magento AI Agents: The 4 Types and the Tools in Each appeared first on scandiweb.

A new theme is the usual fix when a Magento (Adobe Commerce) store starts to look dated or feel slow, which is why teams go looking for the best Magento themes before a redesign. For the look, a theme delivers: it is the layer that decides how every page appears and how much code the shopper’s browser has to load, so one project can change the whole storefront.

Speed and running costs are where the choice gets harder. A theme only changes what happens in the browser, after the server has built the page, and it decides which of your extensions keep working without extra development. Prices and versions below were read on each vendor’s own page on November 3, 2026.

What a Magento theme controls, and what it doesn’t

A Magento theme is the set of layouts, templates, styles and scripts that decide how every storefront page looks and what the shopper’s browser loads. Magento comes with two themes, Blank and Luma, and a custom theme inherits from one of them and overrides only the files it changes. Before the theme does anything, though, the server has to build the page, and a theme does not change that step.

Every page load has two steps. First, Magento’s server builds the whole page by running code and database queries. The time this takes is called time to first byte: how long the server takes to start sending the page. Second, the browser downloads the HTML and the theme’s CSS and JavaScript, and draws the page the shopper can scroll and tap.

A theme changes the second step: a lighter theme means less code to download and run, so the page appears and responds sooner once it arrives. The first step stays as it was, which is why a store can move to a fast theme and still wait at the start of every page view. Our post on why Magento is slow covers both steps.

The best Magento themes at a glance

For most stores in 2026, Hyvä is the theme to build on, and Expedio Theme speeds up page building under whichever theme you run. Luma and Magento Blank come with Magento, Breeze Evolution and Satoshi for Hyvä are free options on different stacks, and Porto and Argento are paid ready-made designs. The table compares all 10 by what each changes, price and fit.

Prices for these Magento 2 themes were read from each vendor’s page on November 3, 2026, in the currency the vendor shows.

How we compared the themes

We judged each pick on four things. The speed shoppers feel: whether it cuts the code the browser loads or the time the server takes to build the page. The cost to run: license, paid add-ons and upkeep. Extension compatibility: whether a store’s existing extensions keep working, or each one with frontend code needs a compatible version. Updates and support: whether the vendor is releasing, which Magento versions it lists, and what support comes with the price.

Vendors change prices without notice, so confirm the figure on the linked page before you sign.

The 10 best Magento themes in 2026

The ranking puts first the picks that change the most for shoppers, then weighs cost and fit. Hyvä leads because it changes what the browser loads on every page, and Expedio Theme follows because it changes how fast the server builds those pages, on any theme. Then come Magento’s defaults, the free options, the paid designs and Adobe’s newer storefronts.

1. Hyvä Theme

Hyvä Theme replaces Magento’s default frontend with a lighter one built on Tailwind CSS and Alpine.js, so the browser downloads and runs less code on every page. Since version 1.4.0 on November 10, 2025, the core theme has been open source under OSL-3.0 and AFL-3.0. The license page gives you up to five free license keys per account, with community support on Slack.

In scandiweb’s September 2026 study of Chrome UX Report data, Magento stores on Hyvä passed all three Core Web Vitals on mobile 66.4% of the time, against 44.6% for Magento overall. Core Web Vitals are Google’s three page-experience measures.

The paid products are optional: Hyvä UI (€250 one-time), Hyvä Checkout (€1,000 one-time) and Hyvä Commerce (€3,000 per year) for Magento Open Source, and Hyvä Enterprise for Adobe Commerce (€7,500 the first year, then €5,000 per year). Hyvä requires Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7 or 2.4.7-p1 or higher, and every extension with frontend code needs a Hyvä-compatible version. scandiweb is a Hyvä Platinum Partner, and our Hyvä theme development team wrote a guide on how to work with Hyvä. We also covered what changed when Hyvä went open source.

Best for: new builds and redesigns where speed in the browser matters most.

2. Expedio Theme

Expedio Theme speeds up how Magento builds every page, so pages arrive in the shopper’s browser sooner. The server step described above, where Magento runs code and database queries before anything is sent, is what Expedio Theme makes faster. It works under your theme, in the server-side work that builds each page. Your Hyvä, Luma or custom storefront, your design, admin, catalog, prices, checkout and orders all stay as they are.

It is built on Liquid, the open-source template language created by Shopify’s co-founder and used in Shopify themes, applied to how Magento builds a page. It runs on Magento Open Source, Adobe Commerce and Adobe Commerce Cloud, on any Magento hosting. Custom themes and the extensions that touch their templates get adapted and tested as part of the setup.

Expedio Theme makes Magento at least 2x faster and lets the same server handle 3x more traffic before response times start to rise. In scandiweb’s benchmark, the median of eight page types was 6.4x faster at peak traffic. Read that figure with its scope: one real merchant’s store on Hyvä was tested, the measure was server response time (time to first byte), not full page load in a browser, and cart and checkout were not part of the comparison.

As the Expedio page puts it, “Hyvä on the frontend with Expedio on the backend is the fastest Magento setup you can run.” Expedio Theme’s core is open source and built by scandiweb.

Best for: any Magento store, on any theme, where pages are slow before the browser starts: slow server responses, slow category and search pages, or traffic peaks.

3. Satoshi for Hyvä

Satoshi for Hyvä is scandiweb’s own design layer for Hyvä stores and the first open-source theme built on top of the Hyvä frontend. It was built by scandiweb’s CTO and licensed under OSL-3.0, which grants a royalty-free license, so there is no theme fee. The current release is v2.0.0 from July 2025, and the product page links to the GitHub repository and a demo store.

It gives you page transitions and animations, product preview peeks with instant add to cart on the product page, and endless pagination with filtering and sorting. It requires the Hyvä Theme (1.3 or newer) with its free license key and no paid Hyvä product. We explain the thinking in our post introducing Satoshi for Hyvä.

Best for: Hyvä stores that want a finished, app-like design instead of styling the default Hyvä theme from scratch.

4. Luma

Luma is the default demonstration theme included with every Magento Open Source and Adobe Commerce 2.4.x install, at no separate price, under OSL-3.0 and AFL-3.0. Adobe’s theme guide states there are no restrictions on using it for a live store, and Adobe continues to support it, so stores on Luma can move to a newer storefront at their own pace.

Luma inherits from Magento Blank, so a child theme overrides only the files it changes. Its stack is LESS with RequireJS, jQuery and Knockout, the stack with the widest extension compatibility here. Scope: Adobe Commerce as a Cloud Service does not support Luma storefronts. On Adobe Commerce running on cloud infrastructure or on-premises (PaaS), Luma Bridge lets Luma pages share cart and sign-in state with an Edge Delivery storefront during a page-by-page migration.

Best for: existing stores on Open Source or Adobe Commerce PaaS and on-premises that need maximum extension compatibility and have no rebuild planned.

5. Breeze Evolution

Breeze Evolution is Swissup Labs’ free, standalone theme on the Breeze frontend, a lighter frontend for Magento 2 that keeps only Knockout and Underscore from the default JavaScript stack. The theme is MIT-licensed, written from scratch in LESS, and splits its CSS into a critical part and a deferred part. The Packagist metapackage is at 3.1.1 from October 8, 2026, and Swissup lists Magento Open Source 2.4.4 through 2.4.9 and Adobe Commerce 2.4.5 through 2.4.9.

Extensions that use JavaScript need an integration, and the Breeze site documents a Better Compatibility mode that reduces the work by loading Luma-based mixins. The paid tier, Breeze Enterprise, comes with a Swissup Labs subscription at $207 per quarter or $588 per year.

Best for: stores that want a faster Luma-style frontend with no license fee and can budget developer time for JavaScript-heavy extensions.

6. Porto

Porto is the best-selling Magento theme on ThemeForest, with 27,877 sales on its item page as of November 3, 2026. A regular license costs $129 one-off and includes future updates and six months of support from p-themes, with an extension to 12 months offered at $42.75 at the time of reading.

Version 5.2.0 was released on August 24, 2026, with fixes for Magento 2.4.8 and 2.4.9 in the changelog. The listing covers Magento 2.3.x and 2.4.x and tags Magento Enterprise as compatible. Porto runs on the standard Luma stack, with no Hyvä edition on the listing or the vendor’s site. Headline features are a mega menu, 300+ admin features and a fluid product grid of 2 to 8 columns.

Best for: stores that want the most-sold ready-made design with many prebuilt layouts on the standard Luma stack, at a one-off $129.

7. Argento

Argento is Swissup Labs’ modular theme, sold as separate packages for the Luma, Breeze and Hyvä frontends, with one license covering all three. On argentotheme.com, the offer is a $90 one-time lifetime license plus $25 per month for support and updates, first month included, valid for up to five Magento installations.

It bundles 24 Swissup extensions, including Ajax Pro, Ajax Search, NavigationPro and Pagespeed. Current versions are Argento Breeze 3.2.1 (October 8, 2026) and Argento for Hyvä 1.3.9 (August 28, 2026), listed for Magento Open Source and Adobe Commerce 2.4.4 through 2.4.9 and Hyvä 1.4 and newer. Swissup’s own store sells Argento within its quarterly ($207) or yearly ($588) subscription instead, covering all Swissup modules on 10 installations.

Best for: budget-conscious stores that want a ready design plus a bundle of extensions from one vendor, with the option to move from Luma to Breeze or Hyvä later.

8. Magento Blank

Magento Blank comes with every Magento Open Source and Adobe Commerce 2.4.x install, at no separate price, and Adobe describes it as a basis for custom theme creation. Luma inherits from it. Blank is the right starting point when the design will be fully custom: a child theme inherits everything from Blank and overrides only the files it changes, so the team decides what goes into every template and style the shopper receives.

Adobe recommends never editing the Blank or Luma files directly, since upgrades can overwrite those changes, so everything custom goes in the child theme. That makes Blank a project for an in-house frontend team or an agency with a custom Magento design practice.

Best for: stores that want a fully custom design built in-house or by an agency, on Magento’s standard frontend stack.

9. Adobe Commerce Storefront

Adobe Commerce Storefront powered by Edge Delivery Services is Adobe’s newer storefront: starter code, drop-in components for product details, cart, checkout, account and B2B flows installed from npm, and document-based authoring in Microsoft Word or Google Docs plus visual editing with Storefront Builder. Adobe recommends it as the starting point on Adobe Commerce as a Cloud Service, and its storefront overview says Adobe continues to support Luma for stores that stay on it.

Scope by edition: the drop-in components are licensed with Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer. Adobe Commerce on cloud infrastructure or on-premises (PaaS) gets them by adding an Adobe Commerce Optimizer license and the Storefront Compatibility Package. Magento Open Source is not supported. Pricing is not published, so ask your Adobe account representative.

Best for: Adobe Commerce as a Cloud Service merchants, or Adobe Commerce PaaS merchants licensing Adobe Commerce Optimizer, who want Adobe’s recommended storefront.

10. PWA Studio and Venia

PWA Studio is Adobe’s open-source toolkit for building a React progressive web app storefront on an Adobe Commerce or Magento Open Source backend, with Venia as the reference storefront to start from. It is licensed under OSL-3.0 on GitHub and still receives releases: v14.5.2 was published on November 3, 2026, and the repo’s compatibility map pairs it with Magento 2.4.10.

It includes React hooks and components (Peregrine and Venia UI), an extensibility framework in the buildpack, the UPWARD connector for serving the PWA from Magento and a Page Builder extension. Adobe’s release notes for 14.5.2 report Lighthouse performance scores of 98 on desktop for all four Venia pages and 67 to 75 on mobile. For the wider set of options, see our Magento PWA solution comparison.

Best for: teams that already run or maintain a PWA Studio storefront and need a supported upgrade path. For new builds, it is a niche choice.

Free vs paid Magento 2 themes

Free Magento 2 themes (Hyvä core, Luma, Magento Blank, Breeze Evolution and Satoshi for Hyvä) cost nothing to license. The spend moves to add-ons, support and the build: Hyvä’s checkout and UI packs, Breeze Enterprise, developer time for extension compatibility, and the design work. Premium Magento themes such as Porto and Argento charge up front and include a design and a support period.

How to choose the best Magento theme for your store

Match the theme to the one thing your store needs most. Build on Hyvä when you’re starting new or redesigning, stay on Luma when the store works and no redesign is planned, and add Expedio Theme when the server step is the slow one. The other picks cover narrower cases, listed below, and the chart sums them up.

• Choose Hyvä Theme if you’re building new or redesigning and speed in the browser matters most. Add Satoshi for Hyvä if you want a finished design to start from.
• Add Expedio Theme if pages are slow before the browser starts: slow server response, slow category and search pages, traffic peaks. It works on any theme, including Luma and custom themes. For the browser side, see our Magento speed optimization extensions.
• Choose Breeze Evolution if you want a lighter, free Luma-style frontend and can budget developer time for JavaScript-heavy extensions.
• Choose Porto if you want the best-selling ready-made paid design with many layouts.
• Choose Magento Blank as the base when you want a fully custom design.
• Choose Argento if you want a modular paid theme with vendor support and the option to change frontend branch later.
• Choose Adobe Commerce Storefront if you’re on Adobe Commerce as a Cloud Service, or on PaaS with an Adobe Commerce Optimizer license, and starting a new storefront.
• Choose PWA Studio only if you already run it.
• Stay on Luma for now if the store works and a redesign isn’t planned. Expedio Theme can still make it faster.

B2B stores pick on the same criteria, plus whether company accounts, purchase orders and quotes are covered. Adobe Commerce Storefront has B2B drop-ins for purchase orders, company management and quote management. For the other picks, that coverage comes from extensions, so run the same compatibility check.

Frequently asked questions about Magento themes

The best Magento theme for most stores is Hyvä, which is free at the core and strongest on browser speed, with Expedio Theme on the server for the fastest setup. A template is one file inside a theme, you can switch themes on a live store after testing on staging, and Expedio Theme works under the theme you have. The details follow.

What is the best Magento theme in 2026?

For most new builds and redesigns, Hyvä Theme, with Satoshi for Hyvä on top when you want a finished design. Stay on Luma if the store works and no redesign is planned, start from Magento Blank for a fully custom design, and use Adobe Commerce Storefront on Adobe Commerce as a Cloud Service. Under any of them, Expedio Theme makes the server build pages at least 2x faster.

Is Hyvä free to use?

Yes. The Hyvä Theme core has been free and open source under OSL-3.0 and AFL-3.0 since version 1.4.0 on November 10, 2025, with up to five free license keys per account and community support on Slack. The paid products are Hyvä UI (€250), Hyvä Checkout (€1,000), Hyvä Commerce (€3,000 per year) and, for Adobe Commerce, Hyvä Enterprise (€7,500 the first year, then €5,000 per year).

What is the fastest Magento 2 theme?

On the browser side, Hyvä has the strongest field data. In September 2026 Chrome UX Report data, Hyvä stores passed Core Web Vitals on mobile 66.4% of the time, against 44.6% for Magento overall. A theme leaves the server step alone, and that is where Expedio Theme works, making page building at least 2x faster on any theme. Together they cover both steps of the page load.

What is the difference between a Magento theme and a template?

A theme is the whole package Magento applies to every page: layouts, templates, styles and scripts. A template is one file inside it, the PHTML file that renders one block, such as the product gallery or the mini cart. In search, Magento templates and Magento website templates usually mean full themes, so judge any listing by the criteria above: speed, cost to run, extension compatibility, and updates and support.

Can you change the theme on a live Magento store?

Yes. A theme is assigned in the Magento admin, so the switch itself is quick. Do it on a staging copy first: every extension with frontend parts needs a version compatible with the new theme (a Hyvä compatibility module, a Breeze integration or a Luma child theme), and the checkout and your top-selling pages need a test run before the live switch.

Does Expedio Theme replace Hyvä or Luma?

No. Expedio Theme works under your theme, in the server-side work that builds each page, and your Hyvä, Luma or custom storefront, design and data stay as they are. It runs on Magento Open Source, Adobe Commerce and Adobe Commerce Cloud, on any Magento hosting, and the admin, catalog, prices, checkout and orders are untouched. You keep the theme you have, and the server builds its pages faster.

Choosing from the best Magento themes

The best Magento themes in 2026 come down to a short list once you know which step of the page load you need to fix. Hyvä is the theme to build on for a new store or a redesign, Satoshi for Hyvä gives you a finished design on top of it, and Luma and Magento Blank remain sound choices for a store that works or a design built from scratch. Breeze Evolution, Porto and Argento cover the free and paid ready-made ground, and Adobe’s Edge Delivery storefront is the path on Adobe Commerce as a Cloud Service.

Under any of them, Expedio Theme speeds up the server step. Read the prices again on the vendor pages before you sign, since they were current on November 3, 2026, and may have moved. scandiweb is a Hyvä Platinum Partner with 894+ Adobe certifications and 23+ years in eCommerce.

If you're planning a Hyvä build or want to know how much faster your current theme could run, talk to our Magento team.

The post Best Magento Themes in 2026: The Top 10, Ranked appeared first on scandiweb.

Vibe coding started as a post on X, and it is now a question for Magento (Adobe Commerce) store owners too. In February 2025 Andrej Karpathy, an AI researcher, used the term for a way of coding where you describe what you want in plain language, let an AI write the code, and “forget that the code even exists.” By November, Collins Dictionary had named it Word of the Year.

That is easy to picture for a new app built from nothing. Your store is a different case. It already takes orders, it runs custom code someone wrote years ago, and it cannot go down while you try things. So the question for a Magento store owner is whether vibe coding can work on a store like that, and what you would type.

What vibe coding means on a Magento store

On a Magento store, vibe coding means you describe a change in a chat and an AI agent builds it. With Ari, the AI agent for Magento built by scandiweb, the change is built on a copy of your store, you look at the result on a preview store, and a person releases it. You judge what you see, the way you would judge a designer’s draft. You don’t have to read the code.

Alfreds Genkins, CTO at scandiweb, created Ari. In the October 28 webinar he compared the Ari control panel to Lovable, the app builder: “You might have seen Lovable before, and that’s exactly that. That’s Lovable for your Magento. We tried to make it as easy as building features in Lovable, but in the complexity of Magento.”

The copy is what makes this safe to try. Ari works in its own repository with its own instance of your store, so the live store keeps selling while you try things on the preview.

Four requests from the live demo

In the webinar, Alfreds walked through requests in Ari, some typed live and some from earlier conversations. Four of them show what a request looks like as typed, what came back, and where you, the store owner, come in. None of them needed a line of code from the person asking.

“The header blends into the white page a bit”

The conversation started with “Hi! Our designer sent the new header designs”, with the designer’s mockups attached. Before calling the job done, Ari listed what it had checked: the desktop header and mega menu at 1440 pixels wide, the mobile menu at 375, and the header at an in-between width of 1024, where “the first build broke here and was fixed.” A before-and-after comparison below the header showed that nothing else on the page had changed.

Ari also flagged what it had left out. The mockups showed Store Locator, Blog, FAQ, and Careers links that don’t exist on the store, so none were added, and Ari asked whether the currency switcher was the “pill” the design meant.

One detail bothered Alfreds, so he typed: “The header blends into the white page a bit. Could you make the header background a light grey?” A follow-up works the same way as the first request: look at the preview and say in plain words what is off.

“Looking to build a blog. How do I start?”

That was the whole request. Ari answered with the simplest route, Blog by Magefan: a paid extension at $149 that adds posts, categories, tags, authors, and comments, with a trial available. Then it asked: “Would you like to try it out, or would you prefer a custom blog built for your store?”

“I never said I want an extension. And it offered me options,” Alfreds said.

He chose the trial and asked Ari to keep the checks light. Ari installed the extension on the copy and replied: “Blog is installed on your Ari store. It reaches your live store only when you release this change.” Then it suggested next steps, such as writing the first post or seeing how comments work. The same route is open from Ari’s extension marketplace, where you pick an extension, press “Try it out,” and Ari installs it on the copy and guides you through the setup.

“What’s going on in Ari?”

Ari has connected apps, so you can use it from ChatGPT or Claude, the AI assistants. In ChatGPT, Alfreds asked what was going on in Ari and got a live update: the header color change was in progress. You can also give Ari tasks from there, without opening the control panel.

“@support, please make sure it’s all perfect”

Type “@support” in the chat and the support team is notified. Requests collect in a separate support tab, and you can send images.

When the header was ready, Ari merged the finished changes into a release draft, showed it on the preview, and set out a test plan:

• the new header is in place and looks right on desktop and mobile
• the home page, product pages, and category pages open without errors
• search, the cart, and the checkout still work end to end
• the admin opens, with any new settings in place

Alfreds typed “Go ahead,” and his note went to support: “please make sure it’s all perfect!” After you sign off, a person or an automation takes it from there. A pull request is opened to your production repository, or your deployment pipeline is triggered, as set up at onboarding.

What one store owner handed over in his first month

Martin Thompson owns a health products store in New Zealand and has run it on Magento since 2009. Before Ari, he had planned to move to a .NET platform because basic work cost too much. In his first month, within his plan’s credits, Ari upgraded an extension, built a Klaviyo integration, fixed a product snippet issue, installed a security patch, fixed a speed issue, and fixed a duplicated menu left by a previous developer.

He tested everything Ari did on his end, and it was right almost every time. “It kept things simple and to the point. It didn’t overengineer things,” he said.

His routine is short: “It will tell me that it’s on my preview site, and then I go and test that. I used to just talk to the developer. Now I just say it’s ready for release and I tag the developer in the portal, and they’ll release it.”

The first night, he stayed up until about 2 a.m. After that, he told the developer to deploy whenever they were confident, went to sleep, and the change went live the next day. He says he got more done in that month than in the previous three.

Requests worth starting with

Start with a change you would otherwise put in a ticket: something small, visible to shoppers, and easy to check on the preview. These come from Ari’s own examples and from Martin’s first month, written the way a merchant would type them.

• A product page block: “Show a delivery date under the Add to cart button on every product page.”
• A promo bar, a banner, or a change to the menu.
• An extension, such as Mageplaza’s SEO Suite. An install uses 50 to 150 credits, about €2.50 to €7.50 on the €99 plan. The manual route is in our guide to installing a Magento 2 extension.
• An upgrade: “Upgrade us from 2.4.6 to 2.4.9 and tell me what breaks.” Our guide on how to upgrade Magento covers what such an upgrade involves.
• A fix, such as a product snippet issue or a duplicated menu left by a previous developer.
• An integration, such as connecting the store to Klaviyo.
• A custom feature, such as finding product information online and adding it to the product.

Anything technically possible inside Magento is open, including integrations with outside APIs.

How to phrase a request

Say what the shopper or your team should see and where, the way you would brief a developer. “Show a delivery date under the Add to cart button on every product page” is a complete request. You do not need to know which part of Magento it touches, and you can write it in any language.

A few habits from the demo and the Q&A make the rest easier:

• If details are missing, Ari asks clarifying questions and offers options for how to build it before it starts.
• You can queue as many requests as you want. They run one after another on your store’s copy, and Ari tells you when each one is done.
• Check the result on the preview link. You can browse it any time, and it has nothing to do with production.
• When something looks off, reply in the same chat, the way Alfreds did with the header.
• Release when you are happy. Until then, nothing changes for shoppers.

What Ari won’t do from the chat

Ari never changes your live store from the chat. Everything it builds happens on a sanitized copy of your store, in a separate environment, like a staging environment, and a person releases each change. The limits below come from the webinar Q&A.

• The copy has your products but no customer personal data. The database is sanitized, or you provide a sanitized copy.
• Ari never changes the database directly. It writes migration patches instead, including for content changes, the way a good agency or a good developer would.
• Ari does not work inside systems outside Magento, such as an ERP or a CRM. It can build the integration with them, and if a feature belongs in a PIM, it can say where it should live.
• Keys and passwords stay out of the chat. You paste them into the admin yourself.
• The release is always a person’s call: your developer or agency on the Ari plan, or Ari engineers on Ari Agency.

Frequently asked questions about vibe coding Magento

Can you vibe code a Magento store?

Yes, with an AI agent that works on a copy of the store. With Ari, you describe the change in a chat, Ari builds it on a sanitized copy of your Magento store, and you check the result on a preview store. A person then releases it, through a pull request to your repository or your deployment pipeline. Ari is a store-change agent, one of the four types of Magento AI agents.

Do I need to read the code Ari writes?

No. You judge the result on the preview store, the way Martin Thompson tests every change on his preview site before tagging his developer for release. The code comes back to your own repository, so your developer or agency can review it before release if they want to.

Can Ari work on several requests at once?

You can queue as many requests as you want. Ari switches between them, builds each one, and tells you when one is done. They run one after another, because there is one Magento instance behind the copy, so two builds cannot run side by side.

Does it work on a Hyvä store?

Yes. In the webinar Q&A, Alfreds said Hyvä CMS is covered by Ari’s knowledge base, and Ari also installs Hyvä Theme, Hyvä Checkout, and Hyvä extensions. As with any other change, Ari writes migration patches rather than editing the database directly, so the change can be reviewed and deployed through your usual process.

Who is responsible if a released change breaks something?

That depends on the plan. On the self-managed Ari plan, your own team or agency releases the changes and is responsible for them. On Ari Agency, the Ari team takes that responsibility end to end. Ari also monitors the store’s uptime: one night it restarted Varnish, the caching server in front of Magento, on Martin Thompson’s store when it went down.

What does vibe coding a Magento store cost with Ari?

Ari is €99 a month with 2,000 credits included, and you or your developers release the changes. Ari Agency is €299 a month with 2,000 credits, managed by Ari engineers who carry the responsibility end to end. An extension install uses 50 to 150 credits, about €2.50 to €7.50 on the €99 plan.

Start vibe coding your Magento store with one request

Vibe coding a Magento store works when the request is plain, the change lands on a copy, and a person releases it. That is the pattern the webinar demo showed, from a header redesign and a blog to a release with a test plan and a note to support. It is also how Martin Thompson went from planning to leave Magento to working through his backlog.

Glebs Vrevsky, co-founder of Ari, gave one piece of advice in the webinar: take one task from your backlog and deliver it the new way. Then compare the time, the cost, and the effort with how that task would have gone through a ticket.

The header, the blog, the ChatGPT check-in, and the release step are all in the recording, where you can watch the full webinar.

Want to try vibe coding on your own Magento store? Book an Ari demo and bring the first request from your backlog.

The post Vibe Coding a Magento Store: What You Can Ask Ari to Build appeared first on scandiweb.

You probably have a few quotes open and are comparing one number on each: what the Magento (Adobe Commerce) developer charges an hour. For a 20-minute job, such as a new tax rule or an update to an extension (an add-on module), the real Magento developer cost depends on how that time is billed. Under a one-hour minimum per task, you pay for 60 minutes of a 20-minute fix. A retainer, a monthly fee for a set block of hours, changes the total too, and so does handover: the paid hours a new developer spends learning your store’s code.

Every range comes from a public page you can open, and we read each on November 2, 2026: freelance marketplaces’ rate pages, job-ad trackers, a US government wage survey, and a directory where agencies list their rates. Each figure comes with its source and how that source collects its numbers.

Magento developer cost at a glance

Magento developer cost in 2026 starts around $16 an hour, the low end of the median contract rates Upwork reports worldwide. On Clutch, 13% of Magento firms that show a rate list $100 an hour or more. In-house, US job ads on Indeed average $99,595 a year for a Magento developer, before benefits.

Fiverr’s figures are for bug fixes and maintenance. Clutch shows the rate band each firm lists, counted on November 2, 2026.

These are people costs. License, hosting, and a full build are covered in our guide to Magento pricing.

Magento developer rates by region

Magento developer rates follow local pay levels. Arc’s 2026 survey of freelance developers on all stacks puts US and Canadian freelancers at $82 to $130 an hour, Eastern Europe at $40 to $85, and South Asia at $22 to $55. Magento freelancers in Germany, Austria, and Switzerland list an average of €85 an hour on freelancermap.

Arc’s ranges cover freelance developers on all stacks. The right column adds the Magento-only figures we found for each region.

Give more weight to the Magento-only column, since Arc’s figures include every stack. Upwork’s worldwide median for Magento contracts, $16 to $35 an hour, falls at or below the low end of Arc’s range for every region in the table except South Asia. Figures stay in the currency each source uses.

Magento developer hourly rate by seniority

A Magento developer’s hourly rate rises steeply with experience. Fiverr’s 2026 Magento cost guide puts entry-level developers at $12 to $28 an hour, mid-level developers at $30 to $75, and senior architects at $70 to $200. Match the level to the task: a routine change rarely needs an architect, and a custom integration rarely suits a beginner.

A listed agency band or a marketplace median rarely says which level it buys. The Magento developer price per hour that matters is the rate of the person who will open your code, so ask each provider which developer does the work and at what level.

Freelancer, contractor, in-house, or agency: what each costs

Each hiring model bills differently. Freelancers bill per hour or per task, contractors bill a day rate for full-time project work, in-house developers cost a salary plus benefits every month, and agencies bill hours or a retainer for a team that can cover absences and several skills. Compare what each model costs over a year for your workload.

Freelance Magento developer rates

Three marketplaces publish Magento figures, and each measures something different. Upwork reports median rates from past contracts: $16 to $35 an hour for Magento developers and $18 to $39 for Magento 2 developers. Fiverr’s marketplace data puts bug fixes and maintenance at $20 to $120 an hour, with fixed-price jobs averaging $94. On freelancermap, the 1,379 freelancers in Germany, Austria, and Switzerland who list Magento in their profiles ask €85 an hour on average, an asking rate rather than a paid one.

A Magento freelancer bills for the hours worked, and the cost of a Magento developer at that rate includes your own time. You check the work before it goes live, and you cover the gap when the freelancer is away.

Contractor day rates

In the UK, contract job ads citing Magento quoted a median day rate of £480 in the six months to November 2, 2026, according to ITJobsWatch, up from £463 in the same period of 2025 and £406 in 2024. That is a small sample, 13 day rates from 25 job ads, so treat it as a marker rather than a benchmark. A contractor suits full-time project work with an end date, such as a rebuild or a version upgrade, where one person works on your store every day for a set period.

In-house Magento developer salary and its full cost

In the US, Indeed averages $99,595 a year for a Magento developer, from 38 salaries in job postings over the past 36 months. The US Bureau of Labor Statistics puts the median wage for all web developers at $92,650 (May 2025), from its survey of employers. In the UK, ITJobsWatch shows a £42,500 median salary in job ads citing Magento (52 salaries), and Indeed UK reports £40,329 from 134 salaries.

The salary is the visible part. In the BLS Employer Costs for Employee Compensation release for June 2026, wages were 70.0% of what private employers pay per hour worked and benefits the other 30.0%. On that all-industry average, a $99,595 salary costs the employer about $142,000 a year, an estimate before recruiting, equipment, and software. A salary also pays for holidays, meetings, and learning time, so the cost per hour of store work is higher than the salary divided by 2,080 hours.

Agency rates on Clutch

Clutch publishes no average rate, but its Magento directory lets you filter firms by the hourly band each one lists on its own profile. We counted those bands on November 2, 2026: of 6,749 firms listed, 5,479 show a band, 67% of them list under $50 an hour, and 13% list $100 or more.

A listed band does not say which seniority, minimum, or retainer terms come with it, and the category includes firms that list Magento as one service among many. What an agency adds for the money is cover when a developer is away and several skills, such as frontend, backend, and DevOps, under one contract.

What a small Magento job really costs

A small Magento job costs the time billed, which can be more than the time worked. A 20-minute fix billed in 10-minute segments costs 20 minutes, in 15-minute increments 30 minutes, and under a one-hour minimum a full hour. Retainers prepay hours each month, and a new developer may bill hours to learn your store before the first fix.

Small jobs here are tasks of under an hour: a tax rule, an email template, a new column in an admin grid, an update to one of your Magento 2 extensions. A version upgrade is a project of its own (see how to upgrade Magento).

Minimum billable time and billing increments

Take one 20-minute fix at $60 an hour, a rate chosen only as an example, and bill it under three different rules.

Same work, same rate, and the Magento developer cost for the task is three times higher under the strictest rule. The 10-minute segment is how Upwork tracks hourly contracts, according to its help center page on work diaries. The other two are terms a provider sets for itself. Magento developer minimum billable hours are rarely printed on a rate card, so ask every provider for its billing increment and any per-ticket minimum, in writing.

Retainers: when a block of hours pays off

A Magento retainer prepays a block of developer hours each month at an agreed rate, and the arithmetic decides whether it pays. A 10-hour retainer you use for four hours costs 2.5 times the rate for each hour used. The same retainer used in full costs exactly the rate. Before you sign, check whether unused hours roll over to the next month, what an hour beyond the block costs, and how fast urgent requests are answered.

For the services a retainer should cover and how to read the invoice, see what a support retainer should include.

Handover: the hours before the first fix

A new developer needs access to your code repository, a copy of the database, and your deploy process, and then time to read your custom modules before a first fix is safe to make. Those hours are billed once per new developer, so they come back every time you switch providers. Ask how many onboarding hours a provider bills before the first task, and ask the outgoing developer to write down what they know about the store while they still have access.

Where an AI agent fits in a Magento budget

An AI agent for Magento charges a monthly subscription instead of an hourly rate. You describe a store change in chat, the agent builds it, and a person reviews and releases it. For small jobs, the subscription replaces some developer hours, but someone still checks each change, so budget for review time as well as the plan.

Content generators and admin chat agents work on store data inside the admin. Agents that change code, themes, and extensions are the ones that take on developer hours.

Ari, the AI agent for Magento built by scandiweb, is one option of this kind. Its self-managed plan costs €99 a month per store, with 2,000 credits and unlimited seats included, and your own developers review each change and release it. The Ari Agency plan, at €299 a month, adds Ari engineers and a dedicated project manager who take responsibility for delivery. Ari builds each change on a copy of your store with customer data removed and returns it as a pull request, so nothing reaches the live store until a person approves it.

In plain arithmetic: at the €85 average that Magento freelancers in Germany, Austria, and Switzerland list on freelancermap, €99 buys a little more than one hour. At Upwork’s worldwide median of $16 to $35 an hour, €99 (about $111 at the European Central Bank rate for November 2, 2026) buys three to seven hours. A subscription pays off when your small jobs would cost more in minimum billable time than the plan plus the review hours. See Ari’s plans and pricing.

How to choose a hiring model for your Magento budget

Choose by the size and rhythm of your Magento work. A few defined tasks a month suit a freelancer, a project of a few months suits a contractor, and full-time work all year suits an in-house developer. Steady small jobs across several skills suit an agency retainer, and a queue of small changes with a reviewer suits an AI agent.

Choose a freelance Magento developer if:

• You have a few defined tasks a month and can describe each one in writing.
• You have someone who can check the work before it goes live.

Choose a contractor if:

• You have a project of a few months, such as a rebuild or a version upgrade, that needs one person full time.
• You want a fixed day rate and a clear end date.

Choose an in-house developer if:

• Your Magento work fills a full-time role all year.
• You want the knowledge of your store’s code to stay inside the company.

Choose an agency retainer if:

• Your small jobs add up to a similar number of hours every month.
• You need several skills, such as frontend and DevOps, or cover when one developer is away.

Choose an AI agent subscription if:

• You have a queue of small store changes waiting for developer time.
• You have a developer or agency who can review each change and release it.

Frequently asked questions about Magento developer cost

How much does a Magento developer cost per hour?

It depends on where and how you hire. Upwork reports median Magento contract rates of $16 to $35 an hour worldwide. On Clutch, two in three Magento firms that list a rate list under $50 an hour, and 13% list $100 or more. Arc’s 2026 survey puts US and Canadian freelance developers at $82 to $130 an hour.

How much does it cost to hire a Magento expert?

A senior Magento specialist costs $70 to $200 an hour on Fiverr, which calls this level senior architects with six or more years of platform experience. Arc’s survey puts senior freelance developers on all stacks at $75 to $150 an hour. In the UK, the median day rate in Magento contract job ads is £480, according to ITJobsWatch.

What is a Magento developer’s salary?

In the US, Indeed averages $99,595 a year from 38 Magento developer salaries in job postings over the past 36 months. The US Bureau of Labor Statistics puts the median for all web developers at $92,650 (May 2025). In the UK, ITJobsWatch shows a £42,500 median for permanent jobs citing Magento in the six months to November 2, 2026.

Are freelance Magento developers cheaper than agencies?

Per hour, usually yes. Upwork’s median Magento contract rates run $16 to $35 worldwide, while 72% of Magento firms on Clutch that list a rate list $25 an hour or more. Per job, billing rules and handover decide. At a one-hour minimum, a $30 rate costs $30 for a 20-minute fix, while $60 an hour billed in 10-minute segments costs $20.

Do Magento developers charge a minimum per task?

Some do, so ask before you agree a rate. On Upwork, hourly contracts are tracked in 10-minute billing segments, so a 20-minute fix is billed as 20 minutes. Billed in 15-minute increments, the same fix counts as 30 minutes, and under a one-hour minimum per ticket it counts as 60. The billing rule can triple the cost of a small job.

Is a Magento support retainer worth it?

A retainer is worth it when your small jobs fill most of its hours every month. It prepays a block of developer time, so a 10-hour retainer you use for four hours costs 2.5 times the rate for each hour used. Check whether unused hours roll over, what extra hours cost, and how fast urgent requests are answered.

What to ask before you agree a Magento developer rate

Magento developer rates follow local pay levels. Arc’s 2026 survey of freelance developers puts the US and Canada at $82 to $130 an hour, Western Europe at $70 to $120, Eastern Europe at $40 to $85, and South Asia at $22 to $55. Public data puts most marketplace and agency rates under $100 an hour, with senior and North American work above that.

So what will your store pay? It depends. The region, the developer’s seniority, the hiring model, and how the hours are billed all move the total. Before you sign, ask each provider how it would bill a 20-minute task and what handover will cost. Also ask whether unused retainer hours roll over.

If most of your work is a queue of small changes, you can also hand it to an AI agent and pay a monthly subscription instead of billed hours. Ari, the AI agent for Magento, builds each change on a copy of your store, and a person reviews it before it goes live.

If you want a number for your own store, send us your task list and we will quote it.

The post How Much Does a Magento Developer Cost? Hourly Rates and Retainers in 2026 appeared first on scandiweb.

Which job should AI take off your Magento (Adobe Commerce) team’s list first: the product descriptions nobody has time to write, or the store changes waiting in the developer queue? Both are sold as Magento AI, yet a module that writes copy in the admin and an agent (software that carries out a task you describe in chat) that edits your theme need very different access to your store, and they carry different risks.

The prices, supported Magento versions and compatibility with Hyvä, a popular Magento frontend theme, come from each vendor’s own page or from Adobe’s documentation, read on November 2, 2026. Check your edition as well as the price, because not every tool here runs on both Magento Open Source and Adobe Commerce.

Magento AI tools at a glance

Magento AI is any tool that uses an AI model to do a job in a Magento (Adobe Commerce) store: writing content, answering shoppers, ranking search results, summarizing reviews, connecting your own AI assistant or changing the store itself. Most of it comes from extensions and services, and Adobe’s own AI search and recommendations require Adobe Commerce.

Prices are for Magento Open Source as listed on each vendor’s page on November 2, 2026. Adobe Commerce editions cost more.

AI agents for Magento: store changes and admin requests

An AI agent for Magento carries out a task you describe in chat. Admin chat agents work on store data inside the Magento admin, within each user’s admin role. Store-change agents work on code, themes and extensions: they build the change on a copy of the store, and a person approves the release. Magento has no built-in assistant like Shopify Sidekick that changes the store from the admin, so stores add agents from third-party vendors.

1. Agent for Magento (Ari) by scandiweb

Ari, the AI agent for Magento, takes store changes you describe in chat and builds them on a copy of your store with customer data removed. Your team checks the result on a preview store, and a person approves it and releases it as a pull request. Its marketplace holds 1,000+ extensions from vendors including Amasty and Magefan, and Ari installs each one on a copy of the store and shows how to set it up (see the Ari extension marketplace). Ari’s security page says it has no access to the live store, servers or customers’ data.

Best for: store teams with a backlog of frontend, backend or extension work who want each change built and checked before anyone releases it.

Key features:

• Frontend and backend changes, extension installs and conflict fixes
• Magento version upgrades and security patches
• ERP, PIM and carrier integrations
• Content and merchandising, Hyvä theme and checkout rebuilds

Price (November 2, 2026): from €99 a month per store, with unlimited seats. Ari engineers can be added for review and release. Enterprise plan on request.

Works with: Magento Open Source and Adobe Commerce, Hyvä, Luma and custom themes.

2. Magefan Magento 2 AI Agent

Magefan Magento 2 AI Agent adds an AI chat panel to the Magento admin that answers questions from live store data and carries out admin requests. Magefan says it can find, create, update and delete store entities, including products, categories and cart price rules.

Best for: admin users who want sales summaries, stock checks and routine catalog edits by asking in chat, for example “Sales summary for last week” or “Low stock products”.

Key features:

• Reusable prompt templates and reports from real-time store data
• Works with products, orders, invoices, shipments, refunds, customers, blog content, cache and indexers
• Follows each user’s admin permissions (ACL), with an option to restrict AI actions further

Price (November 2, 2026): €134 one-time, with 365 days of updates and support.

Works with: Magento 2.3.0 to 2.4.9 (Open Source, Adobe Commerce, Commerce Cloud, B2B), Hyvä, Breeze and Mage-OS. Version 2.1.0. Magefan names the Claude API as its AI connection.

Magento 2 AI content generators for ChatGPT, Gemini and Claude

A Magento 2 AI content generator writes product descriptions, category text and meta tags inside the admin, using a model from OpenAI (ChatGPT), Google (Gemini) or Anthropic (Claude). Most need your own API key, and the AI provider bills you for what you generate on top of the extension price. Read the text before you publish it.

3. Mirasvit AI Content Generator and Assistant

Mirasvit AI Content Generator and Assistant writes product and category descriptions, meta tags, CMS content, blog posts, help desk replies and newsletters inside the admin.

Best for: large catalogs that need bulk rewrites or translations by store view, with a record of what changed.

Key features:

• Bulk rules by attribute, with a dry run first
• Translation rules per store view
• Keeps the previous value of every changed field
• Six admin permissions for who can generate

Price (November 2, 2026): $149 the first year (Open Source), then $90 a year. Commerce and Cloud editions cost more.

Works with: OpenAI (ChatGPT), Anthropic (Claude), Google (Gemini) and xAI (Grok) through your own API key. Magento 2.3 to 2.4.9, Hyvä. Version 1.8.2, October 28, 2026.

4. Amasty ChatGPT AI Content Generator

Amasty ChatGPT AI Content Generator generates product, category and CMS text, meta tags and product images from attributes or custom prompts, one product at a time or by mass action.

Best for: stores that need copy and images from one Magento 2 ChatGPT extension, with Page Builder support.

Key features:

• ChatGPT models from GPT-4 to GPT-5.5, plus Gemini 3 models
• Amasty AI Service lets subscribers generate without their own API key
• Unique content per store view
• Pro adds translation, email and newsletter templates, and generation history

Price (November 2, 2026): $189 a year (Community edition), Pro $259.

Works with: Magento 2.4.5-p15 to 2.4.9, Hyvä Theme and Hyvä Checkout. Version 6.4.1.

5. Meetanshi Magento 2 AI Content Generator

Meetanshi Magento 2 AI Content Generator bulk-generates titles, meta descriptions and descriptions for products, categories and CMS pages with ChatGPT or Gemini models.

Best for: smaller catalogs on a small budget, with a log of who generated what.

Key features:

• Custom prompts with Magento variables
• Page Builder support and multi-language content by store view
• AI Content Log by user, date and store view

Price (November 2, 2026): $99 (Open Source), $150 more for Adobe Commerce editions. One year of support and updates, free installation.

Works with: your own OpenAI or Gemini API key. Magento 2.3.0 to 2.4.9, Hyvä. Version 1.0.6, May 19, 2026.

Magento AI chatbots and shopping assistants

A Magento AI chatbot answers shoppers in a chat window on the storefront. It uses your product data to suggest items and answer product questions, and both extensions below can look up an order’s status. Each question goes to the AI provider you connect, so check that provider’s data terms before launch.

For what AI shopping assistants cost and how to measure them on any platform, see our guide to AI shopping assistants. The two Magento 2 chatbot extensions below differ in which AI providers they connect to and in what your staff can do in the same chat window.

6. Meetanshi Magento 2 AI Chatbot

Meetanshi Magento 2 AI Chatbot is a storefront chatbot that suggests products, answers product and store questions, and tracks orders by order ID. It uses RAG, which means it looks up your product data before it answers.

Best for: stores where shoppers ask product-fit questions (“is this suitable for oily skin?”) and “where is my order”.

Key features:

• Gemini models, or any OpenAI-compatible provider including a local Ollama model
• A business context section for store policies
• Choice of which product attributes to index
• Full chat history in the admin

Price (November 2, 2026): $299 (Open Source), $150 more for Adobe Commerce editions.

Works with: Magento 2.3.0 to 2.4.9, Hyvä, Luma and custom themes. Version 1.0.1, May 19, 2026.

7. Mirasvit eChat

Mirasvit eChat is an AI chatbot that answers from your catalog and CMS pages, shows product cards with photos and prices, and lets shoppers check order status and download invoices.

Best for: teams that want the AI and a human agent in the same chat window, so staff can take over a conversation.

Key features:

• OpenAI, Anthropic, Google or xAI through your own key, with no per-conversation fee from Mirasvit
• Order status and tracking
• Support tickets with Mirasvit Help Desk MX

Price (November 2, 2026): $149 the first year (Open Source), then $90 a year.

Works with: Magento 2.3 to 2.4.9, Magento Cloud, Mage-OS, Hyvä. Version 1.6.1, October 27, 2026.

Magento 2 AI search and product recommendations

Magento 2 AI search replaces the default catalog search with a service that ranks results by what shoppers are likely to want and can suggest related products. Adobe Commerce stores get Adobe’s Live Search and Product Recommendations. Magento Open Source can’t use them, so Open Source stores add a third-party search service instead.

8. Adobe Live Search and Product Recommendations

Adobe Live Search and Product Recommendations are Adobe’s own AI services for Adobe Commerce. Live Search replaces Magento’s standard search with “AI-powered dynamic faceting and re-ranking of search results”, and Product Recommendations use “Adobe AI and machine learning trained on aggregated shopper behavior and catalog data”.

Best for: Adobe Commerce stores on 2.4.4 or later.

Key features:

• SaaS services connected through the Commerce Services Connector
• Search and recommendation widgets for the storefront
• Recommendations managed in the Commerce Admin

Price (November 2, 2026): Live Search is “included in your license”. Adobe’s pages don’t state a price for Product Recommendations.

Works with: Adobe Commerce on cloud and on-premises, 2.4.4 and later. Adobe’s setup guide says these services “require Adobe Commerce” and “are not available for Magento Open Source.”

9. Algolia for Magento 2

Algolia for Magento 2 is a free extension that replaces the default search in Magento Open Source and Adobe Commerce with Algolia’s hosted search, autocomplete and recommendations.

Best for: Magento Open Source stores that need AI ranking without Adobe Commerce.

Key features:

• Autocomplete and an instant results page
• Algolia Recommend: frequently bought together, related products, trending items, looking similar
• AI Ranking on the Grow Plus plan

Price (November 2, 2026): the extension is free. Grow Plus (“keyword search with AI capabilities”) includes 10,000 search requests a month, then $1.75 per 1,000. Enterprise plans are custom.

Works with: the latest version supports Magento 2.4.8 and 2.4.9.

Magento 2 AI review summaries

A Magento 2 AI review summary extension turns a product’s customer reviews into a short summary on the product page, usually with the main positives and negatives. It helps most on products with many reviews. Before you buy, check which AI provider it uses and whether you need your own API key.

10. MageDelight AI Review Summary

MageDelight AI Review Summary shows AI-generated summaries of customer reviews on the product page.

Best for: stores whose best sellers have more reviews than a shopper will read.

Key features:

• Review summary on the storefront
• Customer sentiment analysis
• One module for Open Source, Commerce and Cloud

Price (November 2, 2026): $129 the first year (Open Source), $249 (Adobe Commerce), $349 (Commerce Cloud), then $89 a year.

Works with: Magento 2.4.7 to 2.4.9. MageDelight says all its extensions are Hyvä-ready. The page doesn’t name the AI provider, so check before buying.

Also available: Webkul’s ChatGPT Product Review Summary ($199, nine AI providers), Meetanshi’s AI Reviews Summary (Google Gemini), and Amasty’s content generator, which summarizes reviews together with Amasty’s reviews extension.

MCP connectors: use ChatGPT or Claude with your Magento store

An MCP connector lets an AI assistant you already use, such as ChatGPT or Claude, read and change your Magento store through the Model Context Protocol, a standard way for AI tools to call another system. The connector does nothing on its own, and Magento’s admin roles decide which of its tools the assistant can use.

To connect Magento to Claude or ChatGPT, install one of the two modules below. Each runs on your store and shows the assistant only the tools it is allowed to call.

11. Magento 2 MCP module by scandiweb

Magento 2 MCP module by scandiweb is an open-source module that lets an AI assistant such as Claude or ChatGPT view and edit store content over MCP: CMS pages and blocks, categories, products, Hyvä CMS and Snowdog menus. Our guide to the Magento MCP server covers installation and setup.

Best for: teams that already use an AI assistant and need it to edit catalog and CMS content within admin roles.

Key features:

• Every tool is a resource in Magento’s admin role permissions
• Destructive deletes need an explicit confirm=true
• Sign-in with an admin token or OAuth 2.1
• Hyvä and Snowdog tools appear only when those modules are installed

Price (November 2, 2026): free, open source (OSL-3.0).

Works with: Magento 2.4.4 and later, PHP 8.1 to 8.4, a public HTTPS address.

12. Mirasvit AI Agent Connector (MCP)

Mirasvit AI Agent Connector is a Magento 2 MCP server that gives AI clients access to the REST API, GraphQL, read-only database queries, media upload and store diagnostics.

Best for: teams that use several AI clients (Claude, ChatGPT, Cursor, Gemini, Copilot Studio) and need one connector for all of them.

Key features:

• Nine read-only tools and five that can change data
• Each tool a separate admin role permission
• Every write logged in a Change Journal
• OAuth 2.1 and an IP allowlist

Price (November 2, 2026): $149 the first year (Open Source), then $90 a year.

Works with: Magento 2.3 to 2.4.9 (the GraphQL tool needs 2.4.4 or later), Magento Cloud, Mage-OS, Hyvä. Version 1.2.13, October 28, 2026.

Adobe Commerce AI features by edition

Adobe’s own AI for Magento is mostly for Adobe Commerce. Live Search and Product Recommendations require Adobe Commerce and aren’t available for Magento Open Source. The Commerce Developer Agent needs an Adobe Commerce entitlement and App Builder access. Adobe also offers a Commerce MCP server and a Brand Concierge integration for building shopper-facing AI.

Adobe announced the general availability of the Commerce Developer Agent on September 25, 2026. Adobe has also committed to the Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP), standards that let AI assistants find and buy products for a shopper, a shift often called agentic commerce. The wider differences between Adobe Commerce and Magento Open Source are in our edition comparison.

Which Magento AI tool do you need? Choose by job

Choose a Magento AI tool by the job you want done. Content generators save writing time in the admin. Chatbots and AI search help shoppers find products, and review summaries help them decide. MCP connectors let your own assistant work with store data, and agents take on store changes or admin requests you describe in chat.

Choose an AI content generator if:

• You have hundreds of products with thin or missing descriptions and meta tags.
• You sell in several store views and need the same copy in each language.

Choose an AI chatbot if:

• Your support inbox fills with “where is my order” and product-fit questions.
• You want shoppers to get product suggestions in a chat window on the storefront.

Choose AI search and recommendations if:

• You run Adobe Commerce 2.4.4 or later and haven’t switched on Live Search.
• You run Magento Open Source and need AI ranking from a third-party search service.

Choose a review summary extension if:

• Your best sellers have more reviews than a shopper will read before buying.

Choose an MCP connector if:

• Your team already works in ChatGPT, Claude or Cursor and wants it to read or update store data.
• You have a developer to install the module and set the admin role permissions.

Choose an admin chat agent if:

• You want sales summaries, stock checks and routine catalog edits by asking in the admin.

Choose a store-change agent if:

• You have a backlog of storefront, backend or extension work waiting for developer time.
• You want each change built on a copy of the store, checked on a preview and released by a person.

How to add AI to a Magento store without risking the live site

Add AI to a Magento store the way you would add any extension. Confirm it supports your edition and version, and install it on a copy of the store before a person checks and releases it. Then limit what it can change with admin roles, and know which AI provider receives your store data.

1. Check edition and version. Vendor pages list the Magento versions and editions they support. Adobe’s own AI services need Adobe Commerce.
2. Know who pays for the AI. Most content tools and chatbots use your own API key, and the provider bills you for usage on top of the extension price.
3. Install it on a copy of the store first. Every AI module is still an extension, so the usual rules for Magento 2 extensions every store needs apply: one tool per job, tested before release. Our guide shows how to install a Magento 2 extension with Composer or a ZIP file.
4. Limit what it can change. Use admin roles for admin agents and MCP connectors, start with read-only access, and read AI-written copy before it goes live. Mirasvit’s dry run and stored previous values help here.
5. Know where store data goes. Shopper questions and product data go to the AI provider you connect, so check that provider’s data terms.

Agents that change code need the same care at a larger scale. Ari, for example, builds each change on a copy of the store with customer data removed, your team checks it on a preview store, and a person releases it. See how Ari builds and releases a change.

Frequently asked questions about Magento AI

Does Magento have built-in AI?

Adobe Commerce includes Adobe’s AI-powered Live Search in its license and offers Product Recommendations, which uses Adobe AI and machine learning trained on shopper behavior and catalog data. Adobe’s setup guide says both require Adobe Commerce and aren’t available for Magento Open Source. Open Source stores add AI through extensions and third-party services.

How much does it cost to add AI to Magento?

It depends on the job. The extensions in this list cost $99 to $299 for Magento Open Source, more for Adobe Commerce editions, and most add AI provider fees billed to your own API key. Live Search is included in the Adobe Commerce license. The store-change agent here starts at €99 a month per store.

How do I use ChatGPT with Magento 2?

Content generators such as Amasty’s and Mirasvit’s use OpenAI’s ChatGPT models to write store copy in the admin. To let ChatGPT itself read or change store data, install an MCP connector, which works within your Magento admin roles. Selling inside ChatGPT is a separate project: see how to list your products in ChatGPT shopping.

Can AI make changes to a Magento store?

Yes, with limits you set. Admin chat agents edit store data such as products and cart price rules within each user’s admin role. Store-change agents build code, theme and extension changes on a copy of the store, and a person approves the release. Test any AI tool on a copy of the store before it touches the live site.

Can Magento Open Source use Adobe Live Search?

No. Adobe’s setup guide says Catalog Service, Live Search and Product Recommendations require Adobe Commerce and are not available for Magento Open Source. Open Source stores can use a third-party service instead, such as Algolia, whose free Magento 2 extension replaces the default search on both Magento Open Source and Adobe Commerce.

Do Magento AI extensions work with Hyvä?

Most do. Mirasvit, Amasty, Meetanshi and Magefan state Hyvä compatibility on their product pages, and Amasty’s content generator also supports Hyvä Checkout. MageDelight says all its extensions are Hyvä-ready. Check the vendor’s own page for the exact module and version, because Hyvä support can differ between a vendor’s extensions.

Do I need my own OpenAI API key for a Magento AI extension?

Usually, yes. Mirasvit and Meetanshi ask you to connect an API key from OpenAI, Google, Anthropic or another provider, and that provider bills you for usage. Amasty’s AI Service lets subscribers generate content without their own key. Check the vendor’s page for which models it supports before you buy.

Start with one Magento AI job

Magento AI pays off fastest when it starts with one job. Pick the job that costs your team the most time today, whether that is product content, shopper questions, search, reviews or store changes, test one tool for it on a copy of the store, and add the next job once the first one works.

Prices and versions above are what each vendor page or Adobe’s documentation showed on November 2, 2026, so open the page again before you buy.

For a plan that matches AI tools to your store’s priorities and your edition, talk to scandiweb about AI strategy consulting for eCommerce.

Tell us your first AI job, and we'll say which of these tools fits your store and edition.

The post Magento AI: The Best AI Extensions and Agents for Magento 2, Grouped by Job appeared first on scandiweb.

On October 13, 2026, Adobe published security bulletin APSB26-153 for Magento (Adobe Commerce), with fixes for 11 security holes, and the worst of them scored 10.0 out of 10 for severity. A security bulletin is Adobe’s public notice of what it fixed and which versions get the fix, and each fix reaches your store as a patch: a small file of code changes that closes the hole without a full version upgrade. Adobe’s notes for the October patch also warn that it leaves out September’s emergency fix for a flaw attackers were already using. So which Magento security patch does your store need, and is it already installed?

Every command below comes from Adobe’s own documentation, checked on November 2, 2026, and the Adobe Commerce Cloud differences are marked where they apply.

What is a Magento security patch?

A Magento security patch is a code change from Adobe that closes known security holes in Magento Open Source or Adobe Commerce without adding features. Most arrive in two forms: a security patch release such as 2.4.8-p5, and smaller monthly isolated patch files in between. A flaw that attackers already use gets an emergency hotfix.

Adobe uses the word patch for four different things, and the table shows how each one arrives and how you apply it.

The security patch release is the base, and it installs through Composer, the tool that manages Magento’s code packages. Adobe’s release policy requires the latest -p release for your line before any monthly isolated file goes on.

Every monthly file is then folded into the next security patch release, so a store that moves to the next -p release picks up the months it missed. Each fix carries a CVE, the public ID number a security hole gets, and each bulletin lists the CVEs it closes along with the fixed versions, whether it announces a Magento patch release or a hotfix.

Which Magento security patches does your store need?

Your store needs the latest security patch release for its version line, then every monthly isolated patch Adobe has published since, in release order, plus any hotfix announced on top. Which files exist depends on your version and edition: in October 2026, Adobe’s isolated patch files for Magento Open Source started at 2.4.7.

Adobe’s most recent files, from bulletin APSB26-153 in October 2026, show the pattern for each line.

Whatever your line, check for a hotfix announced since your last patch: it is not part of the monthly file.

Find your Magento version and edition

The version shows in the bottom-right corner of any Admin page. If it is hidden, run bin/magento --version.

Note the edition as well, because Magento Open Source and Adobe Commerce get different files. If you run 2.4.8 or older and the version has no -p suffix, you are behind the latest Magento 2 security patch release, since every line from 2.4.4 to 2.4.8 has one.

Read the bulletin’s affected and fixed versions

Each Adobe Commerce security bulletin has two tables. The first lists the affected versions, the second lists the fixed ones. A label such as 2.4.8-2026-sep means a 2.4.8 store patched through September, and 2.4.8-2026-oct means the same store with October’s file applied.

The October bulletin lists Magento Open Source 2.4.6 as affected, and its fixed versions for Open Source start at 2.4.7, which is why the edition matters. New bulletins are published in the Adobe Trust Center, so bookmark that page rather than Adobe’s older HelpX page.

How to check which Magento security patches are installed

To check which Magento security patches are installed, run Adobe’s Commerce Version Tool from the project root with php vendor/bin/patch-status. It lists applied and missing patches and marks each CVE as PROTECTED, VULNERABLE or UNKNOWN. The tool came with the July 2026 isolated patch, so if the command is missing, apply that file first.

Missing one patch is a common gap: in a scandiweb check of 13,000 Magento 1 stores, published in 2019, 14.82% were open to major breaches, mostly because a single patch was missing.

php vendor/bin/patch-status --version
php vendor/bin/patch-status

Read two lists in the output. applied_patches should hold every monthly file since your -p release, and missing_patches should be empty, with each CVE marked PROTECTED. The output is machine-readable, so you can run it automatically as part of continuous integration (CI) and report on it.

On Adobe Commerce Cloud, check both the patch files and the Cloud Patches package, Adobe’s bundle of required fixes that Cloud applies at deployment.

vendor/bin/magento-patches -n status | grep "248p5-2026-10-001-CE\|Status"
php ./vendor/bin/ece-patches status

The first command shows whether one monthly file is applied, and the second is Adobe’s status check for Cloud Patches for Commerce.

How to apply a Magento security patch, step by step

To apply a Magento security patch, back up the store and work on a staging copy first. Move to the latest -p release for your version, then apply each isolated patch file from the Magento root with patch -p1, oldest month first and CE before EE. Refresh the cache, confirm the result with patch-status, test the store, and release.

1. Back up the store and copy it to staging. Adobe strongly recommends applying and testing every patch on a staging or integration environment first, and keeping a recent backup.

1. Move to the latest -p release for your line. The commands below are for Magento Open Source. On Adobe Commerce, replace magento/product-community-edition with magento/product-enterprise-edition. The full routine, with maintenance mode and compilation, is in our guide on how to upgrade Magento.

composer require-commerce magento/product-community-edition 2.4.8-p5 --no-update
composer update
bin/magento setup:upgrade

1. Download the month’s patch files. Open the bulletin’s knowledge base article, which for October is Adobe’s October 2026 patch article, download the ZIP for your line, and unzip it. Adobe Commerce 2.4.6 or earlier asks for your Composer keys before the download.

1. Apply each file from the Magento root. Apply any missed month first, then CE before EE, then B2B if you run it. CE is the Open Source code and EE the Adobe Commerce code, and Adobe’s order within a month is the CE file, then the EE file. Adobe’s isolated patch guide describes this as how to install a Magento patch file on-premises and on Magento Open Source.

patch -p1 < 248p5-2026-10-001-CE.patch

If that fails, try -p2 instead.

patch -p2 < 248p5-2026-10-001-CE.patch

1. Refresh the cache. In the Admin, open System > Cache Management and refresh it there.

1. Check the result. Run php vendor/bin/patch-status again. The month’s patches should appear under applied_patches, with nothing in missing_patches.

1. Test on staging, then release. Run your usual checkout and admin checks. Then apply the same files in production through your normal deployment. Adobe’s guide says you can apply a patch locally with the same command, then commit and push it as usual.

On a store that skipped several months, repeat step 4 for each month, oldest first: each file assumes the earlier ones are in place, and patch-status lists a skipped month as missing.

How to apply an emergency hotfix

A hotfix arrives on its own, with its own bulletin, as a Composer patch file. Adobe’s October article says September’s hotfix for CVE-2026-75650 is not included in the October isolated file and must be applied separately. Upload it to the Magento root and run the same patch command, then refresh the cache.

patch -p1 < %patch_name%.composer.patch

On Cloud, copy the file to the m2-hotfixes folder in your project, commit, and push. Apply a hotfix as soon as it passes staging. September’s hotfix also meant rotating every exposed credential, which our StyleSmuggler patch guide covers step by step.

How to undo a patch

Quality patches have a revert command. Run ./vendor/bin/magento-patches revert <PATCH-ID> for one patch or ./vendor/bin/magento-patches revert --all for all of them, then ./bin/magento cache:clean. On Cloud, delete a custom patch file from m2-hotfixes and push.

Isolated monthly files have no documented revert command. When Adobe revised October’s 2.4.8-p5 file, it told merchants to reverse the original by using their established patch-management process. So commit each patch file on its own, and roll back that commit if testing fails.

Magento patch tools: Quality Patches Tool or Composer patches?

Use the Quality Patches Tool for Adobe’s official patches and Composer patches for your own fixes. Adobe’s documentation says it does not support applying official, Adobe-provided patches with the cweagans/composer-patches plugin. Monthly isolated security patches are a separate case: they come as patch files, applied with the patch command or, on Cloud, through Cloud Patches for Commerce.

The Quality Patches Tool needs Git or the patch utility installed and writes a log to var/log/patch.log. Adobe’s documentation for the tool warns that applying many patches makes the next upgrade harder, so apply a quality patch only for a bug your store has.

The command-line method in Adobe’s patch guide is the one for the monthly files. For what a Composer patch looks like and how to write your own, see how Composer patches work.

How patching works on Adobe Commerce Cloud

On Adobe Commerce Cloud, the Cloud Patches for Commerce package applies required security fixes during your next deployment, through ECE-Tools. Check your installed Cloud Patches version before adding a monthly isolated file, because applying a fix that is already in place can make the install fail. Your own patch files go in the m2-hotfixes folder.

During a deployment, ECE-Tools, the deployment toolset for Adobe Commerce Cloud, applies patches in a fixed order, with the required patches from Cloud Patches for Commerce first, then the optional quality patches you selected, then your own files in m2-hotfixes in alphabetical order. You select quality patches in .magento.env.yaml, the Cloud project’s configuration file, using the IDs that magento-patches status shows for your store, in place of Adobe’s example IDs below.

stage:
  build:
    QUALITY_PATCHES:
      - MCTEST-1002
      - MCTEST-1003

Your own patch files, and any Adobe Commerce security patch you apply by hand, go into m2-hotfixes. Copy the .patch file into the folder, then commit and push, and check the result with ece-patches status.

mkdir m2-hotfixes
git add m2-hotfixes/
git commit -m "Apply 248p5-2026-10-001-CE.patch patch"
git push origin <branch-name>
php ./vendor/bin/ece-patches status

Adobe’s Cloud patching guide covers the packages and the order.

What to do when your Magento version no longer gets patches

When Adobe stops publishing patches for your version, plan the upgrade to a supported line. Adobe Commerce 2.4.4 and 2.4.5 get isolated security fixes only until May 31, 2027, and Adobe’s October 2026 files for Magento Open Source covered 2.4.7 and later. Until the upgrade is live, backported fixes and close monitoring lower the risk.

Under Adobe’s lifecycle policy, the security-only period for 2.4.4 and 2.4.5 brings isolated security fixes and no quality fixes, and 2.4.7 has standard support until the same May 31, 2027 date. Adobe Commerce 2.4.6 has extended support until August 31, 2027, and security-only fixes until May 31, 2028. Every line’s dates are in our list of Magento end of life dates.

If the upgrade is the real fix, scandiweb’s Magento upgrade services can plan it from your current version. For one critical flaw on an old release, a backport can buy time: our StyleSmuggler fix for older Magento versions covers 41 releases from 2.2.0 to 2.4.3-p3. Keep the Security Scan Tool running in the meantime.

How to keep up with Adobe’s monthly patches

Adobe publishes isolated security patches every month on Patch Tuesday, the second Tuesday of the month, and may release extra patches between them. Subscribe to Adobe’s free security notifications and keep a fixed monthly slot for testing and applying the new files. Agree in advance who applies an emergency hotfix, because those can’t wait for the slot.

Two Adobe pages carry the schedule. Adobe’s monthly patching policy sets out the Patch Tuesday cadence and the order rules, and Adobe’s security notification service emails you each new bulletin for free. Since bulletins moved to the Trust Center in September 2026, the email is the easiest way to hear about a hotfix, because a hotfix comes with its own bulletin on its own day.

Magento patches close the holes in the core. Magento 2 security also depends on the extensions and custom code around it, and Adobe’s enforcement policy puts auditing third-party extensions and securing custom code on the merchant, alongside applying the patches.

Put Patch Tuesday in the calendar

Patch Tuesday is the second Tuesday of the month, and the next one is November 10, 2026. Book a staging slot for the days after it, with the person who applies the files and the person who tests checkout.

Read your extension vendors’ changelogs in the same slot. In November it comes right before the Black Friday code freeze, so book it early.

Decide who applies the patches

A developer on your team can do it with server access and a staging copy. The job is the seven steps above once a month, plus a hotfix now and then. To budget for it, see what a Magento developer costs per hour and on a retainer.

A support partner applies them on a schedule and runs the same staging test, which suits a store with no developer of its own.

A third option is Ari, the AI agent for Magento built by scandiweb. Your team asks for the month’s patch in chat. Ari applies and checks it on a copy of the store with customer data removed, the team reviews the result on a preview store, and a person approves it and releases it as a pull request. Ari has no access to the live store, its servers, or the live database. See how Ari can apply Magento security patches for your store.

Frequently asked questions about Magento security patches

Are Magento security patches cumulative?

Security patch releases are cumulative: each -p release includes the security and quality fixes of the patch release before it. Monthly isolated patch files are not. Adobe calls them non-cumulative, standalone files, so you apply every month’s file in release order on top of the latest -p release for your version line.

Can I skip a month of Magento security patches?

No. Adobe builds each monthly isolated patch on top of the previous month’s, so a store that missed September has to apply September’s files before October’s. Within a month, apply the CE file first, then EE, then the matching B2B file if you run B2B. Run php vendor/bin/patch-status afterward to check that nothing is missing.

Do I still need a hotfix if I install the monthly patch?

Yes. Adobe’s October 2026 knowledge base article says the hotfix for CVE-2026-75650 from bulletin APSB26-146 is not included in the October isolated patch file and must be applied separately. Adobe also reported that this flaw was exploited in the wild, and its notice asks merchants to rotate the encryption key and every exposed credential.

Can I apply Magento security patches with Composer?

Partly. Security patch releases such as 2.4.8-p5 install with Composer, using composer require-commerce and composer update. Monthly isolated patch files are not Composer packages, so you apply them with the patch command. Adobe also says it does not support applying its official patches through the cweagans/composer-patches plugin, which is meant for your own fixes.

Does Magento Open Source get security patches?

Yes, for supported versions. Adobe’s monthly isolated patches cover Magento Open Source as well as Adobe Commerce, but the October 2026 files for Open Source were available only for 2.4.7 and later. Bulletin APSB26-153 lists Open Source 2.4.6 as affected without a fixed version, so 2.4.6 stores need an upgrade plan.

Is the Magento Security Scan Tool free?

Yes. Adobe’s Security Scan Tool is free from the dashboard of your Commerce or Magento account, for both Adobe Commerce and Magento Open Source. It runs more than 21,000 security tests, watches for security risks and malware, and can run weekly, daily or on demand. A Magento security scan checks the live site from the outside, so pair it with patch-status, which reads the code. See Adobe’s Security Scan Tool guide.

Keep every Magento security patch on schedule

A Magento security patch is only done when the files for every month since your last -p release are applied in order and patch-status shows no missing patches. Check your version and edition today, read the latest bulletin, test the files on a staging copy, and book the next Patch Tuesday in the team calendar.

Whoever applies them, the staging test before release is the step that protects checkout. If nobody on your team owns the monthly patch slot, scandiweb’s Magento support and maintenance plans apply Adobe security patches on schedule, tested before release.

If you want a second pair of eyes on your patch status, talk to our Magento support team.

The post How to Apply a Magento Security Patch (and Know Which Ones You Need) appeared first on scandiweb.

Setting up Varnish, the caching server Adobe recommends in front of every live Magento 2 (Adobe Commerce) store, usually takes an afternoon. It keeps finished copies of your pages and hands them to shoppers, so Magento doesn’t have to build each page again. You install it, switch the store over in the admin, load the file Magento generates, and restart. A test page comes back from the cache at once, and at the time, the Magento 2 Varnish configuration looks finished.

Then the odd problems start: a price change that doesn’t show, a homepage that loses its styling after a release, error pages that come and go.

The admin setting only tells Magento that Varnish exists. What Varnish keeps, for how long, and what it drops when a product changes is set in the VCL, the file of rules Varnish runs. Even then, some requests go on to Magento, where the shopper waits for the page build.

What a Magento 2 Varnish configuration includes

A Magento 2 Varnish configuration has four parts: Varnish itself, at a version Adobe supports and with enough memory, the Full Page Cache setting in the Magento admin, the VCL file that Magento generates and Varnish runs, and the purge hosts in Magento’s env.php file, which let Magento clear pages from Varnish when content changes.

In production, Varnish is the full page cache. How a page is cached, keyed and purged is covered in that guide, so this one stays on the Varnish side.

VCL stands for Varnish Configuration Language. The file Magento generates is a starting point, and once you edit it, it is yours: keep your changes in version control and reapply them after each re-export, because a new export doesn’t carry them.

Which Varnish version does Magento 2 support?

Magento 2.4.9 supports Varnish 8, according to Adobe’s system requirements, and so does the latest 2.4.8 patch, 2.4.8-p5. Our Magento 2 system requirements guide lists the other versions each release needs. Earlier 2.4.8 releases list Varnish 7.x, and Adobe’s table gives a version for each older patch line as well. Magento’s VCL generator includes templates for Varnish 6 and 7 only, so on Varnish 8, generate the Varnish 7 file and test it on staging first.

Supported Varnish versions and the VCL templates each Magento release includes. The 2.4.7 line and older have no Varnish 7 template, even where Adobe lists Varnish 8 for their latest patch.

The template number is the lowest Varnish version it supports. On 2.4.9 the Varnish 6 and Varnish 7 files are identical apart from two comment lines, so either one gives the same rules, and nothing in them uses the functions that the Varnish 8.0 upgrade notes list as removed. Adobe hasn’t published a Varnish 8 template, so compile the file with varnishd -C -f default.vcl on your Varnish 8 build and run a purge on staging before it goes live.

Varnish 8 and the Vinyl Cache name

Varnish is still in use, and Adobe still strongly recommends it in production. The open-source project behind it is now called Vinyl Cache. Varnish Cache 8.0, released in September 2025, was its last release line under the old name, and Vinyl Cache 9.0 followed in March 2026. Varnish Software continues a separate distribution that keeps the Varnish Cache name. Adobe’s table says Varnish 8, so install the newest 8.0.x package, 8.0.2 at the time of writing, and check it with varnishd -V before you generate the VCL. The September 2026 advisory VSV00020 covers 8.0.2, but only for VCL that calls the .upper() or .lower() string methods, and the file Magento generates calls neither.

How to configure Varnish for Magento 2, step by step

To configure Varnish for Magento 2:

1. Put Varnish on port 80 and move the web server to port 8080.
2. Set Caching Application to Varnish Cache in the admin.
3. Generate the VCL with bin/magento varnish:vcl:generate --export-version=7.
4. Check the health check URL.
5. Allow Magento to purge.
6. Set memory and header limits, then restart.

These steps assume Magento on-premises. On Adobe Commerce Cloud, skip to the last section.

1. Put Varnish in front of the web server

Varnish listens on port 80 and the web server, nginx or Apache, moves to port 8080, as in Adobe’s guide to configuring nginx for Varnish. Use an IP address or hostname for the backend rather than localhost, even on one machine. For HTTPS, a TLS terminator in front of Varnish passes X-Forwarded-Proto: https, the header Magento’s VCL expects by default, so HTTP and HTTPS copies of a page stay apart.

2. Switch Magento to Varnish and generate the VCL

In the admin’s Full Page Cache section, set Caching Application to Varnish Cache (Recommended), fill in the access list, backend host and port, and grace period, then use the export button for your Varnish version. On 2.4.9 there are buttons for Varnish 6 and Varnish 7. The command line does the same with bin/magento varnish:vcl:generate and the options in Adobe’s CLI reference. Two traps: the default --export-version is still 6, and --access-list takes one IP per flag. Back up /etc/varnish/default.vcl before you replace it, then restart Varnish.

A starting point. Replace the IPs with your own servers.

bin/magento varnish:vcl:generate \
  --export-version=7 \
  --backend-host=192.0.2.20 \
  --backend-port=8080 \
  --access-list=192.0.2.20 \
  --access-list=192.0.2.21 \
  --grace-period=300 \
  --output-file=/tmp/default.vcl

3. Point the health check at the right file

The probe calls health_check.php every 5 seconds with a 2-second timeout and marks the backend sick when fewer than 5 of the last 10 checks pass. The script returns 500 when MySQL or the cache storage can’t be reached. The path depends on your web root. The VCL from 2.4.7 on probes /health_check.php, which fits a web root of pub/. With the Magento folder as the web root, use the older /pub/health_check.php form, which Adobe’s advanced page still shows, because Magento keeps the script only in pub/. Open the URL from the Varnish server to confirm it answers, because a wrong path fails every check and Varnish then treats Magento as down.

From the 2.4.9 VCL. Use /pub/health_check.php if your web root is the Magento folder rather than pub/.

backend default {
    .host = "192.0.2.20";
    .port = "8080";
    .first_byte_timeout = 600s;
    .probe = {
        .url = "/health_check.php";
        .timeout = 2s;
        .interval = 5s;
        .window = 10;
        .threshold = 5;
    }
}

4. Let Magento purge Varnish

When a product, category or price changes, Magento sends a PURGE request with the cache tags to each host in http_cache_hosts. Set them with setup:config:set --http-cache-hosts. Without them, Magento purges the store’s own host name on port 80, which misses a Varnish on another port or server. Varnish accepts a purge only from an IP in acl purge and answers 405 otherwise. In most setups that means the address of every server that runs Magento, which is what the generator’s access list is for. Adobe’s page words it as the Varnish host’s IP, the same machine when the two share a server, so with a load balancer in between, check which address Varnish sees. On several web servers, as in an autoscaling setup, every node sends purges. When Magento can’t reach any purge host, it logs “No cache server(s) could be purged” in var/log/system.log. A 405 from Varnish leaves no log entry, so test each Magento server with the purge request below.

Comma-separated, no spaces. The port can be left out for port 80. The test purge bans a tag that no page carries, so it clears nothing: 200 Purged means the server is allowed, 405 means it isn’t.

bin/magento setup:config:set --http-cache-hosts=192.0.2.30:80,192.0.2.31:80

# Run on each Magento server: 200 Purged = allowed, 405 = not in acl purge
curl -i -X PURGE -H 'X-Magento-Tags-Pattern: ((^|,)no_such_tag(,|$))' http://192.0.2.30/

5. Set memory and header limits before you go live

With no storage option, Varnish starts with 100 MB, and Adobe gives no size. Give it what the server can spare and watch the eviction counter covered in the measurement section. Category pages carry one cache tag per product in the X-Magento-Tags header, and past Varnish’s 8 KB default the browser gets 503 Backend Fetch Failed. Adobe’s 503 guidance sizes http_resp_hdr_len from the largest category, product count times 21, and raises http_resp_size with it. Varnish takes the response headers from workspace_backend, 96 KB by default, which Adobe’s snippet also sets, so give it room above http_resp_size. These options live in your Varnish service file, and the path depends on the OS. Change them well before peak season and your code freeze, then retest with a load test at peak traffic.

A starting point from Adobe’s 503 guidance. Size the header limit from your largest category (products × 21), keep the workspace above the response size, and set the memory to what the server can spare.

varnishd -a :80 -f /etc/varnish/default.vcl \
  -s malloc,<size> \
  -p http_resp_hdr_len=65536 \
  -p http_resp_size=98304 \
  -p workspace_backend=131072

On Adobe Commerce Cloud, configure Fastly instead

On Adobe Commerce Cloud, full page caching uses Fastly, a Varnish-based CDN, through the Fastly CDN module that Adobe installs on Pro Staging and Production and on Starter Production. There is no default.vcl to edit, and custom rules go into Fastly custom VCL snippets. The VCL rules in the rest of this article describe what Magento expects from its cache. Fastly runs its own configuration.

What the Magento VCL does with query strings, cookies and TTLs

Magento’s VCL builds the cache key from the URL plus the X-Magento-Vary cookie, so other cookies don’t split the cache. On 2.4.9 it sorts query parameters and strips a fixed list of marketing parameters. It stores only 200 and 404 responses that aren’t marked private, and everything else goes to Magento.

The generated VCL sets what counts as the same page. The rules below are read from the VCL Magento 2.4.9 generates, and several of them changed between releases.

Query strings: sorted, and marketing parameters stripped

The 2.4.9 VCL sorts query parameters first, so ?color=red&size=m and ?size=m&color=red share one entry. Sorting is new in 2.4.9. It then removes known tracking parameters: utm_ parameters, Google and Microsoft click IDs such as gclid and msclkid, fbclid, mc_ parameters and a few more. Lists differ by release: 2.4.8 added the Google and Microsoft click IDs, and Magento’s development branch already carries a much longer list. A parameter missing from your release’s list gives every click its own cache entry. Add it to both regex lines in vcl_recv and note the change for the next re-export. Filter parameters must stay, because they change the page. The removal pattern only checks that the URL holds a tracking parameter, then cuts every match, even inside a longer name: on 2.4.9 a link to ?country_of_origin=12&utm_source=newsletter reaches Magento as ?country_of_, so the shopper lands on the unfiltered page. If a filter or other parameter name ends in a listed name, such as origin or ie, anchor the pattern to ? or &.

Cookies: only X-Magento-Vary splits the cache

X-Magento-Vary is the cookie in which Magento records the shopper’s context, such as customer group, store and currency. The VCL hashes only that value out of the Cookie header, so analytics and consent cookies don’t create extra copies of a page. It removes Set-Cookie from cacheable responses, and since 2.4.7 it won’t store a page whose response sets X-Magento-Vary when the request didn’t send it. Custom code that adds values to the context multiplies the copies of every page. Passing requests on session cookies, as some tutorials advise, adds nothing, because the hash already ignores them.

TTLs, status codes and pages Varnish won’t store

The TTL comes from Magento’s s-maxage header, set by the admin field “TTL for public content”, 86400 seconds by default. Only 200 and 404 responses that aren’t marked private are stored. A response marked no-cache or no-store gets a two-minute marker, and requests in that window go straight to Magento. The VCL comment calls the marker hit-for-pass, while Varnish 8’s reference says beresp.uncacheable produces a hit-for-miss object, so expect these requests in cache_hitmiss rather than cache_hitpass. Browsers get no-store for HTML, so the browser never holds a stale page. Static and media files pass by default, so serve them from the web server or a CDN.

Grace mode, purges and ESI in the Magento VCL

Magento’s VCL keeps every page for three days past its TTL. While the backend passes its health check, Varnish serves an expired page for the admin’s grace period, 300 seconds by default, and fetches a fresh one. If the check fails, it keeps serving stale pages. A purge from Magento, sent as a ban by cache tag, removes pages outright.

Grace mode keeps expired pages for three days

The VCL keeps every object three days past its TTL. While the backend passes its health check, Varnish serves an expired copy for up to the admin’s grace period, 300 seconds by default, and refreshes it in the background. After that, the request waits for a fresh build. When the health check fails, Varnish keeps serving what it has, which keeps a store up through a short outage, as Adobe’s advanced Varnish page describes. A Grace header on hits shows which case applied: “none” for a copy within its TTL, “normal (healthy server)” or “unlimited (unhealthy server)”. A page removed by a purge is not served in grace.

Purges are bans by cache tag

Magento sends tags rather than URLs, so one product save can clear the product page, its categories and any block that shows it. Varnish turns each purge into a ban on X-Magento-Tags, which applies to every stored object with a matching tag. These are obj.* bans, so Varnish’s background ban lurker can clean them up. The next shopper gets a miss, unless a cache warmer requests the page first. Count bans in MAIN.bans: a number that climbs all day points to imports, cron jobs or mass saves.

ESI blocks are cached on their own

ESI stands for Edge Side Includes, a way for Varnish to assemble a page from separately cached pieces. With Varnish selected, a layout block with its own ttl, such as the default theme’s top menu, becomes an ESI include that points at page_cache/block/esi and is cached with its own TTL and tags. The admin field “Handles params size” caps how many layout handles the include passes, 100 by default, and Magento’s own comment advises 50–100. Watch MAIN.esi_errors.

How to measure and raise your Varnish hit rate

To measure your Varnish hit rate in Magento 2:

1. Read the X-Magento-Cache-Debug header: HIT, MISS or UNCACHEABLE.
2. Compare MAIN.cache_hit with MAIN.cache_miss in varnishstat.
3. Group requests by URL and result with varnishncsa.
4. Trace one slow URL with varnishlog.
5. Watch MAIN.n_lru_nuked for evictions and MAIN.bans for purges.

Varnish answers hits. Every miss and pass goes to Magento, so the hit rate sets how much of your traffic waits for PHP.

Read the cache headers

The VCL sets X-Magento-Cache-Debug on every response: HIT, MISS, or UNCACHEABLE on 2.4.7 and later. UNCACHEABLE means Magento told Varnish to skip the page. It’s there in production mode too, although Adobe’s verification page says to switch to developer mode to see the headers. Developer mode only adds X-Magento-Cache-Control and keeps Age. If the debug header is missing, the response didn’t pass through Magento’s VCL, so check that Varnish loaded the new file and that no proxy or CDN in front removes the header. If the header says HIT and the page is still slow, the wait is elsewhere: see why a Magento site gets slow.

Count hits and misses with varnishstat

varnishstat is Varnish’s live counter tool. The Varnish 8 counters that matter: cache_hit (which includes grace hits, counted separately in cache_hit_grace), cache_miss, cache_hitpass and cache_hitmiss for the “don’t cache” markers, s_pass for passes, n_lru_nuked for objects evicted to make room, and bans. A practical hit rate is hits divided by hits plus misses plus passes, measured over a busy day and per page type where you can. No published target fits every store, so measure your own.

Find the URLs that miss with varnishncsa and varnishlog

varnishncsa writes one line per request. Log ten minutes or a busy day with the handling value and URL path, then group the lines to see which page types miss or pass. varnishlog follows one URL through Varnish and its backend request. Then time the pages that miss, as you would when you audit your store page type by page type, because misses show up in field data as slow server response time.

Run on the Varnish server. Counters are totals since Varnish started.

# Hits, misses, passes, evictions and bans since Varnish started
varnishstat -1 | grep -E 'MAIN\.(cache_hit|cache_hit_grace|cache_miss|cache_hitpass|cache_hitmiss|s_pass|n_lru_nuked|bans) '

# Ten minutes of requests: how Varnish handled each URL path
timeout 600 varnishncsa -F '%{Varnish:handling}x %U' > /tmp/handling.txt
sort /tmp/handling.txt | uniq -c | sort -rn | head -30

# Follow one URL through Varnish and Magento
varnishlog -g request -q 'ReqURL ~ "^/women/tops"'

Fix what keeps the hit rate low

Match what the log shows to the change that fixes it.

1. Many pass or hitmiss lines on catalog pages: find what sends Cache-Control: private, no-cache or a block marked cacheable="false".
2. Misses on the same URLs again and again, with MAIN.bans climbing: move imports and mass saves off-peak, and stop flushing the cache on every deploy.
3. Misses with n_lru_nuked climbing: Varnish is evicting pages to make room, so give it more memory.
4. Many one-off URLs: strip the extra tracking parameters, and accept that layered navigation filters and rare searches miss more often.
5. 503 errors: raise the header limits and check the health check URL, as in the setup steps.

What still reaches PHP when Varnish is tuned

Even with a tuned VCL, Varnish passes every POST, cart, checkout and account request to Magento. It also misses the first request after each purge, rare filter and search URLs, and each customer group’s first view of a page. Those shoppers wait while Magento builds the page in PHP, so the build speed sets their response time. A miss also runs the database queries behind each block, covered in our Magento MySQL optimization guide. Server response on uncached pages is also where Magento trails most other platforms, as our fastest eCommerce platforms research shows.

A pass or a miss costs a full page build in PHP, and that build is the time those shoppers wait. Cache settings move requests between the two groups, and for the second group only the build speed counts.

Expedio, scandiweb’s software for the server-side page build, works on exactly those requests. It speeds up how Magento builds each page by applying Liquid, the open-source template language created at Shopify, and its core is open source. It runs on Magento 2 Open Source, Adobe Commerce and Commerce Cloud, with Luma, Hyvä or a custom theme and on any hosting, and it leaves the theme, design, data, admin, catalog, prices, checkout and orders as they are. Pages that reach Magento are built at least 2x faster, and the same server handles 3x the traffic before response times start to rise.

In a benchmark on one merchant’s Hyvä store, measured as server response time with no full page cache, category pages opened with all caches empty took a median of 57 ms instead of 181 ms. The method and caveats are in the Expedio benchmark.

Frequently asked questions about Magento 2 Varnish configuration

Which Varnish version should I use with Magento 2.4.9?

Use Varnish 8. Adobe’s system requirements list Varnish 8 for Magento 2.4.9 and 2.4.8-p5, and give a version for each older patch line. Magento’s VCL generator has no Varnish 8 template, so generate the Varnish 7 file with --export-version=7, then test it on staging before it goes to production.

How do I generate the Varnish VCL for Magento 2 from the command line?

Run bin/magento varnish:vcl:generate. It prints the VCL, or writes it to a file with --output-file. Set --export-version to 7 for Varnish 7 or 8, because the default is still 6, and pass the backend host and port, the grace period, and each IP allowed to purge with --access-list. Then replace /etc/varnish/default.vcl and restart Varnish.

Why does Varnish return 503 Backend Fetch Failed on Magento?

One common cause is response headers that are bigger than Varnish allows. Category pages carry a cache tag for each product in the X-Magento-Tags header, and Varnish’s default limit is 8 KB. Adobe suggests setting http_resp_hdr_len to your largest category’s product count times 21, for example 65536, and raising http_resp_size above it.

Why are Magento pages not being purged from Varnish?

Magento sends a PURGE request to every host in http_cache_hosts, and Varnish answers 405 unless the sender’s IP is in the VCL’s acl purge list. Set the hosts with bin/magento setup:config:set --http-cache-hosts, add each Magento server’s IP to acl purge, then send a test PURGE from each one: 200 means Varnish accepts it, 405 means the IP is missing. Magento logs “No cache server(s) could be purged” only when it can’t reach any host.

What is the difference between Varnish and Redis caches?

Varnish caches whole pages in front of the web server, so a cache hit never reaches Magento. Redis, or Valkey on Magento 2.4.9, holds Magento’s own cache data and sessions in memory, which speeds up the work Magento does when Varnish misses. Most production stores run both: Varnish for pages, Valkey or Redis for the rest.

Is Varnish used on Adobe Commerce Cloud?

No. On Adobe Commerce Cloud, full page caching uses Fastly, a Varnish-based CDN, instead of a Varnish server you run yourself. Adobe installs the Fastly CDN module for Magento 2 on Pro Staging and Production and on Starter Production. Custom caching rules go into Fastly custom VCL snippets rather than a default.vcl file.

Magento 2 Varnish configuration: what to check after every upgrade

A Magento 2 Varnish configuration is done when you can show three things: the VCL matches your Magento and Varnish versions, Magento’s purges reach every Varnish host, and you know your hit rate by page type. Check all three after every upgrade. Then make the requests Varnish sends on to Magento faster.

The version table, the health check path and the marketing parameter list are the three things that change most often between releases, so re-export the VCL after each upgrade and diff it against the one in production. Where the two differ, carry your own changes into the new file, and keep a Magento 2 Varnish check on the release checklist. For the layers around Varnish, from PHP to the browser, see how to speed up Magento layer by layer.

If you're moving to Varnish 8 for Magento 2.4.9, or your hit rate is lower than you expected, talk to our Magento team about a review of your VCL and purge setup.

The post Magento 2 Varnish Configuration: Setup, VCL Tuning, and Hit-Rate Fixes appeared first on scandiweb.