Do you replace the WooCommerce plugin we use today?

Often yes for the ERP flow, but we scope it with you. Where a plugin is doing work you want to keep, we integrate around it rather than fighting it.

Can inventory be updated instantly?

Availability is published on a cadence agreed with you. We do not claim real-time updating on this page; cadence is chosen against your order pattern and channel risk.

Are refunds supported?

Refund posting depends on your Acumatica configuration and your finance team's rules. It is confirmed in scoping rather than assumed.

What about multiple warehouses?

Multi-warehouse allocation is supported through rules you approve — which locations feed the store, and how orders are assigned.

Who owns the integration after go-live?

APIWORX takes responsibility for the agreed workflows, works the exception queue and handles mapping changes. You keep master data and commercial decisions.

How is scope determined?

From the objects in play, your Acumatica configuration and the store's plugin footprint. You get a written scope before any build.

eCommerce · Cloud ERP

Acumatica

WooCommerce

Connect Acumatica + WooCommerce

Automate sales order, customer record, item / stock item match, inventory availability, shipment / tracking between Acumatica and WooCommerce — 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 WooCommerce.

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 WooCommerce, 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

For eCommerce and operations teams running WooCommerce on WordPress with Acumatica as the ERP of record.

What needs to be in place

Acumatica with REST access and a service account permitted to create sales orders and read inventory.
WooCommerce with REST API keys and, where used, the plugins that affect orders, tax or subscriptions identified up front.
Agreed item numbering between the store and Acumatica.
A named owner for customer and item master data.

When you may not need this

A simple store with one warehouse, standard tax and no B2B pricing may be served adequately by a plugin. Managed integration matters when plugin conflicts break order flow, when refunds and cancellations need to reach the ERP correctly, or when nobody is watching whether last night's orders actually landed.

What is out of scope

APIWORX does not maintain your WordPress or WooCommerce plugin estate.
Storefront design, checkout behaviour and payment gateway configuration remain yours.
Which refund and cancellation paths can be automated in Acumatica is confirmed in scoping — it depends on your configuration.

What actually moves, and who owns it

A representative WooCommerce ↔ Acumatica scope. Final objects and direction are agreed before build.

AcumaticaAPIWORX (mapping, retries, exception queue)WooCommerce

Objects exchanged between Acumatica and WooCommerce, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Sales order	WooCommerce	Acumatica	Acumatica (once created)	Order reaches an agreed status	Held in exception queue; store order untouched	APIWORX
Customer record	WooCommerce	Acumatica	Acumatica	Matched at order creation, created if new	Order held rather than duplicating a customer	APIWORX (matching) / you (master data rules)
Item / stock item match	Agreed mapping	Acumatica	Acumatica	Per order line	Unmapped SKU raises a named exception	APIWORX
Inventory availability	Acumatica	WooCommerce	Acumatica	Scheduled publish on an agreed cadence	Last good quantity stands; failure alerted	APIWORX
Shipment / tracking	Acumatica	WooCommerce	Acumatica	Shipment confirmed	Retried; persistent failures queued	APIWORX
Cancellation	WooCommerce	Acumatica	Acumatica	Cancelled before fulfilment	Escalated when already picked or shipped	APIWORX (delivery) / you (decision)
Refund / credit	WooCommerce	Acumatica (where supported by your configuration)	Acumatica	Refund recorded in the store	Queued for finance review rather than posted blind	APIWORX (delivery) / you (accounting rules)

Three decisions that make or break this integration

Customer and item matching

Almost every WooCommerce-to-ERP problem is a matching problem. Guest checkout, repeat buyers with different email addresses and store SKUs that drifted from the ERP part number all produce duplicates unless the rules are decided in advance.

Matching key agreed — email, customer number or a store field you control.
Guest orders handled by an explicit rule, whether that is a single walk-in account or a created record.
Store SKU to Acumatica inventory ID via a mapping table, with variants handled deliberately.
An unmatched item holds the order instead of posting to a fallback item.

Sales-order import

Which store status should create an ERP order, and what the order should look like once created, is a business decision. We settle it early so finance and the warehouse see the same thing.

Trigger status chosen — paid, processing, or another store status you nominate.
Tax, shipping and discount lines mapped to the Acumatica fields and accounts your controller approves.
Warehouse and branch determined by rules rather than defaults.
The store order number is carried into Acumatica so support can trace either way.

Shipment, cancellation and refund handling

The end of the order is where most integrations stop and most customer-service problems start. Shipment, cancellation and refund paths are scoped rather than left as a follow-up project.

Shipment and tracking pushed back to WooCommerce so the customer sees a real status.
Partial shipments reflected rather than collapsed into a single despatch.
Cancellations before fulfilment applied automatically; after despatch they escalate as a decision.
Refunds mapped to the credit process your finance team already uses, where your Acumatica configuration supports it.

Reliability and ownership

Store-to-ERP flows fail at 2am. These are the arrangements that mean someone notices before you do.

Every run is logged with the source record reference so a document 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, PO number, document ID) so a replayed message does not create a second record.
Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
Mapping changes — new SKUs, new accounts, new dimensions, new trading-partner requirements — are handled as part of the ongoing engagement.
Response commitments and support windows are set in your agreement; this page does not state an SLA.

Illustrative order mapping

Illustrative example — not a customer result

An anonymised mapping shape used in scoping.

Illustrative order mapping
WooCommerce order number	Acumatica sales order → Customer Order Nbr.
Store SKU	Acumatica inventory ID (via mapping table)
Billing email	Customer matching key
Shipping method	Acumatica ship-via code
Tax total	Nominated tax handling per your configuration
Tracking number on shipment	WooCommerce order note / tracking field

Scope and questions

Do you replace the WooCommerce plugin we use today?: Often yes for the ERP flow, but we scope it with you. Where a plugin is doing work you want to keep, we integrate around it rather than fighting it.
Can inventory be updated instantly?: Availability is published on a cadence agreed with you. We do not claim real-time updating on this page; cadence is chosen against your order pattern and channel risk.
Are refunds supported?: Refund posting depends on your Acumatica configuration and your finance team's rules. It is confirmed in scoping rather than assumed.
What about multiple warehouses?: Multi-warehouse allocation is supported through rules you approve — which locations feed the store, and how orders are assigned.
Who owns the integration after go-live?: APIWORX takes responsibility for the agreed workflows, works the exception queue and handles mapping changes. You keep master data and commercial decisions.
How is scope determined?: From the objects in play, your Acumatica configuration and the store's plugin footprint. You get a written scope before any build.