Acumatica Connector FAQ: compatibility and workflows.

Every installation includes compatibility review, connector installation, tenant-specific configuration, catalogue and order testing, and production go-live validation.

Acumatica implementations differ substantially between businesses. Onboarding configures the connector for the tenant’s warehouse, pricing, tax, freight, unit, customer, and order workflow before production automation is enabled.

The plugin installs like any WordPress plugin, but the commercial package includes installation and configuration. QuixWP enables scheduled synchronization and automatic export after testing and sign-off. Both start disabled; the onboarding checkbox does not technically prevent an administrator from enabling them earlier.

The implementation time depends on access, catalogue quality, warehouse and price-class complexity, and how quickly test results can be reviewed. QuixWP confirms the expected schedule after the compatibility review.

No. This connector is for Acumatica Cloud ERP and MYOB Acumatica with supported contract-based REST endpoints. See the MYOB Acumatica WooCommerce integration scope.

Yes. It supports Acumatica Cloud ERP and MYOB Acumatica environments that expose the supported contract-based REST API endpoints.

No. The plugin runs inside your WordPress installation and communicates directly with the Acumatica contract-based REST API. Catalogue, pricing, customer, stock, and order data are not routed through a QuixWP-hosted synchronization platform.

Yes. The connector declares compatibility with WooCommerce High Performance Order Storage and uses WooCommerce order APIs rather than directly querying legacy order posts.

Yes. Variations can synchronize stock and price data when each exported or synchronized variation has a unique SKU matching the corresponding Acumatica Inventory ID.

The standard package covers one WooCommerce production site and one Acumatica or MYOB Acumatica tenant. Multi-store or multi-tenant configurations can be reviewed and quoted separately.

The standard onboarding configures the agreed warehouse and stock-availability behavior. Advanced allocation, aggregation, regional warehouse selection, or per-customer warehouse rules may require custom scope.

The standard implementation matches the WooCommerce product or variation SKU to the Acumatica Inventory ID. Exact, consistent SKU data is therefore required before the first synchronization.

The standard package synchronizes existing WooCommerce products and variations. Product creation, images, categories, attributes, and matrix-item generation can be quoted as an additional module.

The code reads supported inventory inquiry fields, preferring on-hand before available quantity when both are present, and sums returned rows by Inventory ID. QuixWP validates the endpoint results against the agreed stock rule. Different warehouse filtering or allocation may require custom work.

Yes. Catalogue synchronization uses WP-Cron. Export retries use Action Scheduler when available, with WP-Cron as a fallback. The first manual run and server scheduling are reviewed during onboarding.

Audit SKU-to-Inventory ID matches before enabling synchronization. Missing quantity records can be treated as zero stock, so do not assume every unmatched SKU will remain unchanged. Product creation is outside the standard workflow.

Yes. WooCommerce roles can be mapped to Acumatica customer price classes, and imported class prices are applied to product, variation, cart, and checkout pricing.

No. Imported base and price-class records are indexed locally so normal storefront requests do not depend on a live ERP API request.

Retail, guest, and ignored roles use the synchronized base price unless another pricing rule is explicitly configured during onboarding.

Customer-specific pricing requires a cache configuration that varies or bypasses full-page cache for logged-in users. QuixWP reviews the active caching setup during onboarding.

The export trigger is configured during onboarding. A common setup exports when an order reaches Processing, but the correct status depends on payment, fraud review, and internal order procedures.

The connector looks up an existing Acumatica customer using a stored customer ID or billing email. It does not create new customer accounts; other matching rules or customer-creation workflows require separate review.

The connector records the export error and retries with increasing delays up to the configured limit. Failed orders remain visible in Order Export for manual retry after the issue is corrected. Review stored order errors before sharing them; diagnostic-log redaction does not guarantee every error field is redacted.

Sent-status checks and an order lock help prevent routine duplicate submissions. They do not guarantee exactly-once delivery after an ambiguous timeout. Check the ERP record before manually re-exporting an order whose response is uncertain.

The standard package focuses on WooCommerce-to-Acumatica SalesOrder export. Bidirectional fulfilment, shipment, refund, invoice, and advanced document workflows are reviewed and quoted separately when required.

The API password and cached session data are encrypted at rest using WordPress salts and the encryption capabilities available on the server. The connector refuses insecure plaintext password storage.

Operational data moves directly between your WooCommerce site and the Acumatica REST API. QuixWP does not require a hosted middleware service to relay catalogue, pricing, customer, stock, or order data.

The diagnostic logger redacts passwords, cookies, email addresses, and common address fields. Redaction is not exhaustive, and stored order errors need separate review. Debug logging should be temporary; direct web access to the log directory must be blocked on the actual hosting server.

Normal storefront price lookups use the local index without a live ERP request. Export API failures are caught and recorded for retry. However, the first export runs on the configured order-status change, so an unavailable or slow ERP can delay that request; zero checkout delay is not guaranteed.

No. Do not send passwords or API credentials through the website form or email. QuixWP arranges a secure credential exchange as part of onboarding when access is required.

The standard package includes one commercial connector licence, one WooCommerce production site, one Acumatica tenant, compatibility review, installation, standard mappings, catalogue and order testing, production sign-off, and one year of updates and support.

Submit the compatibility form with your WooCommerce and Acumatica details. QuixWP reviews the environment, confirms the standard or custom scope, and sends an invoice. Onboarding is scheduled after payment.

Standard maintenance renews at $699/year and includes updates, supported-platform compatibility maintenance, and connector support.

The installed connector continues to run. Licence expiration stops access to plugin updates, compatibility maintenance, and support until the licence is renewed.

Common custom-scope examples include product creation, multi-store or multi-tenant installations, advanced warehouse logic, unusual UOM rules, bidirectional fulfilment, custom API endpoints, and extensive custom-field or tax mapping.