At a glance
Share of Shippo label-purchase requests that returned a valid shipping label (transaction statusSUCCESSwith a populatedlabel_url) rather than an error, over the trailing 24 hours. This is the despatch desk’s heartbeat: when label generation stalls, parcels cannot leave the building and the dispatch SLA clock keeps running.
What it tracks
This card reads Label Generation Success for the selected period over a rolling24H window. The denominator is every Shippo transaction request (a label purchase against a selected rate); the numerator is the count returning transaction status = SUCCESS with messages empty and a label_url populated. Failures surface as transaction status = ERROR with carrier-returned messages, most often invalid or undeliverable address, carrier account inactive or unauthorised, insufficient postage balance, or an upstream carrier API timeout. Because Shippo brokers labels across many carriers, a dip here is usually carrier-specific or credential-specific rather than a Shippo-wide outage, so read it next to Label Failure Rate by Carrier to see which carrier credential needs attention, and API Error Rate to separate carrier rejections from transport-layer 5xx errors. The alert fires below 98%, because even a 2% failure rate on a busy despatch morning leaves dozens of parcels stuck in the queue. A sustained drop also feeds the real-time Label Print Failures Spike alert, which pages the despatch team within the hour.
Reconciling against the source
Compare against the Shippo dashboard Shipments view, where failed transactions are flagged, and against the Shippo transactions list in the API (count wherestatus is not SUCCESS). Carrier-side rejections also appear in each underlying carrier’s own shipping portal; Shippo records transaction timestamps at request time in carrier-local time, so a 24-hour reading can shift slightly against a portal reporting in a different timezone.