How to Reconnect Your WooCommerce Integration

Your WooCommerce connection feeds orders, refunds, and products into Kintsugi so your sales tax calculations and filings stay accurate. If that connection breaks or sync requests start failing, it's almost always one of a few well-understood causes below and each one has a quick fix. This guide covers why a WooCommerce connection typically disconnects, how to reconnect it, and answers to the questions we hear most often about WooCommerce specifically.

Why Did My WooCommerce Integration Disconnect?

WooCommerce connections work a little differently from other platforms: connecting involves two separate steps: linking your store on the Kintsugi Import page, and then entering your API key in the WordPress plugin. Most disconnects and sync failures trace back to one of these:

• The underlying Kintsugi connection was removed, but the plugin still has an old API key. If you disconnect or "start over" on the Kintsugi side, the plugin has nothing left to connect to, even though the API key itself may still look valid. This shows up as a "Connection Failed" error in WordPress.

• The API key's WordPress user doesn't have enough permission. WooCommerce API keys inherit the permissions of the WordPress user they were created under. Keys created under Editor, Author, Contributor, or Customer roles will fail on orders and refunds (often with a 403 / woocommerce_rest_cannot_view error) even if everything else looks correctly set up.

• Cloudflare, a WAF, or a security plugin is blocking sync requests. If your store uses Cloudflare, Wordfence, or similar, sync requests to /wp-json/wc/* can be silently blocked even when the connection looks healthy in Kintsugi.

How to Reconnect

If you see "Connection Failed" in the WordPress plugin:

1. Log in to Kintsugi and go to the Import page.

2. Reconnect your WooCommerce store there first, as this re-establishes the underlying connection.

3. Once the store shows as Connected in Kintsugi, go back to your WordPress plugin and re-enter your API key.

4. If it still fails after that, regenerate the key (see below) and reconnect using the new credentials.

If sync is failing on orders or refunds (API key permissions):

1. Go to Users → All Users in your WordPress admin.

2. Find the user tied to your API key and confirm their role.

3. If it's Editor, Author, Contributor, or Customer, change it to Shop Manager or Administrator.

4. If it still fails, regenerate the key under WooCommerce → Settings → Advanced → REST API. Set the permission to Read for a read-only integration or Read/Write for a tax engine integration, then reconnect in Kintsugi with the new Consumer Key and Secret.

If sync requests are being blocked (Cloudflare or firewall):

1. Whitelist these static IP addresses: 18.197.244.247, 18.156.9.3, 3.65.139.215.

2. IP allowlisting alone won't bypass Cloudflare's bot protection, so in Cloudflare, go to Security → Bots and disable Bot Fight Mode, or exclude /wp-json/* from it.

3. Disable Browser Integrity Check for /wp-json/* under Configuration Rules.

4. Make sure the exception covers both the product/order sync path and the refunds path (/wp-json/wc/v3/orders/{order_id}/refunds). Refunds can still fail even after products and orders sync correctly.

5. If requests are still being blocked, check Security → Events for the specific rule that's firing and the associated cf-ray ID.

If you've checked all of the above and your sync still isn't working, contact Kintsugi Support with your store URL and we'll take a closer look.

FAQs

Q: Is it safe to reconnect my WooCommerce integration?

A: Yes. Reconnecting only re-establishes the connection and refreshes your API key. It doesn't affect data that's already synced.

Q: I disconnected and "started over," and now my API key won't connect. What happened?

A: Disconnecting on the Kintsugi side removes the underlying connection the plugin relies on, even if the API key itself is unchanged. First, reconnect your store on the Kintsugi Import page, then re-enter the API key in the WordPress plugin; doing it in that order resolves this.

Q: Why do products sync fine but orders and refunds fail?

A: This is almost always an API key permission issue. The WordPress user tied to the key needs the Shop Manager or Administrator role; lower roles can fetch products but will be blocked from orders and refunds.

Q: My connection looks healthy in Kintsugi, so why isn't anything syncing?

A: Check whether your store is behind Cloudflare, a WAF, or a security plugin. These can silently block sync requests to /wp-json/wc/* even when Kintsugi shows the connection as fine.

Q: I fixed the Cloudflare rule for products and orders, but refunds still aren't working. What could be the problem?

A: Refunds use a different endpoint path (/wp-json/wc/v3/orders/{order_id}/refunds). Make sure your Cloudflare exception explicitly covers that path too, not just the general product/order sync paths.

Q: Do I need to regenerate my API key every time I change a user's role?

A: Yes. If the WordPress user's role changes after the key was created, regenerate the key so it picks up the updated permissions, then reconnect in Kintsugi with the new credentials.
Q: What if I've checked everything and sync still isn't working?

A: Contact Kintsugi Support with your store URL and we'll dig into the specific request logs on our end.

Need Help?

Still need help? Reach out to our support team anytime using the chat in the bottom-right of your screen. We are always here and happy to help.