Sendcloud incident

Third-party issue: [GLS NL] - Label announcement issues | Problemen met het voormelden van de labels | Problème de création d’étiquettes

Minor Resolved View vendor source →

Sendcloud experienced a minor incident on February 13, 2026 affecting BE and NL, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2026, 01:23 PM UTC
Resolved
Feb 13, 2026, 01:23 PM UTC
Duration
—
Detected by Pingoru
Feb 13, 2026, 01:23 PM UTC

Affected components

BENL

Update timeline

  1. investigating Feb 12, 2026, 12:58 PM UTC

    Status: Investigating We are currently experiencing an issue affecting some users shipping with GLS Netherlands (GLS NL) via a direct contract. When creating a label with the GLS Point Delivery shipping method, label creation can fail with this error: “No ParcelShop found with ParcelShopId … ; please verify the service point ID.” The carrier has confirmed a malfunction on their side and is currently working on a fix. We onderzoeken momenteel een probleem dat sommige gebruikers treft die verzenden met GLS Netherlands (GLS NL) via een direct contract. Bij het aanmaken van een label met de verzendmethode GLS Point Delivery kan het aanmaken van het label mislukken met de volgende foutmelding: “No ParcelShop found with ParcelShopId … ; please verify the service point ID.” De vervoerder heeft bevestigd dat er een storing aan hun kant is en werkt momenteel aan een oplossing. Nous enquêtons actuellement sur un problème affectant certains utilisateurs expédiant avec GLS Netherlands (GLS NL) via un contrat direct. Lors de la création d’une étiquette avec la méthode d’expédition GLS Point Delivery, la création de l’étiquette peut échouer avec le message d’erreur suivant :"No ParcelShop found with ParcelShopId … ; please verify the service point ID." Le transporteur a confirmé un dysfonctionnement de son côté et travaille actuellement à sa résolution. Affected components NL (Operational) BE (Degraded performance)

  2. investigating Feb 12, 2026, 01:07 PM UTC

    Status: Investigating We are continuing to investigate this issue. Affected components NL (Operational) GLS Netherlands (Degraded performance) BE (Degraded performance) GLS (Degraded performance)

  3. identified Feb 13, 2026, 08:37 AM UTC

    Status: Identified The carrier has confirmed a malfunction on their side and is currently working on a fix. Affected components GLS Netherlands (Degraded performance) BE (Degraded performance) GLS (Degraded performance) NL (Operational)

  4. resolved Feb 13, 2026, 01:23 PM UTC

    Status: Resolved This incident has been resolved. Affected components GLS (Operational) NL (Operational) GLS Netherlands (Operational) BE (Operational)