Disclosure: this article contains an affiliate link. If you buy hosting through it we may earn a commission, at no extra cost to you. We only recommend what we already run for clients.
Most Sendcloud WooCommerce integration problems are not Sendcloud’s fault, and they are not really WooCommerce’s fault either. They happen because four settings on the WordPress side quietly block the connection, and nothing in the interface tells you which one. We set this integration up regularly for Dutch stores, and the same handful of causes come back every time: plain permalinks, HPOS without compatibility mode, a store still behind a coming-soon page, and API keys created read-only.
This guide covers the current V2 integration, what actually happens inside your site when you connect it, and the failure modes that will cost you an afternoon if you meet them cold.
First: V1 is dead, use V2
Sendcloud has two generations of WooCommerce integration. V1 is deprecated and no longer maintained or updated — Sendcloud’s own support confirms this to merchants who reinstall it. Everything below assumes WooCommerce V2, delivered by the free Sendcloud Shipping plugin on WordPress.org (version 1.0.33 at the time of writing, released 28 July 2026, 5,000+ active installations, tested up to WordPress 7.0.4, PHP 7.0 or higher).
Worth knowing before you commit: that plugin sits at roughly 2.8 out of 5 stars. The praise is genuine and so are the complaints. We come back to those at the end, because you should decide with your eyes open.
Four pre-flight checks that prevent most failures
Do these before you touch the Connect button. Each one maps to a support ticket we have watched somebody else open.
- Permalinks must not be “Plain.” Go to Settings → Permalinks and pick anything else — Post name is fine. With Plain permalinks the Connect button in the Sendcloud integration screen stays greyed out and gives you no explanation.
- The store must be live. A site still sitting behind a coming-soon or under-construction screen cannot complete the handshake.
- HPOS needs compatibility mode. Check WooCommerce → Settings → Advanced → Features. If High-Performance Order Storage is on, compatibility mode must also be on, or Sendcloud simply cannot retrieve your orders. This one is silent: the integration connects, then imports nothing.
- API key permissions must be read/write. Read-only keys let the connection form succeed and then break the importer.
If you are also mid-way through a payments setup, get that finished first — our Mollie WooCommerce setup guide covers the equivalent pre-flight work on the payment side. Debugging shipping and payments simultaneously is a false economy.
Connecting the integration
The flow starts on the Sendcloud side, not in WordPress:
- In the Sendcloud panel, go to Settings → Integrations, find WooCommerce V2, and click Connect.
- In WordPress, go to Plugins → Add Plugin, search for “Sendcloud”, then Install Now and Activate. Installing from the WordPress directory is cleaner than uploading a zip, because you keep automatic updates.
- Go to WooCommerce → Sendcloud Shipping. Tick the checkbox to enable the Connect button, then click it.
- A new tab opens asking for your Sendcloud credentials. Enter them, and you land back in the Sendcloud panel.
- Confirm the result under Settings → Integrations. If the integration is not listed there, it did not connect, regardless of what WordPress shows you.
What Sendcloud silently creates in your site
This is the part that surprises people during a security review, so know it in advance. A successful connection creates two things in your WordPress install:
- A user called sendcloud_api with the Shop manager role.
- A webhook called Sendcloud Update Order listening on the
order.updatedtopic, delivering to a URL shaped likehttps://woocommerce.eu-central-1-0.sendcloud.com/v1/webhooks/fetch_order/<6-digit integration ID>.
Neither is a problem — the webhook is what makes orders sync when an address or status changes rather than on a slow poll. But if you audit users or webhooks, or if a security plugin flags an unexpected shop manager account, that is what it is. Do not delete either one and then wonder why syncing stopped.
Shipping zones, rates and service points
Sendcloud does not create your shipping methods for you. Set them up in WooCommerce → Settings → Shipping → Add shipping zone, name the zone, pick the regions, then add methods: flat rate, free shipping, or local pickup. Split domestic from international into separate zones from day one — retrofitting that split once you have live orders and tax rules is far more work than doing it up front.
For pickup points, enable service points in the Sendcloud panel under Integrations → WooCommerce, then enable Service Point Delivery for the relevant zones in WooCommerce. Verify it on the front end: customers should see a Service Point Delivery option with a Select Service Point button. For a Dutch store this is usually the whole reason for the integration — PostNL and DHL pickup points are what customers expect.
Note the block checkout caveat. The plugin added block-based checkout compatibility in version 1.0.16 and has patched service point behaviour several times since. If your service point selector does not render, check whether you are on the block checkout and whether the plugin is current before you blame anything else. The same rule applies to gateways — see our seven WooCommerce checkout fixes for the order we work through.
Product data you will need for international shipping
Two fields matter and both live in the product data box:
- EAN — under Product data → Inventory. WooCommerce 9.2 and above has a native EAN field; below that, use the “EAN by Sendcloud” field the plugin adds. Most stores are well past 9.2 now, so use the native one.
- HS code and country of origin — under the Shipping tab. Skip these and non-EU shipments will stall in customs paperwork.
The failure modes worth knowing about
Being straight about this is more useful than a clean five-star writeup:
Admin-screen server load. Merchants have reported the plugin’s admin configuration page polling heavily via admin-ajax.php, producing measurable server load and 504 gateway timeouts for shoppers while that screen sits open. The practical mitigation is simple — do not leave the Sendcloud settings page open in a tab all day on a shared host.
WPML and missing orders. If you run WPML and orders placed in a non-default language never reach Sendcloud, set Orders (shop_order) to Not Translatable under WPML → Settings → Post Type Translation. Customers can still check out in any language; the orders just become visible to the integration.
Delayed order import. Aggressive full-page or object caching in front of the REST endpoints will serve Sendcloud stale order data. Exclude the API routes from cache.
Third-party plugin conflicts. Sendcloud has formally limited support for third-party plugins and custom themes. If labels will not generate, orders will not sync, or the service point selector disappears, the expected debugging path is yours: disable other plugins, retest, and take it to the conflicting plugin’s author.
The “API is not active” error. This is a leftover from older plugin versions that depended on WooCommerce’s Legacy API. The current plugin does not need it. The fix is not to re-enable Legacy API — it is to disconnect any stray integrations in Sendcloud, fully uninstall the old plugin, install the current version, and reconnect.
Where hosting actually matters here
Three of the problems above — 504s under polling load, delayed imports, and webhook deliveries that time out — are hosting-shaped problems wearing a plugin costume. A store on cheap shared hosting with a low PHP worker count will hit all three sooner. If your host is the constraint, Cloudways is what we run for client WooCommerce stores; we compared it head-to-head in Cloudways vs SiteGround for WooCommerce, and the same headroom that keeps checkout responsive is what keeps a chatty shipping integration from taking the site down. Pair it with the free fixes in our guide to speeding up a WooCommerce store before you spend anything.
On cost: Sendcloud has a free tier and several paid plans, and the paid plans add a small per-label processing fee on top of the carrier rate. Published figures vary between resellers and regions, so check the current numbers on Sendcloud’s own pricing page for your country rather than trusting a comparison site — including this one.
In short
The Sendcloud WooCommerce integration is quick when the groundwork is right and maddening when it is not. Fix permalinks, confirm the store is live, turn on HPOS compatibility mode, and use read/write API keys — then connect from the Sendcloud panel, not from WordPress. Know that a sendcloud_api shop manager account and an order webhook will appear, and leave them alone. Everything after that is shipping zones and product data.
Need this set up properly? Intec Infosys handles WooCommerce development, shipping and payment integrations, and the unglamorous debugging that follows. Get in touch at intecinfosys.com.
Plugin version, setup steps and troubleshooting behaviour checked against Sendcloud’s official documentation and the WordPress.org plugin listing in August 2026.
