Common Issues

Connection issues

Cloudflare or a WAF is blocking the connection

This is the most common connection problem for WooCommerce users. If your site uses Cloudflare (or another web application firewall), it may block Coupler.io's requests and return an HTML page instead of JSON data. You'll typically see errors like line 1 column 1 (char 0) or a generic "non-JSON response" message.

To fix this, whitelist Coupler.io's IP addresses in your Cloudflare firewall rules, or temporarily disable the "Bot Fight Mode" or "Under Attack" mode. Contact Coupler.io support to get the current list of IP addresses to whitelist.

401 Unauthorized — access token is invalid

This means the Consumer Key or Consumer Secret you entered is incorrect, or the API key has been deleted or regenerated in WooCommerce.

Go to WooCommerce → Settings → Advanced → REST API in your WordPress admin and verify the key exists. If you've regenerated it, create a new data flow connection in Coupler.io with the updated credentials. Also double-check that you're using the correct store URL — it must match the URL your WooCommerce store is served on exactly.

Wrong site URL causing a non-JSON response

If your store URL redirects (e.g., from HTTP to HTTPS, or from www to non-www), Coupler.io may receive an HTML redirect page instead of API data. Always enter the final, canonical URL of your store — the one you see in your browser after all redirects resolve.

Missing data

Product variations are missing

WooCommerce returns product variations as nested data within each product record, not as top-level rows. Coupler.io does not currently expand variations into individual rows. If you need variation-level data, consider using the Orders with line items entity, which includes the specific variation purchased in each order.

Custom fields or plugin-specific data is not appearing

Custom meta fields added by third-party plugins (e.g., WooCommerce Subscriptions, WCMP Multi-Vendor, custom checkout fields) are not part of the standard WooCommerce REST API response and are not exported by Coupler.io. This is a WooCommerce API limitation. If you need this data, check whether the plugin exposes its own REST API endpoint.

The Search filter isn't returning expected results

The Search parameter performs an exact match only. For example, searching SMYTH will only return results where that exact string appears — partial matches won't work. Make sure you're entering the full, exact value. For orders, you can search by customer name or line item title.

Permission errors

API key doesn't have the right permissions

If you generated an API key with Write or No access permissions, Coupler.io won't be able to read your data. Go back to WooCommerce → Settings → Advanced → REST API, edit your key, and set permissions to Read. Then reconnect in Coupler.io.

Data discrepancies

Sales report numbers don't match the WooCommerce dashboard

The Report: Sales report entity reflects the same data as the WooCommerce built-in reports, but results depend on the period selected. Make sure the period in your data flow matches what you're comparing in the dashboard. If you're using a Custom period, use the date picker carefully — the report is inclusive of the start date and exclusive or inclusive of the end date depending on WooCommerce's rounding.

Timestamp fields cause errors in BigQuery

WooCommerce date fields are returned as strings in ISO 8601 format. BigQuery's schema autodetection may fail to parse them as timestamps in some cases. If you see a "could not parse as timestamp" error, cast the field explicitly in BigQuery using PARSE_TIMESTAMP or adjust the column type in your BigQuery table schema.

Rate limits and timeouts

Data flow times out on large stores

If your store has tens of thousands of orders or products, the WooCommerce REST API may take too long to respond and cause a timeout error. To work around this, use the After date and Before date filters to split your export into smaller date ranges. You can create multiple sources within one data flow and use the Append transformation to combine them.

"Maximum number of columns" error

Coupler.io has a limit of 2,000 columns per data flow. If your WooCommerce data includes many nested or metadata fields, you may hit this limit. Use the Columns setting in the data flow to specify only the fields you need, which reduces the column count and improves performance.