Sendcloud Shipping

The Sendcloud plugin relies on outdated technology that is no longer supported by default in recent versions of WooCommerce. It communicates via the legacy v2 API which has been deprecated for years, and uses admin-ajax.php for continuous polling — an approach that dates back to 2006 and has long been superseded by better alternatives.

In practice, this means the configuration page in wp-admin puts a heavy load on the server as long as it’s open. In our case, this caused measurably high server load and 504 errors for shop visitors — on a server that was otherwise running fine. This is clearly visible in the server logs:

52.58.233.101 - - [23/Mar/2026:14:56:12 +0000] "POST /wp-json/wc-sendcloudshipping/v2/
integration?consumer_key=...&oauth_signature_method=HMAC-SHA256... HTTP/1.0" 504 4227

Every request from Sendcloud results in a 504 Gateway Timeout — caused by the server being overwhelmed by the plugin’s own polling behaviour.

Support offers no real solution and points to workarounds rather than acknowledging the underlying issue. For a paid shipping service used by many webshops, this level of technical quality is simply not acceptable.

Avoid at all costs! I spent over an hour talking to someone who was handling multiple clients simultaneously and kept me waiting for hours. In the end, it turned out the problem was exactly as described at the beginning: I couldn’t connect to Sendcloud! A response in a month!!! Bravo Sendcloud, what customer service!

Purtroppo l’esperienza di integrazione con Sendcloud è stata deludente.

Il processo di installazione è chiaramente legacy e non allineato agli standard moderni di sicurezza e integrazione. Per poter creare i webhook è necessario creare un utente WordPress con ruolo “Gestore negozio”, pratica discutibile e poco sicura, soprattutto in contesti professionali dove l’accesso deve essere minimo e controllato.

Inoltre, l’integrazione entra facilmente in conflitto con Cloudflare: anche una semplice regola di protezione anti-bot è sufficiente a bloccare le comunicazioni, senza che Sendcloud fornisca indicazioni chiare o soluzioni robuste (ad esempio IP allowlist ufficiali, firme dei webhook, token dedicati, ecc.).

Il risultato è che si perdono ore a diagnosticare problemi che non dipendono dallo store, ma da un’architettura di integrazione ormai superata.

Nel 2025 ci si aspetterebbe un collegamento tra store e Sendcloud più semplice, più sicuro e più pratico, senza dover abbassare le difese del sito o creare utenti con privilegi elevati solo per far funzionare un webhook.

Il servizio in sé può essere valido, ma l’esperienza tecnica di onboarding e integrazione può e deve essere migliorata.

Todo estupendo muchas gracias

# Setup Information:

• Fresh install for testing – no plugin
• WooCommerce: Version 10.2.2
• Sendcloud Shipping: Version 1.0.16
• Theme: Twenty Twenty-Five

—

# Issue:

The plugin and API connection are successful, but Service Point Delivery options are not appearing at checkout. The feature is correctly activated, and this has been confirmed by the Sendcloud support team. Debugging Details:

While debugging, I found that a variable is never initialized in the following file:

sendcloud-connected-shipping/includes/Controllers/Api/class-service-point-controller.php

Specifically, this line seems problematic:

$this->config_service->set_service_point_script( $data['script_url'] );

In the database table ####_sendcloud_configs, the plugin appears to be looking for the value with the key:

SERVICE_POINT_SCRIPT

But this value is never set, so the Service Point script is not being loaded on the frontend.

—

# Current Status:

Awaiting support or further guidance to resolve the issue.