Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Connect your WooCommerce store and your team can see its latest orders and its products inside Avox, next to the chats. With one extra step in WooCommerce, Avox also hears about new and changed orders the moment they happen. This page covers everything from connecting to disconnecting, including what Avox does when your store is slow, down or says no.
Avox can:
Avox cannot:
https://;https:// address that anyone on the internet can reach. A
local or private test site cannot connect, and Avox only accepts the standard port.Create a read-only key in WooCommerce
In WordPress open WooCommerce, then Settings, Advanced, REST API, and click Add key.
Pick a user, set Permissions to Read (that is enough), and generate it. Copy the Consumer
key (starts with ck_) and the Consumer secret (starts with cs_) before you leave the page.
Open WooCommerce in Apps
In Avox open Apps in the sidebar (under Connect & Monitor), then WooCommerce, click Connect, read What Avox can do and click Continue.
Paste your details
Fill in Store address (like https://shop.example.com), Consumer key and Consumer secret.
Webhook secret is optional and can be added later. Click Connect.
Avox checks the key
Avox asks your store for one product to try the key before saving anything. The check gives up after 10 seconds. If it works you see WooCommerce is connected. The keys are stored encrypted and never shown again.
A wrong address gives AVX-3702, a key that doesn't start with ck_ or cs_, or
that your store refuses, gives AVX-3686. Coming soon does not apply here:
WooCommerce connects with your own keys, so it is ready as soon as you are.
Without this, Avox still shows your orders whenever you open the page. With it, new and changed orders arrive by themselves.
Until the secret is saved, Avox shows AVX-3709 and refuses the updates, because it cannot check they came from your store. WooCommerce's first test message when you save the webhook is answered normally.
WooCommerce has its own menu under Apps: Overview, Orders, Products and Activity.
Connection statuses are Connected, Needs reconnecting (your store refuses the key: click Reconnect with a new one), Having trouble (several calls in a row failed) and Disconnected.
Example (hypothetical): a customer messages about an order. Your team opens WooCommerce > Orders, opens the order and sees it is Paid and still processing, then tells the customer in the chat. Once your webhook is on, an order marked completed in WooCommerce shows as Fulfilled in Avox without anyone refreshing.
https://, by itself.Your store runs on your own hosting, so slowness and security tools are the usual causes.
Updates that fail the check are counted under Instant updates; this never changes the status. Fix the secret and the count starts over.
Click Disconnect on the Overview. Avox lists what uses WooCommerce, deletes the keys it saved and keeps the log for your retention period. Avox can't tell WooCommerce itself, so to be sure the key can't be used again, revoke it under WooCommerce > Settings > Advanced > REST API and delete Avox's webhook under Webhooks.
The address must start with https://, be reachable from the internet, use the standard port, and
have no password in it (AVX-3702). A site on a private network can't be reached.
No. Orders and products always load when you open the pages. The webhook only makes new and changed orders arrive without waiting.
Your store no longer accepts the key. Create a new read key and click Reconnect, then paste it. Leave Webhook secret empty to keep the one saved.
Avox reuses lists for 30 seconds. Click Refresh, or turn on instant updates.
Last updated