Acumatica is the ERP we are happiest to see on a discovery call. Its contract-based REST API is the friendliest integration surface in mid-market ERP, the data model is coherent, and the company’s growth means we meet it constantly at manufacturers and distributors who outgrew QuickBooks or fled a legacy system. If the integration API were the whole story, Acumatica ecommerce projects would be a formality.
They are not a formality – because the API was never where ERP integration projects go wrong. Here is where the real work lives when we connect Acumatica to Shopware or Adobe Commerce.
The good news first: the API
Acumatica exposes a versioned, contract-based REST API: you define (or extend) an endpoint contract, and the integration codes against that contract rather than against screens or tables. Generic Inquiries can be exposed as OData feeds for efficient reads. Webhooks and push notifications cover event-driven flows. In practice this means the plumbing phase of an Acumatica integration is measured in days, and upgrades rarely break a well-built contract.
Native connector, or custom integration?
Acumatica ships native connectors for selected commerce platforms, and unlike most ERP vendors’ connectors, they are respectable. Our honest rule:
- The native connector is the right answer when you sell stocked items at list or simple customer pricing, on a platform the connector supports, with straightforward fulfillment. Take the win; spend the budget elsewhere.
- Custom integration is the right answer when distribution reality applies: matrix or contract pricing with quantity breaks, multi-warehouse availability rules, kitting and BOM items, B2B portals with credit and AR visibility, or a storefront (like Shopware) outside the connector list. Forcing a connector past its design leads to the workaround treadmill – the same failure mode we describe across every ERP in our ecommerce ERP integration guide.
Where the effort actually goes
- Pricing fidelity. Acumatica’s sales price worksheets, customer price classes, and discount sequences express real B2B pricing well. The storefront must resolve prices the way Acumatica does – same precedence, same effective dates – or your accounts will find the differences for you.
- Warehouse and availability logic. Multi-warehouse quantities, allocations, and what “available” should mean per channel. The number you display is a business decision the integration enforces, not a field it copies.
- Consumption-aware sync design. Acumatica licenses by resource consumption, not seats. A well-batched integration is invisible in your sizing; a chatty one is not. This is unique to Acumatica in our bench and worth designing for explicitly.
- Document flow into financials. Orders, shipments, invoices, and payments need to land with the right numbering sequences, branches, and GL treatment – the ID-chain discipline finance can audit is the same one we apply everywhere.
The portal-first option
Because customer pricing, credit, and order history read so cleanly through the API, Acumatica is one of the best backbones for a logged-in B2B ordering portal – frequently the right first phase before any public storefront. The full argument and rollout plan is in our customer portal playbook (written for P21 shops, but the sequencing logic is ERP-agnostic), and the build options are covered in B2B customer portal development.
Who we are
Web Solutions NYC has built B2B commerce since 2007: 50+ implementations, senior-only US engineers, and an ERP bench spanning Acumatica, NetSuite, Microsoft Dynamics, SAP, Epicor P21, and Sage. We are a Shopware Platinum Partner (the first Shopware agency in the US) and an official Adobe Commerce partner – the platform recommendation follows your requirements, not our inventory.
Frequently asked questions
Yes, cleanly. Acumatica’s contract-based REST API is among the friendliest in mid-market ERP, and both Adobe Commerce and Shopware integrate with it well. Acumatica also ships native connectors for some platforms; whether the native connector or a custom integration is right depends on how far your pricing, workflows, and catalog stray from standard.
When your model is close to standard: stocked items, list or simple customer pricing, single warehouse or simple availability, and the platform the connector targets. That is a real and legitimate answer for some merchants. The connector runs out where distribution reality begins – complex customer-specific pricing, multi-warehouse logic, kitting, or a storefront platform outside the connector’s support list.
Acumatica licenses by resource consumption rather than per user, which is great for putting your whole team in the ERP – and it means a storefront integration is a real consumer of your commercial arrangement. A chatty, unbatched integration is not just poor engineering; it can show up in your Acumatica sizing. Design the sync cycles deliberately and the issue never comes up.
Against an existing storefront, typically 6-12 weeks: the API makes the plumbing fast, and the calendar goes to pricing fidelity, warehouse and availability logic, and testing with real data. A full B2B storefront plus integration typically runs 4-6 months for a mid-market distributor or manufacturer.
Yes. Customer-specific pricing, credit and terms, and order history all read well through the API, which makes Acumatica a good backbone for a logged-in ordering portal – often the highest-ROI first phase before a public storefront. The same portal architecture we build for other ERPs applies directly.
On Acumatica and planning a storefront or portal? Bring your pricing setup and warehouse structure. We will tell you honestly whether the native connector covers you – and exactly what the custom build involves if it does not. Let’s talk.