What we do
Tools
Industries
Department
How we workLet's talk →
Home/Adobe Commerce/Adobe Commerce Integration
Adobe Commerce

Adobe Commerce Integration: Deciding Where the ERP Code Runs Before It's Written

The ERP project has a budget, and the first technical question is where the code will live. On Adobe Commerce there are four answers: an extension from the Commerce Marketplace, a custom PHP module inside the store, an integration platform with its own Commerce connector, or an App Builder app that runs outside the store and reacts to its events. Each ties you to a different upgrade story, and Adobe's SaaS edition only accepts the outside kind.

Four homes for an Adobe Commerce integration

Your situation Where the integration runs What it commits you to
A common ERP, CRM or tax tool, and a Marketplace extension already exists for it An extension from the Adobe Commerce Marketplace, installed in the store The vendor's release schedule. Extensions run in process, so each Commerce upgrade means retesting them and sometimes waiting for a new version.
Business rules no extension models, and a team already running custom modules A custom PHP module: plugins, observers and service classes inside Commerce It's deployed with the store and tied to its version, so it gets retested on every upgrade. Not allowed on the SaaS edition.
Several systems to link, and someone in-house who looks after flows An integration platform calling Commerce's REST API from outside The platform's subscription, and how much custom logic its flow builder will let you write.
Adobe Commerce 2.4.4 or later, or a planned move to Adobe Commerce as a Cloud Service An App Builder app: serverless actions on Adobe I/O Runtime, triggered by Adobe I/O Events Built and deployed apart from Commerce. It's the only kind of extension the SaaS edition takes.

In process or out of process on Adobe Commerce

Inside the store

A PHP module

  • Runs in Commerce's own process, with full access to its service classes.
  • Can change behavior anywhere, from price calculation to the order save itself.
  • Ships with the store's code and is retested whenever Commerce is upgraded.
  • Not an option on Adobe Commerce as a Cloud Service.
Beside the store

An App Builder app

  • Commerce sends an event, such as an order being placed, through Adobe I/O Events. The app picks it up and fetches the details over REST or GraphQL.
  • For I/O Events, the store has to be on Adobe Commerce 2.4.4 or newer.
  • When Commerce has to wait for an answer, such as a credit check before an order saves, Adobe's webhooks call out synchronously, and the reply can change the data or stop the action.
  • Deployed on its own, so a Commerce upgrade rarely means touching it.

For a new ERP or CRM link, out of process is the safer default now. It keeps a slow back-office system away from checkout and is already in the shape the SaaS edition needs.

Before the Adobe Commerce integration is scoped

  • Which system owns each kind of record?

    Orders start in Commerce. Prices, stock and customer terms often belong to the ERP. Name one owner per record type, or the two systems will keep overwriting each other.

  • Does anything need an answer before the order is saved?

    A credit limit, a live stock figure or a tax result from another system needs a synchronous call, through Adobe's webhooks or a module. Everything else can wait for an event.

  • Will a frontend or staff tool read from several systems at once?

    Only then is API Mesh worth adding. It joins Commerce, the ERP and, say, a PIM into one GraphQL endpoint, so that tool makes a single call.

  • Are B2B features part of the sync?

    Company accounts, shared catalogs and negotiated quotes have their own APIs, and not all of them are on REST. The Magento B2B page lists which ones an integration can reach.

  • How many websites and store views will it write to?

    A multi-store install with B2B pricing tiers is where a generic extension's field mapping tends to run out. Prices and names written at the wrong scope also show up as odd overrides later.

Orders out, prices and stock back, on Adobe tooling

n-frames builds Adobe Commerce integrations for the ERP, CRM and older back-office systems the Marketplace doesn't serve. Where the edition and version allow, they're App Builder apps: an order event that posts the sale to the ERP, stock and price changes written back through the REST API at the right scope, and anything the ERP rejects sent to a person with its reason attached. Where the store needs logic inside checkout, it's a module instead.

The record-by-record mapping, such as configurable products, bundles and tax, is the same as on Open Source and is laid out on Magento ERP integration. Credentials and store scope for the REST side are on the Magento API page.

Adobe Commerce integration, from the back-office side

Does Adobe Commerce have an API?

Yes, two main ones. REST covers back-office work such as orders, products, customers and stock, and GraphQL serves storefronts and headless frontends. Self-hosted installs still document SOAP for older integrations. On Adobe Commerce as a Cloud Service, calls authenticate through Adobe IMS rather than Commerce's own tokens.

What's the difference between Adobe Commerce and Magento Open Source?

For integration work, it's mostly the extra tooling. Adobe Commerce adds the B2B module, Adobe hosting and support, and Adobe I/O Events and webhooks for App Builder apps. Magento Open Source is the free, self-hosted core with the same REST and GraphQL foundations, so event-driven links there rely on a Marketplace extension or a custom module.

Can you connect Adobe Commerce to a legacy ERP with no modern API?

In most cases it can be done. If the ERP can drop export files, read a staging table or take a flat-file import, a small service between the two turns those into Commerce REST calls, and turns Commerce events into files the ERP can read. n-frames builds that layer, with a log of every record that didn't make it across.

Adobe Commerce works well for us, but our ERP still isn't connected. Is it worth fixing now?

It is when staff retype orders, stock or prices between the two every day. Each retyped order is a chance for a wrong price or a missed shipment, and the hours add up. If the ERP only needs a weekly summary, a scheduled export may be all it takes.

Should a new Adobe Commerce integration be built on App Builder?

On 2.4.4 or later, or with a move to the SaaS edition planned, it's the sensible default: the code runs on Adobe I/O Runtime, reacts to Commerce events and isn't redeployed with the store. Logic that has to change a checkout result can use Adobe's synchronous webhooks, or stay as a module on a self-hosted or cloud infrastructure install.

Let's talk

An Adobe Commerce ERP link that's ready for the SaaS edition

n-frames writes the integration between Adobe Commerce and your ERP, CRM or legacy system, out of process wherever it can be, so an upgrade or a move to Adobe Commerce as a Cloud Service doesn't mean starting over.

ERP orders without the export →

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.