Is the Acumatica and Shopify integration a connector, an ISV product or a build?
It is a first-party connector, built and shipped by Acumatica rather than by Shopify or by a third party. Acumatica’s commerce connectors page names exactly three platforms with native connectors, Amazon, Shopify and BigCommerce, and describes the Shopify one as connecting "Shopify Plus and B2B on Shopify with Acumatica". Everything else on that page, including Adobe Commerce and WooCommerce, is described as reachable "through supported integrations", which is a different thing and a different budget.
There are two Shopify connectors in the Acumatica product line and the difference costs money. The plain Shopify Connector handles the storefront. The Shopify and Shopify POS Connector adds point of sale and is gated by the Retail Commerce edition licence, and the option renders in the interface without that licence while silently not working, which is how it turns into a budget conversation three weeks into a project.
The mechanical point that decides everything below: the A native connector is integration software published by the ERP or platform vendor themselves, configured rather than built. Acumatica ships native connectors for Shopify and BigCommerce. moves data through named entities that you switch on one at a time, each with its own schedule. Nothing here is real time by default, and no entity asks Acumatica to compute an answer on demand. It copies stored values on a timer.
Checked against: Acumatica eCommerce integrations and commerce connectors, read 20 August 2026, Acumatica for Shopify Connector product page, Community 23200: Shopify and Shopify POS Connector vs Shopify Connector
What actually syncs between Acumatica and Shopify B2B, mechanic by mechanic?
Eight mechanics, one row each, with the direction and the trigger stated because those two facts decide more project risk than the capability itself. A field that syncs nightly in one direction is a different product from a field that syncs on save in both.
Read the trigger column first. Most of the disappointment on an Acumatica and Shopify B2B project comes from a mechanic that does sync, on a schedule slower than the business assumed.
| Criterion | What actually crosses | Direction | Trigger, and the catch |
|---|---|---|---|
| Products and variantsCovered in depth on the matrix items page, including the 25R1 duplicate option value error. | Stock items and non-stock items become Shopify products. Acumatica template items become Shopify products with variants. | Acumatica to Shopify. | Entity sync on a schedule, or a manual Prepare and Process run. Shopify caps a product at three options, so a template item with four attribute dimensions fails outright with "Shopify supports only up to 3 product options", and template sync re-sorts your Shopify variant order on every run. |
| PricingOne stock item on the list that has not synced yet fails the whole list with "Sync ID is not found for the record". | The stock item Default Price, through the base sales price entity, and Acumatica price lists, through the Price List entity. The effective sales price from a released Sales Price Worksheet does not travel. | Acumatica to Shopify. | The Price List entity is prepared and processed manually or on an automation schedule, commonly overnight. Asked directly whether the current effective sales price could sync instead of the Default Price, Acumatica’s community answer was "No. Only Default Price is supported." |
| Inventory | Available quantity per Acumatica warehouse, mapped to Shopify locations. | Acumatica to Shopify. | On the availability entity schedule. UNASSIGNED commitments can make the connector publish a quantity that is not the one Acumatica shows on screen, and changing a warehouse to location mapping after items are already exported needs a deliberate remediation rather than a re-sync. |
| Customers and companiesMap your Acumatica ship-to locations to Shopify company locations on paper before anyone configures anything. | Acumatica customers and contacts become Shopify customers, and Shopify B2B companies and company locations where the B2B module is switched on. | Both ways, with Acumatica intended as the master record. | On the customer entity schedule. The connector is reported duplicating B2B contacts as separate Shopify customers, and company location handling is the thinnest-documented part of the whole integration. |
| Orders | Shopify orders import as Acumatica sales orders with lines, shipping and payment records. Shipments and tracking flow back. | Shopify to Acumatica, with fulfilment status returning. | On order creation and on status change. Once an Acumatica sales order has a shipment or a linked purchase order attached it can no longer be modified, which is what blocks storefront-side edits and exchanges. |
| Credit and termsThis row is a finance problem before it is a technical one. Get your controller to read it. | Nothing enforceable. A Shopify B2B payment term is recorded on the Shopify order as data. | Shopify to Acumatica, as a value on the order. | At order import. Shopify B2B has no native A credit limit is the amount a customer may owe at any one time. Buying on account, often on thirty-day terms, is standard in B2B and the limit is enforced by the ERP. enforcement and no dunning, and users report Shopify Plus "Payment due later, Net 30" orders landing in Acumatica as prepayments, fully paid. |
| Tax | The tax Shopify charged at checkout arrives with the order, and Acumatica recalculates it by default. | Shopify to Acumatica. | At import. Since 2023 R1 a Disable Automatic Tax Calculation checkbox on the Order Types form, paired with Tax Synchronization on the store record, lets the Shopify figure stand. Ticking it stops those invoices going to Avalara or TaxJar, by design. |
| Returns and refunds | Shopify refunds and cancellations reach Acumatica, with three named defects. | Shopify to Acumatica. | At refund or cancellation. A Shopify refund is reported voiding the Acumatica payment rather than refunding it, cancelling in Acumatica can leave the Shopify payment authorized, and multi-location returns post to the wrong store. |
Checked against: Community 17608: "Only Default Price is supported", Community 22606: Shopify price list sync, Sync ID is not found for the record, Community 18873: template item sync error, Shopify supports only up to 3 product options, Community 6261: warehouse to location mapping changed after export, Community 32415: Acumatica and Shopify integration issues, order modification, BOPIS and returns, Community 12996: preventing Acumatica recalculating imported tax, Shopify B2B limitations, LiquidLab, read 20 August 2026
What is not covered by the Acumatica Shopify connector at all?
These are the items with no entity, no setting and no workaround inside the connector. Each one is a line in a statement of work. If your integrator has not priced them, they have not read your requirements.
The first item on the list is the expensive one. Getting a customer’s negotiated price onto a Shopify B2B product page means restructuring Acumatica prices as price lists and accepting last night’s freshness, or calling Acumatica at page render through Middleware is a layer of software that sits between the ERP and the storefront, translating and enforcing rules that neither system holds on its own. It can be a hosted integration platform or a custom service. you own and pay for.
The effective sales price for a customer, calculated on demand. The connector copies stored prices; it never asks Acumatica what this account pays for this item today.
Credit limit enforcement at checkout, and any dunning or hold behaviour. Shopify B2B carries no native mechanism for either.
A required purchase order number field at checkout, and multi-level purchase approval routing. Both need custom development on Shopify.
Per-customer warehouse entitlement, meaning a buyer who may only see and buy from the branch assigned to them. Acumatica’s own community answer to this is still a customization.
Item cost. It does not sync to Shopify, which matters if you planned to report margin on the storefront side.
Shopify BOPIS statuses. "Ready for pick up" and "Marked as picked up" do not transfer to Acumatica.
Orders with no ship-to address, which cannot be imported without a workaround.
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. in either cXML or OCI. Neither Shopify B2B nor the connector provides it, and it is normally a separate provider.
Checked against: Community 5378: multi-warehouse setup and per-customer availability, Community 32415: item cost, BOPIS statuses, multi-location returns, Shopify B2B limitations, LiquidLab, read 20 August 2026
Which Shopify plan and which Acumatica edition does this pairing need?
Two licence questions decide the real cost of an Acumatica and Shopify B2B project, and both are answerable before you talk to anyone.
On the Shopify side, the number that matters is catalogues. Shopify documents that Basic, Grow and Advanced allow "up to 3 active catalogs across all your B2B markets", while Shopify Plus allows an unlimited number, with a maximum of 25 catalogues assigned to any one company location and 10,000 catalogues per store. Since a catalogue is how an Acumatica price list becomes a customer-visible price, three price tiers is the line where a pricing requirement turns into a Plus requirement.
On the Acumatica side, the Retail Commerce edition licence gates the Shopify and Shopify POS Connector. If you do not sell in a physical location you may not need it, and a VAR who quotes it without asking has not scoped your project. One more licence detail worth raising early: a Shopify store activated in a test tenant may count toward your licensed store count, which surprises teams who spin up a sandbox.
Checked against: Shopify Help Centre: customizing B2B pricing using catalogs, read 20 August 2026, Community 23200: POS connector licence gate
Who should not pair Shopify B2B with Acumatica?
Shopify B2B on Acumatica is a good pairing for a distributor with a manageable number of price tiers, a catalogue that fits inside three product options, and a buying process that ends at a checkout. Five situations where it is the wrong answer and you will find out expensively.
None of these are Shopify failing at what it is for. They are requirements that sit outside what a catalogue-and-price-list model can express, and no connector configuration changes that.
Most of your revenue runs on negotiated per-account prices maintained through Sales Price Worksheets, and those prices change more often than a nightly schedule can carry.
Your products routinely carry four or more attribute dimensions, so the Shopify three-option ceiling forces you to split one Acumatica template item into several Shopify products.
Credit limits and payment terms have to be enforced at checkout rather than reconciled afterwards, and your finance team will not accept an order that lands as fully paid when it is Net 30.
Buyers must be restricted to the branch or warehouse assigned to their account, because you cannot promise stock you hold three provinces away.
Your largest customer requires punchout, and their procurement system, not your storefront, has to own the requisition.
Checked against: Community 18873: Shopify supports only up to 3 product options, Community 17608: "Only Default Price is supported", Shopify B2B limitations, LiquidLab, read 20 August 2026
How do you prove this in your own tenant in an afternoon?
Do this before you sign, with your own data. A demo tenant almost never contains a released Sales Price Worksheet, a four-attribute template item or a Net 30 company, which is exactly why the demo goes so well.
Pick an item one of your top ten accounts buys at a negotiated price. Compare the Default Price on the item to the effective price Acumatica shows for that customer today. If they match, choose a different item.
Look at that product in Shopify signed in as that company. Whichever number appears is the answer for your release, not the one on any datasheet.
Find your widest template item and count the attribute dimensions. Four or more means you are splitting products before launch, not after.
Place a test order on Shopify B2B with a Net 30 payment term, then open the resulting Acumatica sales order and read the payment status.
Change a stock quantity in a non-default warehouse and time how long it takes to appear on the storefront. That number is your real inventory freshness, whatever the schedule says.
The wider picture
This page answers one narrow question. Acro Commerce covers the strategy around it.
Common questions
- Does the Acumatica Shopify connector support Shopify B2B companies and company locations?
- Yes, the connector syncs customers into Shopify B2B companies and locations when the B2B module is switched on, and Acumatica’s own page describes connecting "Shopify Plus and B2B on Shopify". Two behaviours need planning: the connector is reported duplicating B2B contacts as separate Shopify customers, and company location handling is the least documented area of the integration. Map your Acumatica ship-to locations to Shopify company locations before configuration rather than during it.
- Can Acumatica send customer-specific prices to Shopify B2B?
- It can send price lists, which become Shopify B2B catalogues, and that is how most teams get per-customer pricing onto the storefront. It cannot send the effective sales price Acumatica calculates at order entry. Asked directly about syncing the current effective sales price rather than the Default Price, Acumatica’s community answer was "No. Only Default Price is supported", which strands anything set through a Sales Price Worksheet.
- Is the integration real time?
- No, and treating it as real time is the most common planning error on this pairing. The connector syncs through named entities, each switched on individually and each running on its own schedule, with Prepare and Process steps that are often set to run overnight. Stock and orders can be scheduled frequently; price lists in practice refresh nightly on most implementations.
- Do we need Shopify Plus, or will Advanced do?
- Count your price tiers. Shopify allows up to three active catalogues across all B2B markets on Basic, Grow and Advanced, and an unlimited number on Plus, with 25 catalogues per company location and 10,000 per store. Since an Acumatica price list reaches buyers as a catalogue, a fourth pricing tier is what moves you to Plus, not the transaction volume.
- What does the connector do about tax that Shopify already charged?
- By default Acumatica recalculates it, which is why a dedicated Acumatica community how-to exists. Since 2023 R1 you can tick Disable Automatic Tax Calculation on the Order Types form and enable Tax Synchronization on the store record, and the imported figure then stands. The trade is explicit: those invoices stop going to Avalara or TaxJar, and the setting does not work with inclusive taxes, gross entry mode or partial invoices.
- Can we edit a Shopify order after it reaches Acumatica?
- Only in a narrow window. An Acumatica sales order can be modified while it is Open or On Hold with no shipment and no linked purchase order attached. Once a shipment exists the order is locked, which blocks the exchange and partial-return flows a storefront usually wants. Design your returns process around a credit memo rather than an order edit.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.