Skip to main content
Connecting Shopify brings orders, abandoned checkouts and your product catalogue into Watx as they happen, and gives the store its own console with order messages, cart recovery and cash on delivery. There are two ways to connect, and they are not equivalent.

​
Which method to use

Shopify treats a customer’s name, phone, email and address as protected data. A custom app you build in your own Shopify admin only receives those fields on the Grow plan or above — on every other plan they arrive empty, silently. Without the phone number, order messages, cart recovery, cash-on-delivery confirmation and contact creation all stop working.
Installing the Watx app is the recommended path: it receives those fields on every plan. The paste-a-token path exists for merchants who already have a working token, or who are on Grow or above and would rather not wait.
Nothing to copy or paste. You approve access on Shopify and come straight back.
1

Open the connect dialog

Integrations → Shopify → Connect. The dialog opens on Install the Watx app, which is the default.
2

Enter your store address

Your .myshopify.com address — not a custom domain like shop.yourbrand.com.
3

Continue to Shopify

Press Continue to Shopify, review the permissions, and approve. You are returned to the store console, and the first catalogue sync starts on its own.
If your Watx contact set up the app in their own Shopify Partner Dashboard and sent you a Client ID and Client secret, open I created the app in my own Partner Dashboard on the same dialog and paste both before pressing Continue. Both fields or neither — an ID without its secret is refused, because pairing one app’s ID with another’s secret makes every webhook fail its signature check for a reason no error message explains.
You may be asked to approve twice: once to install the app, and once when Watx exchanges the access token. Shopify may skip the second prompt if nothing new is being asked for.

​
What Watx reads and writes

The console’s Overview tab shows the scopes the token actually carries, read live from the store — what you ticked, not what was asked for. Shopify collapses read_orders into write_orders when both are granted, so a store with write access may not list the read scope separately.

​
What arrives after connecting

Watx registers 13 webhook topics on the store and starts a catalogue sync: orders/create · orders/updated · orders/paid · orders/fulfilled · orders/cancelled · refunds/create · checkouts/create · checkouts/update · checkouts/delete · products/create · products/update · products/delete · app/uninstalled The Overview tab lists every topic with whether it is registered, when an event last arrived on it, and how many arrived in the last 24 hours. A topic that is registered but has never received anything is the sign that the signing secret is wrong. Registration is idempotent — Re-register webhooks from the console’s More actions menu can be run at any time. If registration fails, the store still connects and the Overview carries the error.

​
Order messages and contacts

An order creates the contact (source store) and an empty WhatsApp thread, so an order message can reach a customer who has never written to you. Abandoned carts do not create contacts — they only match existing ones. Set the messages up on the console’s Messaging tab, and the confirmation flow on Cash on delivery.

​
Reconnecting

​
Disconnecting

More actions → Disconnect store removes the store, its synced catalogue, orders and carts from the workspace, the webhook subscriptions held at Shopify, and the message automations built for it. It cannot be undone. Disconnect through Watx rather than only removing the app in Shopify — otherwise the subscriptions keep delivering to a dead token.
One Shopify store per workspace. To connect a different one, disconnect the first.

​
When something is wrong

More in Troubleshooting integrations.