Acumatica and WooCommerce integration setup

Connect Acumatica with WooCommerce using a product and order map. Check connector requirements, warehouse stock, prices and failed updates.

Yes, an Acumatica WooCommerce integration is available through third-party connectors. Choose a WooCommerce-specific route, then map its supported stock and order flows. Acumatica’s native Shopify connector does not establish WooCommerce compatibility.

Establish the available connection method

Use a documented WooCommerce connector whose scope matches your catalogue and order workflow. Acumatica’s commerce overview distinguishes its native connectors from supported integrations for other platforms, including WooCommerce.

Two documented routes illustrate the difference. Acumatica’s marketplace lists AcuWoo by Ecommerce Business Partners, with technically validated versions 2026 R1, 2025 R2 and 2025 R1. The listing describes inventory and customer synchronisation, imported WooCommerce orders and customer-specific prices. That is a separate third-party offering.

QuixWP Acumatica Connector runs within WordPress and connects directly to Acumatica’s contract-based REST application programming interface (API). Its standard scope updates existing WooCommerce products’ stock and prices, then exports eligible orders to Acumatica. It requires a commercial implementation. Use the following mapping and checks for that narrower route.

Compatibility and access requirements

The QuixWP setup guide declares WordPress 6.0+, WooCommerce 7.0+ and PHP 7.4+ as connector minimums. It requires a supported Acumatica contract-based REST endpoint. Match the endpoint version and tenant during setup. These minimums are separate from the requirements of the WooCommerce release you install.

WooCommerce’s server recommendations call for PHP 8.3+ and WordPress 6.9+, plus HTTPS and adequate memory. Use supported platform versions together. An old connector minimum is not a reason to retain an unsupported server environment.

Install the supplied WordPress plugin with an authorised administrator. Configure a dedicated Acumatica integration user with access to the required inventory and pricing records and SalesOrder operations. Record the instance URL, tenant and branch. QuixWP documents encrypted password storage. Keep credentials out of support forms and ordinary email.

Keep scheduled sync and automatic order export disabled during setup. A successful connection test confirms access, not correct warehouse or tax mappings. Test an actual product and order before enabling either flow.

QuixWP declares support for WooCommerce High Performance Order Storage (HPOS). Product creation and advanced warehouse allocation require separate scope, as do fulfilment and refund updates back to WooCommerce. Its standard customer matching uses existing Acumatica customers. Include customer creation explicitly if your store needs it.

Map the store to the back-office records

Keep WooCommerce responsible for the storefront catalogue structure and Acumatica responsible for the stock and price records you choose to synchronise. The QuixWP route matches a WooCommerce product or variation’s stock-keeping unit (SKU) to an Acumatica Inventory ID.

A fictional catalogue map

Suppose a retailer sells insulated drink bottles in two sizes. The following map is illustrative. It defines the intended records and units for an implementation test.

WooCommerce recordSKU and Acumatica itemSales unitStock sourcePrice owner
500 mL navy variationBOTTLE-500-NAVYOne bottleEligible dispatch stockAcumatica base or mapped class price
750 mL navy variationBOTTLE-750-NAVYOne bottleEligible dispatch stockAcumatica base or mapped class price
Six-bottle cleaning bundleCLEANER-6PACKOne pack of sixA separately mapped pack itemAcumatica pack price
Parent bottle productBOTTLE-PARENTGrouping onlyEach variation owns its quantityEach variation owns its price

Give each sellable variation its own matching SKU. WooCommerce allows a blank variation SKU to inherit the parent’s SKU. For this integration, that would obscure which Acumatica item the line must use. Inspect variation-level stock and price after the first sync.

For the cleaning bundle, a WooCommerce quantity of two means two packs, or twelve bottles. Import a two-pack order and inspect the Acumatica unit and extended quantity. A matching SKU alone cannot prove a correct unit conversion.

Decide which stock can be sold

Set a stock rule before copying quantities. In this fictional catalogue, Perth has 18 navy 500 mL bottles, with five committed to other orders. Melbourne has nine, with two committed. Another four await inspection after returns.

If both dispatch warehouses supply the online store, the intended sellable quantity is 13 plus 7, or 20. Inspection stock contributes zero. Keep that calculation beside the actual endpoint response and WooCommerce quantity during the test.

QuixWP’s FAQ says its inventory inquiry prefers on-hand over available quantity when both fields exist, then sums returned rows by Inventory ID. That behaviour needs to match your intended rule. A raw total of 31 in this example would include commitments and inspection stock. Resolve the endpoint’s warehouse filtering or custom calculation before enabling scheduled stock updates.

Also test a purchase before the next stock sync. After WooCommerce reduces its stock, confirm the Acumatica order records the demand before a refreshed quantity can make those units sellable again. Measure that sequence in your test environment with one identifiable item.

Keep customer prices and tax consistent

QuixWP maps WooCommerce roles to Acumatica customer price classes. Its product scope separates that class pricing from individual customer contracts. A trade role and a named customer’s negotiated agreement are different records.

For a fictional trade account, compare the 500 mL bottle on the product page, in the basket and at checkout. Repeat as a guest in a separate session. Confirm that cached pages keep the two prices separate. Customer replies must use the signed-in account’s price context if they quote a trade price.

WooCommerce’s tax settings distinguish prices entered inclusive of tax from prices entered exclusive of tax. Match that choice to the synchronised amount. Then compare an order’s line tax, shipping tax and final total with the Acumatica document.

Keep currency and rounding in the same mapping record. A correct unit price with a wrong tax basis still produces a wrong checkout total. Treat stock, price class and tax context as inputs to customer replies, with checkout providing the final order amount.

Validate background jobs and order changes

Follow one purchase from WooCommerce payment to an Acumatica sales order, then inspect shipment and cancellation separately. QuixWP’s standard route exports orders. Plan a manual handoff for later statuses unless your implementation includes the return flow.

Trace an illustrative purchase

  1. In a test store, buy two 500 mL bottles. WooCommerce owns the checkout and payment status. Pending payment means payment is outstanding. For this physical order, Processing means payment has arrived and stock has been reduced.
  2. Configure Processing as the export trigger for this example. Find the resulting SalesOrder in Acumatica and its reference on the WooCommerce order. Compare the customer, two-unit quantity and tax-inclusive total with the payment record.
  3. Warehouse staff process and confirm the shipment in Acumatica. The warehouse’s shipment is the evidence that goods left. In a standard QuixWP setup, staff must update WooCommerce’s fulfilment status and tracking through their agreed manual process. Completed must follow fulfilment.
  4. Place a separate paid order and cancel it before dispatch. Mark the WooCommerce order Cancelled, locate any exported Acumatica order and stop its warehouse processing. Staff must reconcile both systems and inspect the payment refund separately.
  5. Reconcile the inventory effect once. Inspect the WooCommerce adjustment and the Acumatica commitment or cancellation, then compare the next stock sync with the physical quantity. An order cancellation must not restore the same units twice.

The WooCommerce order-status guide separates Processing, Completed and Cancelled. An exported ERP reference is evidence of order transfer. It does not establish shipment, payment settlement or cancellation in both systems.

Diagnose a failed job or webhook

QuixWP documents WP-Cron for catalogue runs and Action Scheduler for export retries when available, with a WP-Cron fallback. WP-Cron depends on site requests unless the host runs it independently. A quiet store can therefore expose scheduling delays that a busy staging test misses.

Open WooCommerce > Status > Scheduled Actions to inspect failed or overdue actions. Search by the connector’s hook or group and read the action log. Compare the last completed run with the product movement you expected to see. Check the connector’s Order Export screen for the order’s own error.

A different connector can use WooCommerce webhooks. For that route, inspect WooCommerce > Settings > Advanced > Webhooks and the webhooks-delivery source under Status > Logs. Compare the event’s order identifier with the receiver’s record and response status. A delivered notification still needs a matching ERP order.

Reconcile exceptions before replaying them

FailureEvidence to collectWhere to inspectSafe reconciliation
Unmatched SKUThe failed line’s variation SKU and intended Inventory IDWooCommerce variation editor and Acumatica item recordCorrect the match, test one item and inspect its stock. QuixWP warns that missing quantity records can become zero stock.
Failed scheduled runThe action status, execution log and last successful syncWooCommerce Scheduled Actions and connector logsFix the reported access or mapping fault, then run one controlled sync.
Failed webhookThe delivery response and matching receiver eventWooCommerce webhook logs and the receiving integrationRepair delivery, then reconcile the order identifier before replaying the event.
Repeated order importThe WooCommerce order ID and every matching ERP referenceConnector Order Export and Acumatica Sales OrdersPause retries and inspect whether the first request created an order despite a timeout. Retry only after resolving that result.

Keep raw logs private and remove credentials and customer details before sharing diagnostics. Enable recurring jobs after the test order and cancellation agree across both systems, with a named owner for exceptions and manual status updates.

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.

See it in actionFree trial · Simple setup