Is the Acumatica and BigCommerce integration a connector, an ISV product or a build?
A first-party connector, built by Acumatica, and one of only three native commerce connectors Acumatica lists alongside Amazon and Shopify. Acumatica’s BigCommerce page states the B2B scope plainly: "Connect BigCommerce B2B Edition with Acumatica to easily sync company accounts, customer details, and complex orders."
The architecture is the same entity-and-schedule model as the Shopify connector, which is useful to know if you are comparing the two. You switch entities on individually, each has a Prepare and Process step, and several of them are commonly scheduled overnight. What differs between the two pairings is not the plumbing, it is which platform concepts the entities have to land in.
A live area to check against your own release: Acumatica’s 2026 R1 notes list new BigCommerce B2B Edition import work, and a 2025 R1 BigCommerce Payments integration update was announced in the Acumatica community. Both mean the answers below can move between releases in a way the Shopify side has been more stable about.
Checked against: Acumatica’s integration with BigCommerce, read 20 August 2026, Acumatica eCommerce integrations and commerce connectors, read 20 August 2026, Community 33640: updated BigCommerce Payments integration for 2025 R1 and newer
What actually syncs between Acumatica and BigCommerce B2B Edition, mechanic by mechanic?
The same eight mechanics as the Shopify page, in the same order, so you can hold the two side by side. Direction and trigger are stated for each because they carry the risk.
Two rows here have no equivalent on the Shopify side. BigCommerce genuinely has inventory locations, which is better than most people expect, and BigCommerce B2B Edition genuinely has native quoting, which the connector has no documented entity for.
| Criterion | What actually crosses | Direction | Trigger, and the catch |
|---|---|---|---|
| Products and variants | Stock items, non-stock items and template items sync as BigCommerce products, with attributes mapped to BigCommerce fields. | Acumatica to BigCommerce. | Entity sync on a schedule. Template items are reported not respecting BigCommerce’s default availability setting, and product availability is not an attribute-mappable field, so the community workaround for non-stock availability is a Generic Inquiry exported to Excel and imported by hand, daily. |
| PricingThat single sentence is the most misread fact in this pairing. Groups are not prices. | The stock item Default Price, and Acumatica price lists through the Price List entity. Customer price classes travel as group membership, without their prices. | Acumatica to BigCommerce. | Prepare and Process on the Price List entity, manually or on an automation schedule, usually overnight. Acumatica’s community is explicit that the Customer Price Class entity "will update groups of customers in BigCommerce store (Customers>Customer Groups), but not the prices". |
| InventoryChanging a warehouse to location mapping after items are exported needs a deliberate remediation. | Available quantity per Acumatica warehouse. BigCommerce does support inventory locations, four to eight depending on plan. | Acumatica to BigCommerce. | On the availability entity schedule. BigCommerce Stencil storefront queries return stock from the default location only unless you request an aggregated model, and Acumatica’s own moderator answer for letting a customer shop one assigned warehouse is still a customization keyed on something like ship-to state. |
| Customers and companiesDeleting that first admin severs the Acumatica customer to BigCommerce company link. Tell the customer’s administrator before they tidy up. | Acumatica customers become BigCommerce B2B Edition companies, and contacts become company users, with one contact promoted to first admin. | Both ways, and that is the problem. | On the customer entity schedule. On 23R1 the sync used the main contact rather than the primary contact as first admin, sent the second phone number instead of the first, let BigCommerce values overwrite Acumatica edits to the main contact email and primary contact name, missed edits to any other contact, and created duplicates readily. |
| Orders | BigCommerce orders import as Acumatica sales orders. Acumatica states the sync automatically creates separate shipments and tracking numbers for each package. | BigCommerce to Acumatica, with fulfilment returning. | On order creation and status change. A quote negotiated inside BigCommerce B2B Edition has no documented Acumatica entity, so a quote only becomes visible to Acumatica once the buyer converts it into an order. |
| Credit and terms | Nothing enforceable at checkout from the connector. BigCommerce B2B Edition has its own payment-terms and purchase-order behaviour that the connector does not drive. | BigCommerce to Acumatica, as values on the order. | At order import. If your credit rule is "this account is over its limit, stop the order", that decision has to be made by something you build against Acumatica, not by an entity you switch on. |
| Tax | The tax BigCommerce charged arrives with the order, and Acumatica recalculates it by default. | BigCommerce to Acumatica. | At import. The same 2023 R1 remedy applies as on Shopify: Disable Automatic Tax Calculation on the Order Types form plus Tax Synchronization on the store record, at the cost of those invoices no longer going to Avalara or TaxJar. |
| Returns and refundsSaying we cannot confirm it is more useful to you than rounding the vendor sentence up. | Acumatica claims a working path: "Process returns and refunds in BigCommerce, and watch those updates reflect instantly in Acumatica’s financials." | BigCommerce to Acumatica. | At refund. We have not found a community thread that tests this on the B2B Edition path, so this row is a vendor claim rather than a verified finding, and it is the first thing we would put in a sandbox test. |
Checked against: Community 11823: syncing sales prices from worksheets to BigCommerce, price class vs price list, Community 24685: BigCommerce B2B customer syncing issues on 23R1, Community 5378: multi-warehouse setup with BigCommerce, Community 22691: tracking non-stock items in BigCommerce, BigCommerce developer docs: inventory locations, read 20 August 2026, Acumatica’s integration with BigCommerce, returns and shipments claims
What is not covered, and what do you have to build?
BigCommerce B2B Edition carries more native B2B behaviour than Shopify B2B does, and the connector does not reach all of it. That gap is the honest summary of this pairing: the platform can do more than the integration knows about.
The unit of measure item on this list is the one that quietly puts a wrong number on a page. Older connector builds exported the price and availability held against the base unit rather than the sales unit, so a case-priced item showed the each price. Acumatica added sales-unit price and product sync in 22R2, and a user on that release in February 2023 still could not find the setting, with the request for documentation in that thread unanswered.
Customer-specific effective prices. The connector carries price lists and customer group membership; the negotiated number Acumatica would use at order entry is not among them.
BigCommerce B2B Edition quotes as an Acumatica object. A negotiated quote lives in BigCommerce until the buyer converts it.
Credit limit enforcement at checkout, and hold or dunning behaviour driven from Acumatica’s customer balance.
Per-customer warehouse entitlement. Acumatica’s own moderator points at a customization keyed on ship-to state.
Product availability as a mappable attribute, which is why the non-stock workaround is a daily manual import.
Unit of measure conversion in older builds. Confirm on your release whether the sales unit price and availability settings are actually in effect.
Punchout is a way for a buyer to shop on a supplier’s website from inside their own procurement system. The buyer clicks out, builds a cart, and the cart is returned to their system as a requisition for approval.. Neither BigCommerce B2B Edition nor the connector ships cXML or OCI punchout, so a procurement-driven customer means a separate provider.
Checked against: Community 6697: BigCommerce sales price sync with wrong unit of measure, Community 22691: product availability is not attribute-mappable
When does BigCommerce B2B Edition beat Shopify B2B on Acumatica?
Both are native Acumatica connectors on the same architecture, so the choice comes down to what the platform models rather than what the connector moves. Four differences do the deciding, and none of them is about page speed or theme quality.
BigCommerce has real inventory locations, four to eight by plan, where Shopify locations behave differently for B2B availability. BigCommerce B2B Edition ships native quoting and buyer roles, so a Quote to order is the process where a buyer asks for a price, a person or a system prepares a quote, and the accepted quote becomes an order. In much of B2B it is the normal way to buy, not an exception. business gets more out of the box. Shopify B2B expresses per-customer pricing as catalogues, which is a cleaner mapping from an Acumatica price list than BigCommerce’s customer groups and price lists. And the BigCommerce customer sync is the one with six documented surprises attached to it, which is a real implementation cost.
If your buying process is quote-heavy and multi-branch, BigCommerce B2B Edition is usually the stronger starting point. If your pricing is tiered and your buying process ends at a checkout, Shopify B2B gets you there faster.
Checked against: BigCommerce developer docs: inventory locations by plan, read 20 August 2026, Community 24685: the six customer sync behaviours
Who should not pair BigCommerce B2B Edition with Acumatica?
Four situations where this pairing will cost more than it returns, stated as disqualifiers rather than as caveats.
The fourth one catches distributors specifically. If availability accuracy is the thing your customers judge you on, understand exactly which BigCommerce location the storefront is reading before you build anything on top of it.
Your negotiated prices live in Sales Price Worksheets and change weekly. Customer groups will carry the tier and not the number, and a nightly price list run is the best freshness on offer.
You need a buyer to see only their assigned branch’s stock. That is a customization on this pairing, quoted per requirement, not a setting.
Your team cannot absorb the customer sync behaviours, particularly a first admin that severs the company link if the customer deletes it.
Your catalogue is mostly non-stock or made to order, where availability is not an attribute-mappable field and the documented workaround is a daily manual import.
Checked against: Community 11823: Customer Price Class syncs groups, not prices, Community 5378: per-customer warehouse availability is a customization, Community 22691: non-stock availability workaround
The wider picture
This page answers one narrow question. Acro Commerce covers the strategy around it.
Common questions
- Does the Acumatica BigCommerce connector sync customer-specific prices?
- It syncs price lists and customer group membership, not the effective price Acumatica calculates at order entry. Acumatica’s community answer on this is direct: the Customer Price Class entity "will update groups of customers in BigCommerce store (Customers>Customer Groups), but not the prices", and prices move only when you prepare and process the Price List entity, normally on an overnight automation schedule. Sales Price Worksheet prices do not make that trip.
- Does BigCommerce support multiple warehouses from Acumatica?
- BigCommerce does have inventory locations, four to eight depending on plan, which is more than most people assume. The catch is on the storefront: Stencil queries return stock from the default location only unless you request an aggregated model, and restricting a customer to one assigned warehouse is a customization, according to Acumatica’s own moderator, typically keyed on something like ship-to state.
- Which Acumatica contact becomes the BigCommerce company admin?
- On Acumatica 23R1 the sync used the main contact rather than the primary contact, which is rarely what an Acumatica user expects. That first admin is also the record that ties the Acumatica customer to the BigCommerce company, so deleting it severs the link. Acumatica’s 2026 R1 notes list new BigCommerce B2B Edition import work, so re-test this behaviour on your own release before you design around it.
- Do BigCommerce B2B Edition quotes reach Acumatica?
- Not as quotes. There is no documented connector entity for a B2B Edition quote, so a negotiated quote lives in BigCommerce until the buyer converts it into an order, and Acumatica sees the order. If your sales team needs to work quotes inside Acumatica, that is an integration you commission separately.
- Will Acumatica recalculate the tax BigCommerce charged?
- By default, yes. The remedy is the same as on Shopify: since Acumatica 2023 R1 you can tick Disable Automatic Tax Calculation on the Order Types form and enable Tax Synchronization on the store record so the imported figure stands. Ticking it stops Acumatica sending those invoices to external tax providers such as Avalara or TaxJar, which is deliberate, and it does not work with inclusive taxes, gross entry mode or partial invoices.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.