Print shipping labels from your application
CloudPrint prints a shipping label that your carrier, marketplace or shipping system has already generated. It does not buy postage, choose a carrier or create tracking numbers; its job is to deliver the final PDF or ZPL to the correct local printer and report the result.
Where label generation ends and printing begins
First create or purchase the shipment through the carrier or shipping API and obtain the final label. Then pass that PDF, public HTTPS download URL or ZPL payload to CloudPrint. Keeping this boundary explicit prevents an integration from expecting carrier rates, tracking or label creation from the printing API.
Choose PDF or ZPL
PDF is portable and easy to preview, but the target queue needs system printing or a supported renderer. ZPL is efficient for compatible Zebra printers and preserves device-level control, but it requires document_format=raw, document_raw_language=zpl and a printer that advertises ZPL RAW passthrough.
Route each packing station
During warehouse setup, assign a stable printer_id to each packing station or shipping workflow. Display the queue name for people, but route by ID. If that printer is offline, stop and show a clear fallback choice rather than silently sending a customer label to another location.
Match media and barcode quality
Set the document page to the real label dimensions and, when needed, request matching media_width_mm, media_height_mm and dpi. Calibrate gap or mark sensing, darkness and speed on the physical printer. A successful API status cannot compensate for a clipped or unreadable barcode, so scan production samples before rollout.
Make retries and reprints auditable
Build the Idempotency-Key from shipment ID, label type and operation version. A timeout retry keeps that key. A deliberate second copy gets a new key and records the operator and reason. Test agent shutdown, an offline printer, empty media and workstation restart before enabling unattended printing.
Production checklist
- Validate document format, page size and orientation before creating the job.
- Calibrate the label size and verify the installed printer driver and queue.
- Store the stable printer identity instead of relying only on a display name.
- Handle terminal status, retry policy and duplicate-print protection explicitly.