Skip to content
Adobe Commerce | Commerce Cloud

B2B company accounts, shared catalogues, customer segments, Page Builder and Commerce Cloud. The licensed half of the platform, built properly rather than worked around.

How engagements work

In one paragraph

How is Adobe Commerce development different from Magento Open Source?

The architecture is the same and the surface is not. Adobe Commerce adds company accounts, shared catalogues, requisition lists and multi-level purchase approvals for B2B, customer segments and targeted rules, Page Builder, content staging and preview, and on the Cloud tier a managed Fastly, New Relic and deployment pipeline. Development work therefore splits in two: building correctly inside those modules instead of rebuilding them, and configuring the infrastructure the licence already provides. Most of the waste on Adobe Commerce projects is custom code that duplicates a feature the business is already paying for.

What this is

A business on Adobe Commerce is paying a significant annual licence, and the first useful question on any engagement is which of the paid features it is actually using. The answer is frequently "about half", with custom modules sitting alongside the native ones doing a worse version of the same job.

The second question is whether the B2B module fits the way the business really buys. Company accounts, shared catalogues and approval rules cover a great deal of it natively. Where they do not, the right extension point exists and the wrong one is writing a parallel workflow next to it. Knowing which is which is most of the value here.

On the Cloud tier there is a third layer: Fastly, the deployment pipeline, the three-environment model and New Relic are part of what was bought. Treating them as managed hosting and nothing else leaves performance and release safety on the table.

What this page is not

This page is about the licensed platform. If you are on Magento Open Source, most of the work is the same engineering without the B2B, staging and segment modules, and that has its own page.

What usually brings this in

  • We pay for Adobe Commerce and use it like Open Source.

    A six-figure licence funding features that are switched off, while custom modules do the same work less reliably.

  • The B2B module almost fits, so someone built around it.

    Two approval systems in one codebase, and nobody is certain which one a given order went through.

  • Page Builder was disabled because the theme fought it.

    Every campaign page is a developer ticket, and the content team has stopped planning them.

  • Cloud deploys are slow and occasionally frightening.

    Releases get batched up, which makes each one larger and the next one more frightening still.

What gets built

B2B built on the native module
Company accounts, company users and roles, shared catalogues, requisition lists and multi-level approval rules configured and extended through the module rather than beside it. Five-level approval chains covering orders, quotes and vendor management are on the record.
Customer segments and targeted rules
Segments driven by real attributes and order history, wired into cart price rules, targeted content and related product rules, so merchandising stops needing a deployment.
Page Builder that the theme supports
Content types the theme actually renders, with the layout constraints built in. The test is whether a marketer can ship a landing page without a developer and without breaking the grid.
Staging, preview and scheduled updates
Campaign content, pricing and rules scheduled ahead and previewed before they run, which is the feature most often left unconfigured and the one that removes the most midnight deployments.
Commerce Cloud configuration
Fastly VCL and cache policy, the three-environment branching model, deployment hooks and New Relic alerting, treated as part of the product rather than as someone else is hosting.
Licence audit before any custom build
What the platform already does, what is genuinely missing, and what should be deleted because a native feature covers it. This is routinely the cheapest deliverable of an engagement.

Technologies

Platform
  • Adobe Commerce
  • Magento 2
  • Magento B2B
  • Page Builder
  • MSI
Cloud
  • Commerce Cloud
  • Fastly
  • New Relic
  • ECE Tools
Language & data
  • PHP
  • MySQL
  • GraphQL
  • REST APIs
Performance
  • Varnish
  • Redis
  • Elasticsearch
  • RabbitMQ

How delivery runs

  1. Scope, in writing

    What the work is, and what it explicitly is not. The second half is the one that protects both of us, and it is written before anything is quoted.

  2. Architecture before code

    The data model, the integration points and the failure modes, agreed on paper. Most of the expensive mistakes in commerce are made here and discovered six weeks later.

  3. Build in reviewable slices

    Work lands in increments you can see running, not in one drop at the end. You find out early if something is going the wrong way, which is when it is still cheap.

  4. Test against the real thing

    Production-shaped data, production-shaped traffic. A checkout that works on twelve test products tells you nothing about one carrying a hundred thousand.

  5. Deploy, document, hand over

    Release process written down, documentation aimed at your team rather than at me, and a defined window afterwards where fixes are mine.

Questions

Is Adobe Commerce worth the licence over Magento Open Source?
It is when you need the B2B module, customer segments, staging or the Cloud tooling, and it is not when you need none of them. That is a short assessment rather than a long one: list what you would otherwise build, price it honestly, and compare. Businesses that answer "we would build the approval workflow and the segment engine" nearly always come out ahead on the licence.
Can you work on an Adobe Commerce build somebody else delivered?
Yes, and that is most of this work. It begins by reading the code and the admin configuration together, because the usual finding is a custom module shadowing a native feature, and that is visible only when you look at both.
Do you work on Commerce Cloud or self-hosted Adobe Commerce?
Both. Cloud changes the deployment and caching work rather than the application work: Fastly instead of your own Varnish, the ECE pipeline instead of your own CI. The architecture, the B2B model and the catalogue work are identical.
We are on Magento Open Source and considering Adobe Commerce. Is that a migration?
It is an upgrade path rather than a replatform, and the data comes across. The real work is adopting the modules you are now paying for, which means retiring the custom code that was standing in for them. Budget for that rather than for the move.

Describe what is in front of you and you get a written scope and a figure, usually within a few days of a short call. No charge for either.

All services