How are refunds posted?

Under the treatment finance agrees during scoping — typically a credit document referencing the original order. Restocking behaviour is confirmed separately with operations.

Can several stores feed one Acumatica tenant?

Yes. Each store is mapped separately so orders and channel reporting stay distinguishable.

Is availability real time?

No. It is published on an agreed cadence with an agreed calculation, stated in your scope.

Who owns the integration after launch?

APIWORX monitors it, works exceptions and maintains mappings, escalating business decisions to your named contacts.

Shopify · Acumatica

Acumatica

Shopify / Shopify Plus

Connect Acumatica + Shopify / Shopify Plus

Automate sales order, customer, stock item and price, inventory availability, shipment and tracking between Acumatica and Shopify / Shopify Plus — with monitoring and managed support from APIWORX.

See How It Works

APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.

ERP + eCommerce Specialists

Managed & Monitored Integrations

Expert Integration Team

APIWORX Provides the Service

Yes. APIWORX connects Acumatica and Shopify / Shopify Plus.

But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.

APIWORX automates that process end to end — the objects moving between Acumatica and Shopify / Shopify Plus, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.

Order-to-cash automation Inventory synchronization

How it works

From requirements to a managed integration

Tell Us What You’re Connecting

Provide the systems, workflow and business requirements.

We Design the Integration

APIWORX recommends the integration architecture, mappings and implementation approach.

We Build, Monitor & Support It

APIWORX implements the integration and provides ongoing monitoring and support as applicable.

Who this is for

This page is for ecommerce and operations teams running Acumatica as the ERP behind one or more Shopify stores.

What needs to be in place

Acumatica with API access and a user permitted to create the documents in scope.
A Shopify or Shopify Plus store with API credentials available.
Agreed rules for which warehouses and item classes feed store availability.
A named finance owner for tax, discount and refund treatment.

When you may not need this

A simple single-warehouse store may be well served by lighter tooling. This page is for teams whose order volume, item complexity or refund handling produces recurring manual work.

What is out of scope

Refund handling — credit memo versus return order, and any restocking behaviour — is confirmed in scoping rather than assumed.
Shopify theme and app development are out of scope.
APIWORX does not restructure your Acumatica configuration; we map to what you approve.

What actually moves, and who owns it

A representative Shopify and Acumatica scope, confirmed per customer before build.

AcumaticaAPIWORX (mapping, retries, exception queue)Shopify / Shopify Plus

Objects exchanged between Acumatica and Shopify / Shopify Plus, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Sales order	Shopify	Acumatica	Shopify at capture	Order reaches an agreed status	Held in exception queue with the validation error	APIWORX
Customer	Shopify	Acumatica	Agreed per customer type	New or changed customer	Unmatched customer raises a named exception	APIWORX
Stock item and price	Acumatica	Shopify	Acumatica	Item or price change	Retried, then queued with the rejected field	APIWORX
Inventory availability	Acumatica	Shopify	Acumatica	Agreed publishing cadence	Last published figure retained; exception raised	APIWORX
Shipment and tracking	Acumatica or 3PL	Shopify	Shipment record	Shipment confirmed	Retried, then queued for review	APIWORX
Refund / credit memo	Shopify	Acumatica	Agreed in scoping	Refund approved	Held for finance review	APIWORX (delivery) / you (approval)

Three decisions that make or break this integration

Orders that arrive ready to fulfil

Store orders are validated against Acumatica expectations before a document is created, so missing customers, unmapped items or unexpected tax values become named exceptions rather than bad records inside the ERP.

Trigger status agreed with finance so unpaid or flagged orders do not enter fulfilment.
Discounts, gift cards and shipping charges mapped to agreed treatment.
Warehouse assignment follows your allocation rules.
Unmapped SKUs stop the line rather than defaulting to a catch-all item.

Availability with rules you can point at

Availability published to Shopify is calculated from the warehouses and item statuses you nominate, with buffers applied where you want protection against overselling.

Warehouse inclusion and buffer rules documented per item or group.
Allocation and reserved quantities handled per your Acumatica setup.
Cadence stated in your scope; this page makes no real-time promise.
A failed publish keeps the last known figure and raises an exception.

Refunds handled once, correctly

Refunds are the most common source of cleanup in ecommerce ERP integrations. The credit treatment and any stock movement are agreed before build, and unusual cases are held for approval instead of posted automatically.

Credit memo versus return order treatment agreed with finance.
Partial refunds and shipping refunds mapped explicitly.
Restocking behaviour confirmed with operations.
Held refunds are visible with the reason attached.

Reliability and ownership

The operating rules that apply to this workflow after go-live.

Every run is logged with the source record reference so an order, shipment or stock update can be traced end to end.
Failed messages are retried on a defined schedule; anything that still fails lands in an exception queue rather than being dropped silently.
Duplicate prevention keys on the source system's own identifier (order number, shipment ID, SKU).
Exceptions are worked by the APIWORX team and escalated to your named operations contacts when a business decision is needed.
Mapping changes — new SKUs, new locations, new warehouses, new channels — are part of the ongoing engagement.
Support windows and response commitments live in your agreement; this page does not state an SLA.

How an order is traced

Illustrative — not customer data

An illustrative reference trace between Shopify and Acumatica.

How an order is traced
Shopify order name	Acumatica sales order number
Shopify customer	Acumatica customer ID
Acumatica shipment	Shopify fulfilment with tracking
Shopify refund	Acumatica credit document reference

Scope and questions

How are refunds posted?: Under the treatment finance agrees during scoping — typically a credit document referencing the original order. Restocking behaviour is confirmed separately with operations.
Can several stores feed one Acumatica tenant?: Yes. Each store is mapped separately so orders and channel reporting stay distinguishable.
Is availability real time?: No. It is published on an agreed cadence with an agreed calculation, stated in your scope.
Who owns the integration after launch?: APIWORX monitors it, works exceptions and maintains mappings, escalating business decisions to your named contacts.