Acumatica ERP connects to Adobe Commerce through a certified connector that keeps stock items, pricing, customers, orders, shipments, and returns in sync between the two systems. Acumatica ships native connectors for Amazon, Shopify, and BigCommerce, while Magento and Adobe Commerce integrate through Kensium’s connector on the Adobe Commerce Marketplace.
For a B2B merchant running Acumatica as the system of record, that connector is what turns a storefront into a real sales channel rather than a second place to rekey orders. This article covers exactly which data moves, in which direction, and how to scope an Acumatica to Adobe Commerce project without discovering the hard parts in production.
Why Acumatica and Adobe Commerce Get Paired
Acumatica is a cloud ERP with strong distribution, manufacturing, and B2B roots. It owns inventory, pricing, financials, and order fulfillment. Adobe Commerce owns the buying experience: catalog, search, self-service accounts, and checkout. When a distributor or manufacturer runs both, the question is never whether to integrate them, it is where the boundary sits and which system wins on each field.
The default answer for most B2B operations: Acumatica is the source of truth for inventory, pricing, and customers, and Adobe Commerce is the source of truth for the online catalog presentation and the buyer’s session. Orders originate in Adobe Commerce, then flow to Acumatica for fulfillment and invoicing. This mirrors the broader ERP, CRM, and POS integration patterns that hold up as B2B volume grows.
How Acumatica Connects to Adobe Commerce
There is an important nuance buyers miss. On its own commerce connectors page, Acumatica lists native connectors for Amazon, Shopify, and BigCommerce. Adobe Commerce and Magento are supported, but through a partner-built connector rather than a first-party one.
The established option is Kensium’s Acumatica connector for Adobe Commerce, published on the Adobe Commerce Marketplace. Kensium is Acumatica’s official commerce partner and one of the longest-serving ISVs in that ecosystem, and the Adobe connector is the reference implementation most agencies build around. Under the hood, integration uses Acumatica’s contract-based REST API, which exposes ERP entities as versioned endpoints so the mapping survives ERP upgrades.
You have three realistic paths:
| Approach | What it is | Best for | Tradeoff |
|---|---|---|---|
| Certified connector (Kensium) | Prebuilt, configurable connector with queuing and logging | Most B2B merchants who want a supported path | License cost; you still configure and test every entity |
| Custom via contract-based API | Direct integration your team builds on Acumatica’s REST API | Unusual data models or workflows the connector cannot express | You own every endpoint, retry, and upgrade |
| iPaaS middleware | A platform (such as an integration service) brokers the sync | Multi-system landscapes where Acumatica is one of several | Another vendor and monthly cost in the path |
For most merchants the certified connector is the starting point, with custom work layered on only where the standard mapping falls short.
What Actually Syncs, and Which Way
An Acumatica to Adobe Commerce integration is a set of entity mappings, each with a direction and a trigger. The table below reflects a standard B2B configuration.
| Entity | Direction | Notes |
|---|---|---|
| Stock items and attributes | Acumatica to Adobe Commerce | Item classes and attributes drive catalog structure |
| Inventory / availability | Acumatica to Adobe Commerce | Near real time so the storefront does not oversell |
| Pricing and price worksheets | Acumatica to Adobe Commerce | Includes customer-specific and tiered pricing |
| Sales categories | Acumatica to Adobe Commerce | Keeps merchandising aligned with the ERP catalog |
| Customers and contacts | Both directions | New web registrations flow back to Acumatica |
| Orders | Adobe Commerce to Acumatica | Web orders become Acumatica sales orders |
| Shipments and tracking | Acumatica to Adobe Commerce | Powers accurate order status in My Account |
| Invoices and payments | Acumatica to Adobe Commerce | Surfaces billing history to the buyer |
| Returns (RMA) | Both directions | Keeps credits and restocks consistent |
Most of this runs in real time, with a batch or on-demand re-sync available for historical corrections or when one system was offline. A good connector includes a queuing mechanism so that if Adobe Commerce or Acumatica is briefly unreachable, documents hold in the queue and replay rather than disappearing. Detailed logging of each success and failure is the difference between a five-minute fix and a day of forensic work.
The B2B Fields That Make or Break the Project
Generic ERP integrations sync products and orders. B2B integrations have to sync relationships. This is where an Acumatica to Adobe Commerce project earns its keep, and where thin connectors fall down.
For a company running Adobe Commerce B2B, the connector should map:
- Companies and company hierarchies, so a buying organization in Adobe Commerce matches its Acumatica customer record.
- Contacts and addresses, including multiple ship-to locations per company.
- Customer-specific pricing and price worksheets, so the price a logged-in buyer sees matches their negotiated Acumatica terms.
- Credit limits and payment terms, so a buyer on payment-on-account cannot exceed the limit Acumatica enforces.
- Salespersons, so orders and commissions attribute correctly.
- Quotes, so a negotiable quote in Adobe Commerce can become an Acumatica sales order after approval.
These fields are what separate a B2B storefront from a catalog with a login. They also align closely with how Adobe Commerce models B2B customer hierarchies for distributors, which is why the mapping between the two systems needs care rather than a default template.
Scoping the Project So It Ships
The most common way an ERP integration goes wrong is scope by assumption. Treat these as required discovery, not optional.
- Decide the system of record per field. Write it down. Inventory, price, and customer master usually live in Acumatica; catalog content and SEO usually live in Adobe Commerce. Ambiguity here causes data to bounce between systems.
- Inventory sync frequency and safety stock. Real-time availability prevents overselling, but you also need rules for backorders and multi-warehouse allocation.
- Pricing model. Confirm whether price worksheets, customer classes, and promotions all need to flow, and how discounts stack.
- Order status mapping. Map every Acumatica order and shipment state to a storefront status a buyer will understand.
- Tax and payment ownership. Decide whether tax calculation and payment capture happen in Adobe Commerce, Acumatica, or a dedicated service.
- Error handling and alerts. Define what happens when a sync fails and who gets notified, before go-live rather than after the first chargeback or oversell.
A phased rollout beats a big-bang cutover. Start with catalog, inventory, and orders, prove the loop, then layer in B2B pricing, quotes, and returns.
The Gotchas That Slow These Projects Down
Even with a certified connector, a handful of issues recur across Acumatica to Adobe Commerce builds. Knowing them in advance turns a stalled project into a predictable one.
- Attribute and item-class mismatches. Acumatica item classes and attributes rarely map one-to-one to Adobe Commerce attribute sets. Reconciling them is catalog data work, and skipping it produces products that sync but display incorrectly.
- Multi-warehouse inventory. A single available-quantity number hides the reality of stock split across locations. Decide early whether the storefront shows total availability, a primary warehouse, or a calculated figure that respects allocation and safety stock.
- Unit-of-measure conversions. Selling in eaches while stocking in cases is common in distribution, and a mismatch between Acumatica and Adobe Commerce quantities corrupts both inventory and pricing.
- Tax and payment ownership. When both systems can calculate tax, you get two answers. Pick one authority and disable the other.
- Historical data on first sync. The initial load of years of customers, orders, and SKUs is heavier than the ongoing real-time flow, so plan the cutover load and validate a sample before trusting the whole set.
None of these are exotic. They are the difference between a connector that technically works and an integration a B2B operations team actually trusts on a Monday morning.
Where Hyva Fits
Acumatica integration is a back-office data flow, so it is largely independent of the storefront theme. A Hyva theme development project and an Acumatica integration proceed on separate tracks and meet in only a few places: displaying live inventory, showing customer-specific pricing to a logged-in buyer, and rendering order and shipment status in the account area. Because Hyva keeps the frontend fast and the ERP keeps the data authoritative, the two reinforce each other rather than compete.
The storefront’s job is to render Acumatica’s truth quickly and clearly. A buyer should see accurate stock, their negotiated price, and a live order status without waiting on a slow page or a stale cache.
Choosing an Implementation Partner
Acumatica and Adobe Commerce are both deep platforms, and the connector sits exactly where their models disagree. Look for a team that has shipped both sides: Adobe Commerce development plus real ERP integration experience, not one or the other. Ask how they handle credit limits, multi-warehouse inventory, and quote-to-order, because those are the questions that expose whether a partner has done this before.
Bemeir builds the Adobe Commerce and Hyva side of these integrations and works with a broad set of technology partners across ERP, fulfillment, and payments. You can read more about Bemeir and how the team operates as an extension of a merchant’s staff at bemeir.com. For merchants weighing platforms beyond Adobe Commerce, Bemeir also delivers on Shopify and Shopify Plus, BigCommerce, and Shopware, each of which Acumatica connects to through its own connector path.
FAQ
Does Acumatica have a native Adobe Commerce connector?
Not a first-party one. Acumatica ships native connectors for Amazon, Shopify, and BigCommerce. Adobe Commerce and Magento integrate through a certified partner connector, most commonly Kensium’s connector on the Adobe Commerce Marketplace, built on Acumatica’s contract-based REST API.
What data syncs between Acumatica and Adobe Commerce?
Stock items and attributes, inventory availability, pricing including customer-specific and tiered prices, sales categories, customers and contacts, orders, shipments and tracking, invoices, and returns. B2B configurations add companies, addresses, credit limits, salespersons, and quotes.
Is the sync real time or batch?
Most of it is near real time so inventory and orders stay current, with a batch or on-demand re-sync for historical corrections or after one system was offline. A queuing mechanism holds documents during an outage and replays them once connectivity returns.
Which system should own inventory and pricing?
For most B2B merchants Acumatica is the system of record for inventory, pricing, and the customer master, while Adobe Commerce owns catalog presentation and the buyer session. Deciding this per field, in writing, before development starts prevents data from bouncing between the two.
How does the integration handle B2B credit limits and negotiated pricing?
A well-configured connector maps Acumatica credit limits, payment terms, price worksheets, and customer-specific pricing to Adobe Commerce B2B, so a logged-in buyer sees their negotiated price and cannot exceed the credit limit the ERP enforces. This mapping is the part that most needs testing.
Will integrating Acumatica affect our Hyva storefront?
Only where data surfaces to the buyer: live inventory, customer-specific pricing, and order status. Acumatica integration is a back-office flow, so a Hyva frontend and an ERP integration run on separate tracks and only intersect in the account and product display.
