Development for Adobe Commerce

Stores kept supported,
release after release

We upgrade, extend and support Adobe Commerce and Magento Open Source stores, planning each upgrade from Adobe’s published dates and building custom features so each upgrade has less to change.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

When each upgrade looks bigger than the last

Many businesses run a store built on Magento 2 some years ago, often with dozens of modules, the add-ons that bring in features beyond the platform’s own, some bought and some written for it. Adobe supports each Adobe Commerce release line for a set time, and once that support ends, sends no more fixes for it.

An upgrade often brings newer versions of PHP, the database and the search engine, and every module that runs inside the store has to be checked against them, so the upgrade tends to be put off and the gap grows. Meanwhile PHP and the rest have support dates of their own, which Adobe’s support doesn’t cover.

What we build

Adobe Commerce and Magento Open Source stores kept on supported releases, with every change tried on a copy of the store before it reaches your customers.

  • Upgrades to a supported release

    Each upgrade planned from Adobe’s published dates, with PHP, the database and search moved to supported versions too, and tried on a copy of the store first.

  • Moves from Magento 1

    A Magento 1 store rebuilt on Magento 2, with its products, customers and orders brought across, as Adobe’s own migration guide sets out.

  • Custom features built to last

    Features your store needs, built beside the store where Adobe’s tools allow, or as modules on the extension points Adobe supports, never as changes to Adobe’s own code.

  • Modules reviewed and trimmed

    Every module checked: which are still maintained, which do the same job twice, and which hold back the next upgrade.

  • B2B features

    Company accounts, quotes, and catalogs and prices for each business, with Adobe Commerce’s B2B features. Magento Open Source can price products for groups of customers.

  • Connections to ERP, stock and finance

    The store kept in step with your ERP, stock and finance systems, with one system in charge of each detail, so stock levels, orders and invoices agree.

  • A store that stays quick

    The causes of slow pages and slow admin screens found first, from caching to search and indexing, then fixed where they matter most.

  • Security patches applied

    Adobe’s security patches applied as they’re released, each tried on a copy of the store first, with PHP and the rest kept on supported versions.

  • Moves to another platform

    When another platform would serve you better, products, customers and orders moved across, with every old address redirected to its new page.

Inside the store, or beside it

Custom features for Adobe Commerce and Magento Open Source have long been written as modules: code that runs inside the store, in its own PHP. Adobe’s documentation notes that code written this way has to stay compatible with each upgrade, with the server’s PHP version and with the other services the store relies on.

Adobe Commerce now also offers out-of-process extensibility, Adobe’s name for features that run as separate apps beside the store and talk to it through its APIs, events and webhooks, so they avoid those compatibility issues. Adobe recommends it where possible, and describes using both, keeping inside the store what needs to be there, such as new parts of its pages or changes to how it handles customers, orders and products.

Adobe’s tools for code beside the store are for Adobe Commerce: the documentation for its events, for one, says Magento Open Source isn’t supported. A Magento Open Source store can keep the same separation through a service of its own that talks to the store through its APIs, which is how we build there. On Adobe Commerce as a Cloud Service, Adobe describes code beside the store as the only way to extend it.

Current releaseNext release

Trade prices

A module, inside the store

Checked again

Orders to your ERP

An app, beside the store

Kept apart

Code inside the store moves with every upgrade. Code beside it doesn’t have to.

{{ bsStatus }}

Every part of the store has a date

Adobe supports each Adobe Commerce release for three years from its release, with quality fixes and security patches throughout, and has given some releases a year more. But a store also runs on PHP, a database, a search engine, a cache and a message queue, each with its own end of support, and Adobe’s policy says it doesn’t fix them when they reach it.

So a store is fully supported only while every part of it is, and each upgrade is planned from all of those dates, not one. Adobe’s lifecycle policy covers Adobe Commerce; it doesn’t apply to Magento Open Source.

For stores on Adobe Commerce on Cloud, Adobe has set dates of its own: from June 1, 2027, it says it will stop maintaining Cloud environments that run unsupported versions, and may suspend their traffic, and it sets dates for the software those environments depend on. These dates apply to Adobe Commerce on Cloud only.

Start with a review of your store

The review covers its release and patch level, and where its release stands on Adobe’s support dates; its PHP, database, search, cache and queue versions, and where each stands; its modules, which are maintained, which hold back the next upgrade, and which could move beside the store; any changes made to Adobe’s own code; its connections to other systems; its speed, for shoppers and in the admin; and how it’s deployed, patched and tested.

Moving from Magento 1, or to another platform? We build the catalog, the checkout and one connection and release them early, so customers can buy while the rest is built.

Either way, you get a written review and a proposal for the first step.

Questions worth asking

  1. Which release should we be on?

    One in Adobe’s standard support, with PHP, the database and search on supported versions too. As Adobe’s pages stand in October 2026, 2.4.9 is the newest release line, with standard support until May 31, 2029, and 2.4.8’s runs until May 31, 2028. The review checks which suits your modules.

  2. What happens when our release’s support ends?

    Adobe stops sending quality fixes and security patches for it, as its lifecycle policy sets out, and some releases get a last period of security fixes only. For stores on Adobe Commerce on Cloud, Adobe says it will stop maintaining environments on unsupported versions from June 1, 2027, and may suspend their traffic. A store elsewhere keeps running, but security issues found after that aren’t fixed by Adobe.

  3. We’re still on Magento 1. What are our options?

    Two: a move to Magento 2, which is a new build, with your products, customers and orders brought across as Adobe’s migration guide sets out, or a move to another platform. Either way, the review starts with what the store does today and what it has to keep.

  4. Should we upgrade, or move to another platform?

    It depends on the store: what it sells, how it sells to businesses, and the modules and connections it relies on. Most stores are best served by an established platform, and if another would serve you better, we’ll tell you and recommend the simplest option that fits.

    E-commerce

    Stores on Shopify:Shopify Development

    Stores on WooCommerce:Development for WooCommerce

  5. Should we move to Adobe Commerce as a Cloud Service?

    Adobe recommends it to stores on Adobe Commerce on Cloud: Adobe keeps its infrastructure, patches and upgrades up to date. Custom features then run beside the store, which Adobe describes as the only way to extend it, so a store with many modules moves them out first. Whether it suits you depends on those modules, and the review sets out what would have to change.

  6. Can you move our custom code out of the store?

    Often, where Adobe’s tools allow. Features that work with the store’s data from outside, such as sending orders to an ERP, can run beside it: on App Builder for Adobe Commerce, or as a service of our own that uses the store’s APIs for Magento Open Source. Code that changes the store’s own pages, or how it handles customers, orders and products, stays inside as a module.

  7. Do you work with Magento Open Source as well as Adobe Commerce?

    Yes, both. They come from Adobe on the same release lines, and Adobe’s security updates cover both. Adobe Commerce adds features of its own, among them its B2B features and Adobe’s tools for code beside the store, and Adobe’s lifecycle policy, with its support periods, covers Adobe Commerce only.

  8. Can you take over our existing store?

    Yes. We work on a copy of the store first, read its modules and theme and note the release and versions it runs, and the review says what to change, in what order. Nothing changes on the live store until you agree.

  9. Our store is slow. Can you make it faster?

    Usually, once the cause is found. We look at how the store performs for shoppers and for your team in the admin, find what slows each down, from caching and indexing to modules and the server, and fix what matters most, measuring each fix.

    Performance & Optimization

  10. Can it connect to our ERP and other systems?

    Yes. We settle which system has the final word on each detail, from stock levels to invoices, then keep the store in step with your ERP, stock and finance systems.

    Systems & API Integration

  11. How do you keep it secure?

    By applying Adobe’s security patches as they’re released, each tried on a copy of the store first, and keeping PHP, the database and the rest on supported versions, which Adobe’s patches don’t cover. Our security work adds threat modeling, code review and checks in every build.

    Application Security

  12. Who hosts it?

    It depends on the edition and how you run it. Adobe Commerce runs on your own servers, on Adobe Commerce on Cloud, or as Adobe Commerce as a Cloud Service, which Adobe runs for you; Magento Open Source runs on hosting you choose. Hosting and the platform beneath your software are a service of their own.

    Cloud, DevOps & Security

  13. What does it cost?

    It depends on the store: its release, its modules and connections, and whether it’s being upgraded, extended or moved. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.

    Pricing

  14. Can your developers work inside our own team?

    Yes. We introduce developers for Adobe Commerce and Magento Open Source matched to your store within 48 hours of your request, all working in your time zone, and you decide who joins.

    Hire Magento Developers

Adobe, Adobe Commerce, and Magento are either registered trademarks or trademarks of Adobe in the United States and/or other countries. Webair isn’t affiliated with or endorsed by Adobe.

Let’s build it better

Tell us where your store stands and where it needs to go next. A short call is enough to agree what to look at first.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}