Acumatica and Shopify integration for stock and orders
Map Acumatica and Shopify stock, prices and orders before enabling a connector. Define record ownership, warehouse rules and sync exceptions.
- Published
- Last updated
Yes, Acumatica and Shopify integrate through Acumatica’s official commerce connector. An Acumatica Shopify integration can send catalogue and availability data to Shopify, import orders and send fulfilment information back. Assign ownership before the first sync so staff know which system to correct when records disagree.
Choose the connector and assign record ownership
Use the official Acumatica connector when your store needs Shopify orders processed in Acumatica. Acumatica’s marketplace lists technically validated versions 2026 R1, 2025 R2, 2025 R1 and 2024 R2. Its integration supports manual, scheduled and real-time synchronisation.
Acumatica’s product-edition table includes one Shopify or BigCommerce connector for one storefront in Retail Edition. It lists the Shopify connector as optional for several other editions. Additional connectors and storefronts require additional purchases. The Acumatica Cloud ERP app listing says installation is free, with Acumatica charges billed separately. Include the connector licence, implementation and ongoing support in the project quote.
The public app connection requires an internet-accessible Acumatica instance and the correct tenant. An authorised Shopify installer reviews the requested permissions, then authorises the connection to Acumatica. Enable Retail Commerce and Shopify Connector in Acumatica. Set up customer numbering, payment methods and the order type before importing orders.
Keep the public app route separate from custom development. Acumatica also documents a custom app connection. Shopify’s app setup instructions use the Dev Dashboard for new custom apps and require a developer to obtain API access tokens. Legacy instructions for copying a new token from Shopify admin do not describe that route. Keep credentials in the connector’s protected configuration, with access limited to its administrators.
Object direction and record ownership
This is a recommended ownership map for a retailer that maintains its catalogue in Acumatica. Configure each entity’s supported direction and primary system in Shopify Stores (BC201010). For bidirectional entities, the primary system decides which record takes precedence during a conflict.
| Record | Owner in this setup | Intended direction | Limit or setup decision |
|---|---|---|---|
| Items | Acumatica | Acumatica to Shopify | Export eligible stock and non-stock items. Keep accounting-only items outside the catalogue. |
| Variants | Acumatica | Acumatica to Shopify | Enable Matrix Items and map the template and its matrix items to the product’s options and variants. |
| Prices | Acumatica | Acumatica to Shopify | Separate the public item price from business price lists. Customer price classes need the supported business-to-business route. |
| Customers | Shopify for checkout details | Shopify to Acumatica | Decide whether to create individual customers or use a generic guest customer for imported orders. |
| Orders | Shopify at checkout, Acumatica for processing | Shopify to Acumatica | Map item identifiers, shipping methods and payments before importing. |
| Fulfilment | Acumatica | Acumatica to Shopify | Activate Shipment to transfer the warehouse’s shipment information. |
The Acumatica order synchronisation guide describes importing orders and payments, then processing shipments in Acumatica. A successful order import does not establish that payment mapping also succeeded. An unmapped payment can be filtered while the order exists.
Keep records that the route excludes out of your migration totals. Acumatica excludes the designated refund-amount item from ordinary non-stock item export. Its matrix-image documentation also excludes matrix-item images supplied through Media URLs links. Treat custom fields as separate mappings, with a test value in each receiving field.
Map sellable stock and prices
Map the quantity customers can buy to the locations that can fulfil their orders. Acumatica exports tracked availability through the Product Availability entity. Its quantity is expressed in the item’s sales unit of measure, with conversion from the base unit where needed.
In Shopify Stores, choose the availability calculation and warehouse scope. On Hand describes physical stock. Available and Available for Shipping use different availability calculations. Reservations and allocations can therefore make the sellable number lower than the shelf count. Review the item class’s availability rule before choosing a mode.
A fictional multi-location item
Suppose a retailer sells a navy towel under the stock-keeping unit (SKU) TOWEL-NAVY. Acumatica stores individual towels and sells them individually. The following figures illustrate the retailer’s intended calculation, not a measured connector result.
| Acumatica location | On hand | Reserved for other orders | Intended online quantity | Shopify location |
|---|---|---|---|---|
| Perth dispatch | 20 | 6 | 14 | Perth dispatch |
| Melbourne dispatch | 12 | 4 | 8 | Melbourne dispatch |
| Returns inspection | 3 | 0 | 0 | Excluded from online stock |
Use Specific Warehouses and map each eligible warehouse or warehouse location to its Shopify location. Exclude returns inspection until staff release the stock for sale. After a single-item availability sync, compare the intended 14 and 8 with Shopify’s location quantities. A total of 22 alone does not prove the location mapping works.
If the sales unit becomes a pack of two towels, convert the expected quantities to packs before comparing them. Acumatica’s availability guidance warns against changing the sales unit while unsynchronised orders still contain the item. Complete those orders’ sync and refresh availability after a unit change.
Give each size or colour its own stable identifier. A navy towel and a white towel must not resolve to the same stock record. For matrix items, also inspect the parent product and each variant’s options after export.
Separate public prices from customer prices
The public price and a negotiated customer price answer different questions. Acumatica’s Shopify price-list route exports customer price classes, subject to its supported filters. The documentation requires Shopify’s business-to-business functionality on Plus and the Acumatica Shopify B2B Integration feature.
A customer-specific Acumatica price does not automatically become an authenticated Shopify price. Decide which class maps to each business customer and test the resulting catalogue while signed in. The documented price-list filters include the sales unit and eligible currency, and exclude warehouse-specific prices.
Keep tax treatment beside the amount in your mapping sheet. Record whether the storefront displays tax-inclusive prices and compare the imported order’s tax and total with Shopify. Map tax codes through the connector’s tax settings. For multiple currencies, compare the order currency, store currency and Acumatica document currency before accepting totals.
Customer replies must use the same product variant, sales unit and customer context as checkout. A public catalogue amount cannot establish a private contract price. A stock total across warehouses cannot establish availability at the location fulfilling that order.
Test the order and exception cycle
Test one traceable purchase through payment and fulfilment, then run separate cancellation and return cases. Record the Shopify order identifier and the linked Acumatica order number. The following fictional sequence defines expected checks for your configured workflow.
- Place an order for three towels in a test store. In Shopify, confirm Paid and Unfulfilled. Import the order and mapped payment, then find the linked sales order and prepayment in Acumatica.
- Ship two towels in Acumatica using an order type that permits back orders. Confirm that the exported shipment covers two units. Shopify must show the remaining unit as unfulfilled, with the first shipment’s tracking attached to the shipped quantity.
- Ship the final towel. Compare the two shipment quantities with the original three-unit order. Confirm Shopify’s fulfilment status and Acumatica’s remaining order quantity independently.
- For a separate unshipped order, cancel in Shopify and process its synchronisation record. Inspect the linked Acumatica order before warehouse staff release it. Check the payment’s refund or authorisation state separately from cancellation.
- For a shipped order, issue a line-level refund in Shopify under the configured card or non-card refund workflow. Import the Refund entity. Compare the refund document and return quantities in Acumatica, then inspect the inventory receipt before releasing returned stock for sale.
Shopify’s cancellation instructions distinguish cancellation, refund timing and restocking. Acumatica’s refund guidance requires the original order to be synchronised before importing its refund. A money refund and a physical stock receipt need separate reconciliation.
Find the failed record before retrying
Acumatica’s Sync History (BC301000) links ERP and external identifiers. Prepared means the record is queued. Failed means processing has failed within the allowed attempts. Aborted means it exceeded that allowance. Filtered means the synchronisation rules excluded it.
| Symptom | Where staff investigate | Observable evidence | Safe next step |
|---|---|---|---|
| Permission failure | Shopify app access and Acumatica connection settings | An authorisation error when testing the connection or processing an entity | Repair access for the existing connection, then retry one affected record. |
| Duplicate processing | Acumatica Sync History and Sales Orders | One Shopify external order identifier appears against more than one ERP order | Pause imports for the affected route and reconcile orders and payments before replaying anything. |
| Stale inventory | Acumatica Product Availability history and Shopify inventory | The last processed item predates a stock movement, or Shopify has the wrong location quantity | Check the entity, warehouse mapping and scheduled processing, then sync one known item. |
| Rejected mapping | Acumatica Process Data and Entities (BC202000) | A failed record identifies an invalid field value or unresolved item | Correct the source value or mapping, then reprocess that record and inspect its destination. |
A real-time notification can prepare a record without processing it. Acumatica distinguishes Prepare from Prepare & Process, and scheduled preparation from scheduled processing. Check both stages when a change reaches the queue but never reaches Shopify.
Enable recurring sync after the test order’s quantities, payments and linked identifiers agree. Assign someone to review failed and aborted records so the first exception has an owner.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.