What we do
Tools
Industries
Department
How we workLet's talk →
Home/Magento
Magento Open Source and Adobe Commerce

How to Integrate With Magento: Extensions, Middleware or the API

It's 4pm and someone is exporting today's Magento orders to a spreadsheet so the ERP has them by morning. There are three ways to retire that job: an extension from the Commerce Marketplace, an integration platform between the two systems, or a build on Magento's own REST API. Which one fits depends on the system on the other side and how far your store has drifted from a standard setup.

Where Magento stops

A self-hosted store was never going to talk to your accounting, ERP and CRM on its own.

Stuck on Magento? Let's solve it →

Three ways to integrate with Magento, matched to the store

If your store looks like this Lean toward Watch for
A standard catalog and an accounting or ERP system that already has a Marketplace extension An extension: install, map fields, run Extensions are written for the common setup. Confirm it supports your exact 2.4.x line and that its vendor ships updates after security releases.
Several systems to connect, and someone in-house who can maintain flows An integration platform with a Magento connector Pricing is usually per flow or per volume, and custom attributes, store views and B2B data often need custom steps anyway.
A legacy ERP, a warehouse system or a pricing rule nothing else understands A custom build on the REST API Someone has to own it after launch: tokens, retries, and a test run after every Magento upgrade.
Heavy imports: thousands of prices or stock levels in one go The async bulk API It depends on the message queue consumers running. Without them, requests are accepted and nothing happens.

Setting up API access for a Magento integration

  1. 1

    Create the integration in the Admin

    System Extensions Integrations Add New Integration

    Name it after the system it connects to and confirm with your admin password. On the API tab, grant only the resources it needs, such as Sales and Catalog for an ERP order sync, rather than All.

  2. 2

    Activate it and keep all four values

    Save, then click Activate and Allow. Magento shows a consumer key, consumer secret, access token and access token secret. Put them in a secret store, not a shared doc.

    Watch for: changing the integration's resources later means reauthorizing it, which issues new tokens. Update the other system when you do.

  3. 3

    Decide how the token gets sent

    Stores Configuration Services OAuth Consumer Settings

    From 2.4.4 on, an integration's access token can't be used as a plain bearer token by default, because it never expires. Either sign each request with OAuth 1.0a using all four values, or set Allow OAuth Access Tokens to be used as standalone Bearer tokens to Yes. Adobe advises against the second.

  4. 4

    Make a first REST call

    Request GET /rest/default/V1/orders with a searchCriteria filter, for example orders updated since your last run, plus a pageSize and currentPage. Here default is the store view code, so use your own if the store runs several.

  5. 5

    Send big jobs through async bulk

    For large imports, POST an array of items to /rest/default/async/bulk/V1/products. Magento replies straight away with a bulk_uuid, and GET /rest/V1/bulk/{bulkUuid}/status tells you which items worked.

    Watch for: the async.operations.all consumer has to be running, from cron or bin/magento queue:consumers:start, or the requests wait in the queue indefinitely.

A legacy ERP that hears about orders when they happen

Home furnishings retailer: a Magento store with a legacy ERP behind it

Before

Orders were exported from Magento each afternoon and keyed into the ERP, and stock went back to the store by file.

Overnight sales regularly sold furniture that wasn't there.

After

Orders now reach the ERP when they're placed, and stock flows back to Magento without a file.

Nobody spends the morning cancelling oversold orders anymore.

Questions to settle before a Magento integration goes live

  • Which system owns stock?

    If both Magento and the ERP can change quantities, decide which one wins. With Multi-Source Inventory, also decide which source the ERP figure belongs to.

  • Which store views and currencies are involved?

    Prices, names and tax can differ by store view, and REST calls are scoped by the store code in the URL. A sync written for default misses the rest.

  • What happens to an order the ERP rejects?

    A missing SKU or customer shouldn't hold up the next hundred orders. It should land in a list someone actually reads.

  • Does B2B data need to reach the CRM?

    On Adobe Commerce with B2B turned on, company accounts, negotiated pricing and quote requests live in the store. If sales works from a CRM, that data has to travel there.

  • How will the other system hear about changes?

    Adobe I/O Events for Commerce needs Adobe Commerce 2.4.4 or later and doesn't support Magento Open Source. On Open Source, changes come from a custom module, a webhook extension, or polling by updated_at.

  • Who runs a test order after each patch?

    Security releases can change behavior an integration relies on. One order pushed end to end on staging catches most of it.

Let's talk

Magento orders in your books the same day

n-frames builds Magento integrations on the REST and bulk APIs: orders into QuickBooks, NetSuite or a legacy ERP as they're placed, stock and prices back to the store, and wholesale accounts into the CRM your sales team uses. We work on top of the store you already run, and your Magento developer keeps the theme and checkout.

End the afternoon export →

Questions people ask

What is Magento?

Magento is e-commerce software: a storefront, catalog and checkout that a business installs and runs on servers it controls, rather than a hosted service like Shopify. It began as an independent open-source project, passed through eBay and a standalone company, and is now owned by Adobe.

Is Magento free?

Magento Open Source, which is what most people mean by Magento, is free to download and run. You still pay for hosting, developer time and paid extensions. The paid edition once called Magento Commerce is now sold by Adobe as Adobe Commerce.

Is Magento the same product as Adobe Commerce?

They share a core codebase. Magento Open Source is the free edition you host yourself. Adobe Commerce is Adobe's licensed edition, with B2B and merchandising features, vendor support and optional Adobe-managed cloud hosting. For integration work the REST API is largely the same, but a few things, such as B2B data and Adobe I/O Events, exist only on Adobe Commerce.

Does Magento have an app marketplace?

Yes, the Adobe Commerce Marketplace, where third-party developers sell extensions for payments, shipping, marketing, accounting and ERP connections. It covers a lot of common needs. A particular ERP, a custom pricing rule or a system nobody has built an extension for usually needs custom integration work instead.

Can Magento integrate with other systems?

Yes, through its REST and GraphQL APIs, which every extension and integration runs on underneath. GraphQL is mostly built for storefronts, such as catalog, cart and checkout in a headless build. Back-office jobs like order export, stock updates and bulk price changes usually run on REST and the async bulk endpoints.

Should a new Magento integration use an admin token or an integration?

An integration. Admin tokens from /V1/integration/admin/token expire after four hours by default and are tied to one admin user, which suits scripts you run by hand. A registered integration has its own scoped permissions and can be revoked without touching anyone's login.

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.