Acumatica Connector setup and operations.

Supported workflows and scope

QuixWP Acumatica Connector connects an established WooCommerce store to Acumatica or MYOB Acumatica. It is designed for businesses that already maintain products in WooCommerce and want Acumatica to remain the operational source for stock, base pricing, customer price classes, and sales-order processing.

The connector includes:

• Secure Acumatica authentication and endpoint-version discovery.
• Manual and scheduled stock and base-price synchronization.
• Customer price-class import and WordPress role mapping.
• Customer-specific storefront, cart, and checkout pricing.
• WooCommerce order export to Acumatica SalesOrder.
• Automatic retries, manual retries, redacted logs, and operational status reporting.
• HPOS-compatible order access and Action Scheduler support.

Onboarding: Acumatica environments differ in tenant structure, warehouses, price classes, tax codes, freight items, units of measure, and custom fields. QuixWP configures those environment-specific details and validates the final workflow before production automation is enabled.

WooCommerce and Acumatica requirements

The Acumatica API user should have only the permissions required for the agreed catalogue, pricing, customer, and SalesOrder operations. QuixWP confirms the exact access requirements during onboarding.

Standard implementation scope

The standard package includes:

• One WooCommerce production website.
• One Acumatica or MYOB Acumatica tenant.
• An existing WooCommerce catalogue with matching SKUs.
• Base-price synchronization.
• Stock-quantity synchronization.
• Customer price-class synchronization.
• WooCommerce role-to-price-class mapping.
• WooCommerce order export to Acumatica SalesOrder.
• Catalogue testing, order testing, and production sign-off.

The following commonly require custom scope: product creation, image and category synchronization, matrix-item generation, advanced multi-warehouse allocation, unusual units of measure, multiple stores or tenants, bidirectional fulfilment, refunds, custom endpoints, and extensive custom-field mapping.

Purchasing and invoicing

The connector is sold as a managed implementation rather than an instant-download checkout.

1. Submit the compatibility form with your WooCommerce and Acumatica environment details.
2. QuixWP reviews the catalogue, tenant, warehouses, price classes, and required order workflow.
3. We confirm whether the project fits the standard $1,499 package or requires additional custom scope.
4. QuixWP sends an invoice describing the confirmed implementation scope.
5. Onboarding is scheduled after payment is received.

No API credentials are required during the initial compatibility review. Secure access is arranged separately after the implementation begins.

WooCommerce Acumatica onboarding workflow

1. Compatibility review: QuixWP reviews the WooCommerce catalogue, Acumatica tenant, Inventory IDs, warehouse setup, price classes, order workflow, and required mappings.
2. Secure installation: The connector is installed, the dedicated API account is configured, and the connection is validated.
3. Catalogue test: A synchronization confirms SKU matching, stock behavior, base pricing, and customer price classes.
4. Order test: A test WooCommerce order is exported and reviewed in Acumatica before automatic exports are enabled.
5. Production sign-off: Scheduling and automatic order export are enabled after both teams approve the results.

The plugin’s Onboarding screen records progress and sign-off. Scheduled sync and automatic export are disabled by default. QuixWP enables them after testing as part of the managed implementation; the sign-off checkbox is not a technical lock on those settings.

Installation

Installation is normally completed by QuixWP as part of onboarding:

1. Go to WP Admin → Plugins → Add New → Upload Plugin.
2. Upload quixwp-acumatica-connector.zip.
3. Activate the plugin.
4. Open WooCommerce → Acumatica Connector.
5. Leave scheduled synchronization and automatic order export disabled until the onboarding tests are complete.

Direct Acumatica REST API connection

Open the Connection screen and enter the Acumatica endpoint details supplied for the dedicated integration account.

Use Test connection before saving the production workflow. A successful test confirms login and endpoint discovery; it does not enable synchronization or order export by itself.

Acumatica stock and price synchronization for WooCommerce

The Catalogue Sync screen controls product matching, price and stock behavior, scheduling, and manual runs.

Matching model

The standard implementation matches:

WooCommerce product or variation SKU = Acumatica Inventory ID

Products must have matching SKUs. Validate missing Inventory IDs during onboarding: missing quantity records are not a guarantee that WooCommerce stock will be preserved.

Supported catalogue data

• Base product price.
• Stock quantity using the agreed Acumatica availability field.
• Customer price-class records.
• Simple products and product variations.

Manual and scheduled runs

The first synchronization is run during onboarding. After validation, catalogue runs use WP-Cron on the configured schedule. Order-export retries use Action Scheduler when available, with WP-Cron as a fallback. Onboarding checks that scheduled tasks execute reliably on your hosting.

Acumatica customer pricing in WooCommerce

The Customer Pricing screen maps WooCommerce user roles to Acumatica customer price classes.

For example:

Imported class prices are indexed locally so storefront price requests do not require a live ERP API request. The connector applies the resolved price to product displays, variation data, cart calculations, and checkout totals.

When no applicable class price exists, the connector uses the indexed base price. If neither exists, WooCommerce keeps its existing price. For variations, price lookup also considers the parent SKU. Eligible roles without explicit mappings can be matched by role key or name, so use explicit mappings and validate multi-role customers during onboarding.

Page caching must vary by logged-in customer or role when customer-specific prices are displayed. QuixWP reviews the store’s caching configuration during onboarding.

WooCommerce order export to Acumatica SalesOrder

The Order Export screen controls when WooCommerce orders are sent to Acumatica and which defaults are used for the SalesOrder payload.

Typical workflow

1. A WooCommerce order reaches the configured export status.
2. The connector resolves the Acumatica customer using the agreed customer-matching rule.
3. Line items are mapped by WooCommerce SKU / Acumatica Inventory ID.
4. Freight-item, unit, and order-type defaults are applied. Any additional branch or tax payload mapping is confirmed separately.
5. The SalesOrder is created and the Acumatica reference is stored on the WooCommerce order.

Failure handling

Failed exports record an error on the WooCommerce order and retry with increasing delays up to the configured limit. The diagnostic logger redacts common sensitive fields, but order notes and stored export errors still need review before sharing. After correcting the issue, an administrator can retry from the plugin’s Order Export screen. WooCommerce order-list columns show export status and the ERP reference.

During managed onboarding, QuixWP leaves automatic order export disabled until a test order has been reviewed and approved in Acumatica.

The first export runs during the configured order-status change. API exceptions are caught and recorded for retry, but a slow or unavailable ERP can delay that request. Routine sent-status checks and an order lock reduce duplicate submissions; reconcile ambiguous responses in Acumatica before a manual re-export.

Customer lookup uses an existing stored Acumatica ID or billing email. It does not create new ERP customer accounts. Standard pricing is role-to-price-class pricing, not individual account-contract pricing.

Logs and diagnostics

The Logs screen provides protected operational diagnostics for connection tests, synchronization runs, and order exports.

• Passwords and session cookies are never intentionally written to the diagnostic log.
• Common email and address fields are redacted.
• Logs are stored in an uploads directory with Apache/IIS deny files. Verify direct-access protection on the actual server; Nginx needs equivalent server configuration.
• Debug logging can be enabled temporarily during onboarding or support investigation.

Do not send API credentials through email or the website support form. QuixWP will arrange a secure credential exchange when access is required.

Licence and maintenance

The Licence screen records the directly issued QuixWP enterprise licence, maintenance status, expiry date, and support entitlement.

The annual maintenance renewal includes:

• Plugin updates and security fixes.
• Compatibility maintenance for supported WordPress, WooCommerce, PHP, and Acumatica versions.
• Connector support and diagnostic assistance.
• Access to new standard connector functionality released during the maintenance period.

When maintenance expires, the installed connector does not deliberately disable ongoing stock, pricing, or order operations. Updates and support remain unavailable until renewal.

Developer hooks

The connector exposes documented actions and filters following the QuixWP naming convention. Examples include synchronization lifecycle events, API request and response filters, pricing resolution filters, SalesOrder payload filters, and export result actions.

Custom work should be implemented through documented hooks or a separate integration module rather than editing the commercial plugin directly.

Troubleshooting

Connection test fails

• Confirm the base URL uses HTTPS and points to the correct Acumatica instance.
• Confirm tenant/company and branch values.
• Verify the dedicated API user can log in and access the required endpoint.
• Check whether a firewall, VPN, allowlist, or security service blocks the WordPress server.

Products are not matching

• Confirm the WooCommerce SKU exactly matches the Acumatica Inventory ID.
• Check both the parent product and variation SKUs.
• Review the latest synchronization result and protected log.

Customer-specific pricing is not visible

• Confirm the customer role is mapped to the intended Acumatica price class.
• Confirm a current class-price record exists for the product.
• Purge page and object caches, and ensure full-page caching varies by logged-in user or role.

An order failed to export

• Open Order Export and review the latest redacted error.
• Confirm every exported line has a matching Inventory ID.
• Confirm customer, branch, UOM, freight, tax, and order-type mappings.
• Correct the issue and use the manual retry action.

Support

For a new implementation, onboarding, compatibility, or technical support, use the Acumatica Connector support form. Include the WooCommerce version, Acumatica product/version, affected workflow, and the approximate time of the latest failure. Do not include passwords or API credentials.