+1 480 485 7373
Microsoft Teams
What travels in each direction
Catalog out
Item numbers, weights, vendor data and new-product flags leave Business Central. Rich content, images and layered navigation attributes stay mastered in Adobe Commerce or a PIM.
Stock out
Available stock per Business Central location feeds the matching inventory source. So salable quantity shows what the warehouse can truly ship.
Prices out
Base, customer group and B2B shared catalog prices come from Business Central price lists. So the website and the phone team quote the same figure.
Orders and buyers in
Orders, company accounts, addresses and payment references arrive as sales orders. Shipments, invoices and tracking go back to update the store.
Mapping the Magento store hierarchy to one ERP
Adobe Commerce organizes a site as websites, stores and store views. A website can carry its own currency, customer base and prices, while store views usually handle language and presentation. Business Central has no equivalent structure, so the integration has to translate it.
The usual pattern treats each website as a sales channel in Business Central. A dimension on the order tags it, so you can report revenue by brand or region. Sometimes two websites belong to separate legal entities. Then each posts into its own company, and the integration must route orders by website code first.
Currency deserves an early decision. When a website prices in euros or Canadian dollars, send orders in that currency. Let the ERP handle exchange rates and revaluation. Converting in the store loses the original amount.
Adobe Commerce and Business Central record map
Traps particular to Adobe Commerce
- ✓Salable quantity is not on-hand. The store holds stock for unshipped orders, so pushing raw BC stock can count it twice
- ✓Indexers and full-page cache can delay a price or stock change, even after the API call works
- ✓Extensions that rewrite checkout or add custom order attributes change the payload the integration receives
- ✓B2B negotiable quotes can move the price after Business Central priced the order. Agree which system approves the final figure
- ✓A new Adobe Commerce release can deprecate API behavior; put integration tests in every upgrade plan
- ✓Large catalogs sent one product per call will throttle; use the asynchronous bulk endpoints for price and stock waves
Choosing between an app, a platform and a custom build
AppSource connector app
Connector apps on AppSource from several vendors cover Magento and Adobe Commerce basics. They work well for one website with standard product types and no B2B module.
- ✓Fast to stand up
- ✓Limited room for multi-website routing
- ✓Check how it treats configurable products
Integration platform (iPaaS)
A platform with connectors for both sides handles queueing, retries and mapping in one console. That suits high order volume and extra systems such as a PIM or a 3PL.
- ✓Strong error handling
- ✓Visual mapping your team can maintain
- ✓Another subscription and another vendor
Custom service or Adobe Commerce module
A custom build makes sense when B2B quoting, custom product types or multi-entity routing go beyond any packaged mapping. It may split between a Business Central extension and a store module.
- ✓Fits unusual flows exactly
- ✓Needs developers on both platforms
- ✓The test suite is your responsibility
Proving the integration before it carries live orders
- 1
Mirror the environments
Point a staging store at a Business Central sandbox company. Load it with a recent copy of items and customers.
- 2
Test by website and product type
Run orders for every website, product type and payment method in use. Add an on-account B2B order if that module is active.
- 3
Load test the stock push
Send a full-catalog inventory update and time how long the storefront takes to show it, reindexing included.
- 4
Review the queue every morning
After go-live, check failed messages daily. Give an owner to anything stuck on a mapping error, such as a SKU that exists in one system only.
Adobe Commerce integration questions
Is this the same as a Magento integration?
Yes, largely. Adobe acquired Magento and sells the commercial edition as Adobe Commerce, while Magento Open Source remains the free edition. Both share the same core data model and web APIs, so the integration design is mostly the same. B2B features such as company accounts and shared catalogs belong to the commercial edition. Most of the extra mapping work sits there.
Can Business Central handle several Adobe Commerce websites?
Yes, provided the routing is designed up front. In a Business Central Adobe Commerce integration, each website can post into one company with a channel dimension. Separate legal entities get separate companies. The integration reads the website code on each order and routes it. Pricing and stock per website then come from the price lists and locations assigned to that channel.
Where should product content be managed?
Keep marketing content in Adobe Commerce or a dedicated PIM, and keep commercial data in Business Central. Descriptions, images, attribute sets for layered navigation and SEO fields are storefront concerns. Cost, price, weight, vendor and stock belong to the ERP. Splitting ownership this way stops an ERP push from overwriting merchandising work.
More Business Central Adobe Commerce integration questions
How are B2B credit limits handled?
Business Central should hold the credit limit and the balance, and the storefront should read them. Adobe Commerce company credit can then show buyers their available credit when they pay on account. If the store keeps a separate limit of its own, the two figures drift. Then the store approves orders that finance would have stopped. A scheduled or event-driven balance update keeps them aligned.
We run Magento 2 Open Source. Do we need to upgrade first?
Not necessarily. The integration works against the Open Source APIs too, as long as your version is still supported and patched. If a replatform or upgrade is already planned, building against the target version once saves rework. We look at your version and extensions during scoping and recommend the order of work.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.