WordPress and WooCommerce integration

Availability and requirements

This managed connector is not currently available for live use. Setup documentation is ready; provider sandbox verification is pending. Use a separate test store when the test environment is available.

Store credentials and permissions

WooCommerce: create store REST API credentials with the permissions needed for this connection. Read access is needed for authoritative orders, products and refunds; webhook registration and approved stock publication need write access. Use a dedicated signing secret shared only with this connection’s registered webhooks or trusted WordPress plugin.

Connect and route the store

Download the versioned ZIP below. Requires WordPress 6.5+, PHP 8.1+ and WooCommerce. The signing secret is not displayed again; keep it in a secure store and protect WordPress administration and backups.

Create a WooCommerce connection for the intended store and environment. In Provider setup, verify the store credentials and matching signing secret. Pause an active connection before replacing credentials.
Approve product and variant mappings. Configure accounts, invoice authority and optional Supply routing. Map exact WooCommerce tax IDs to approved tax components/rates. Configure a separately approved shipping service when shipping is charged.
Register store webhooks in Provider setup. Copy the displayed Webhook callback URL. For WooCommerce, download the MeshDex Commerce WordPress ZIP below and upload it in WordPress → Plugins → Add New → Upload Plugin, then activate it in your test store. In WooCommerce → MeshDex Commerce, enter that callback URL and matching signing secret. Protect site administration and backups.

Download MeshDex Commerce for WordPress / WooCommerce · v1.0.0 — Installable ZIP for a test store. Requires WordPress 6.5+, PHP 8.1+ and WooCommerce. Provider sandbox verification remains pending.

Payments, refunds and stock

Guest buyers without a stable customer ID remain order-scoped to prevent merging unrelated customers.
Deleting a store order does not prove cancellation. Paid/posted changes require accounting review.
Physical financial refunds do not automatically restock goods. Supply returns and quality checks remain separate. Partial physical fulfillment requires the governed stock workflow.
Unusual tax rounding, unsupported pricing, gateway splits or missing foreign-exchange evidence require reviewed canonical events. Provider payouts continue through the documented settlement contract.
Indian GST component mappings require the approved combined Ledger tax rate, HSN/SAC and place of supply. The provider destination must match the configured place of supply. Multi-region or ambiguous tax treatment enters review instead of silently applying another region’s tax.
WooCommerce subscription or specialized gateway extensions may need their developer to send the canonical subscription, currency, settlement and refund events. A completed order status alone is not proof of each gateway capture.
Before live use, test webhook signatures, discounts and shipping, tax-bearing orders, partial/full refunds, missed notifications, backfill resume and revoked credentials. WooCommerce sandbox and WordPress installation testing remain pending; the downloadable package is for preparing that test environment.

Recovery and acceptance checks

Review final event outcomes after queue acceptance. Test missed notifications, backfill resume, duplicate delivery and credential revocation before activating a live store.

Test orders, individual captures, cancellation, credits and refunds. A manual WooCommerce refund creates a credit without claiming gateway cash. Enable signed-plugin cash confirmation only after verifying the trusted plugin’s confirmed gateway refunds.
Use Provider delivery & recovery to inspect failed jobs. Correct configuration before entering an audit reason and retrying. Use order/catalog backfill for missed notifications; verify accounting outcomes after queue acceptance.

Related guides

Need help with this workspace?

Ask your workspace administrator for access or contact support with the page name and a sanitized error message.

Store credentials and permissions

WooCommerce: create store REST API credentials with the permissions needed for this connection. Read access is needed for authoritative orders, products and refunds; webhook registration and approved stock publication need write access. Use a dedicated signing secret shared only with this connection’s registered webhooks or trusted WordPress plugin.

Connect and route the store

Create a WooCommerce connection for the intended store and environment. In Provider setup, verify the store credentials and matching signing secret. Pause an active connection before replacing credentials.

Approve product and variant mappings. Configure accounts, invoice authority and optional Supply routing. Map exact WooCommerce tax IDs to approved tax components/rates. Configure a separately approved shipping service when shipping is charged.

Register store webhooks in Provider setup. Copy the displayed Webhook callback URL. For WooCommerce, download the MeshDex Commerce WordPress ZIP below and upload it in WordPress → Plugins → Add New → Upload Plugin, then activate it in your test store. In WooCommerce → MeshDex Commerce, enter that callback URL and matching signing secret. Protect site administration and backups.

Download MeshDex Commerce for WordPress / WooCommerce · v1.0.0 — Installable ZIP for a test store. Requires WordPress 6.5+, PHP 8.1+ and WooCommerce. Provider sandbox verification remains pending.

Payments, refunds and stock

Guest buyers without a stable customer ID remain order-scoped to prevent merging unrelated customers.

Deleting a store order does not prove cancellation. Paid/posted changes require accounting review.

Physical financial refunds do not automatically restock goods. Supply returns and quality checks remain separate. Partial physical fulfillment requires the governed stock workflow.

Unusual tax rounding, unsupported pricing, gateway splits or missing foreign-exchange evidence require reviewed canonical events. Provider payouts continue through the documented settlement contract.

Indian GST component mappings require the approved combined Ledger tax rate, HSN/SAC and place of supply. The provider destination must match the configured place of supply. Multi-region or ambiguous tax treatment enters review instead of silently applying another region’s tax.

WooCommerce subscription or specialized gateway extensions may need their developer to send the canonical subscription, currency, settlement and refund events. A completed order status alone is not proof of each gateway capture.

Before live use, test webhook signatures, discounts and shipping, tax-bearing orders, partial/full refunds, missed notifications, backfill resume and revoked credentials. WooCommerce sandbox and WordPress installation testing remain pending; the downloadable package is for preparing that test environment.

Recovery and acceptance checks

Review final event outcomes after queue acceptance. Test missed notifications, backfill resume, duplicate delivery and credential revocation before activating a live store.

Test orders, individual captures, cancellation, credits and refunds. A manual WooCommerce refund creates a credit without claiming gateway cash. Enable signed-plugin cash confirmation only after verifying the trusted plugin’s confirmed gateway refunds.

Use Provider delivery & recovery to inspect failed jobs. Correct configuration before entering an audit reason and retrying. Use order/catalog backfill for missed notifications; verify accounting outcomes after queue acceptance.