For a reseller store, connecting WooCommerce to Acumatica involves more than copying a product’s price. Different customers may belong to different pricing tiers, while stock needs to reflect what the business can supply.
In one custom implementation behind QuixWP’s Acumatica Connector, we connected a WooCommerce store to MYOB Acumatica using a straightforward model: one warehouse, shared reseller price classes and a nightly stock-and-price sync.
Matching reseller pricing across both systems
The business already maintained its reseller price classes in Acumatica. Multiple reseller accounts belonged to the same class, so there was no need to maintain a separate price list for every customer.
In WooCommerce, we created corresponding user roles and mapped them to those Acumatica price classes.
During synchronization, the integration stored each class’s prices in the local WooCommerce database. When a reseller signed in, the store displayed the pricing associated with their role.
This kept pricing managed centrally in Acumatica while allowing WooCommerce to serve customers from locally stored data. Browsing a product did not require a live pricing request to the ERP.
Why synchronization ran once a day
MYOB prices changed only once a day, so continuously requesting the same pricing data would have added work without making those prices fresher.
The integration synchronized stock and pricing overnight, during a low-traffic window around 1–3 a.m. The store used one warehouse, which kept the stock mapping simpler: there was no need to choose between several warehouses or define how their quantities should be combined.
The daily schedule matched this store’s workflow. It was not a universal recommendation for every WooCommerce business.
A store with frequent inventory movements may need stock updates more often, even if its prices change only daily.
More frequent updates need a realistic processing window
Synchronization can run more frequently, but the interval needs to account for how long a complete run takes.
Product count, the volume of customer-class pricing and Acumatica response times can all affect processing duration. A larger catalogue with several reseller tiers may take considerably longer than a small store with one price per product.
Before choosing a schedule, measure a representative run and decide how much delay the business can accept. Increasing frequency alone does not guarantee that updates will finish sooner or that stock will always be current.
What this means for another store
The useful starting point is to define three things:
- Product matching: how WooCommerce SKUs correspond to Acumatica Inventory IDs.
- Customer pricing: which Acumatica price classes map to which WooCommerce user roles.
- Update timing: how often stock and prices change, and how long synchronization takes.
From a custom implementation to QuixWP Acumatica Connector
Warehouse rules and the meaning of the stock quantity also need agreement before launch. On-hand stock and stock available to sell are not necessarily the same figure.
QuixWP Acumatica Connector grew from this production integration. The commercial plugin generalizes that work, but the original store’s configuration should not be treated as a guarantee that every Acumatica setup behaves identically.
For your store, we start with a compatibility review to confirm the product mapping, warehouse model, pricing classes and synchronization requirements.
Frequently asked questions
Were reseller prices requested live from Acumatica?
No. This implementation stored prices for each Acumatica price class in the local WooCommerce database during synchronization. Logged-in resellers saw prices associated with their mapped WooCommerce user role.
Why did the store synchronize only once a day?
MYOB prices changed once daily. The store ran its stock-and-price sync during a low-traffic window around 1–3 a.m. Another store may need more frequent updates depending on stock movements and processing time.