At a glance
Share of Sendle label and order-creation requests that returned a usable shipping label on the first call over the trailing 24 hours. This is a despatch-bench health metric: when label creation fails, parcels cannot be booked, the pick-pack queue stalls and orders silently miss their dispatch cutoff. The card warns at <98%, a deliberately tight floor because even a 2 percent failure rate on a busy despatch morning means dozens of orders waiting on a manual retry.
What it tracks
Label Generation Success isCOUNT(successful label/order creations) / COUNT(label/order creation attempts) over the rolling 24-hour window, measured against the Sendle Orders API order-creation endpoint (POST /api/orders), which returns the parcel booking together with its label URL. A request fails when Sendle rejects it (invalid or out-of-zone destination address, missing weight or dimensions, an unservicable postcode, or an authentication or rate-limit response) and no label is produced. A sustained dip is usually one of three things: malformed address or weight data flowing from the store, an expiring API credential (cross-check Days to Token Expiry), or a Sendle-side incident (cross-check API Error Rate). Because label creation sits at the very front of the despatch flow, a failure here pushes orders straight into a missed dispatch cutoff, so this card is an early warning ahead of Late Shipments. The <98% alert is the cue to check whether the cause is your data, your credential or Sendle’s platform before the despatch bench backs up.