Packing and Dispatch
Part of Shipping software and carrier integrations
Handling failed label requests
Triage missing data, rejected services, printing failures and uncertain label outcomes while keeping the parcel tied to the correct booking.
When a label request fails, hold the parcel. Establish whether a shipment was created before submitting another request. A visible error may identify missing data or a rejected service. An interrupted response leaves the outcome less clear, so check the platform and carrier records before assuming no booking exists.
Capture the attempt
Keep the order and parcel IDs, carrier account, service, request time, error text and any returned shipment or tracking ID together. Give staff a clear state: no booking found, outcome unknown, booking found but label unavailable, or label ready. These are suggested operating states; platform terminology varies. Keep an uncertain parcel out of carrier hand-off.
Use the returned message to identify the rejected field or service. Compare it with the shipment request and the applicable carrier instructions. Correct only a confirmed issue before retrying.
Choose the next action
| Situation | Check | Action |
|---|---|---|
| Required data is missing | Compare the request with the packed parcel and order | Correct the source value; submit again only after checking for an existing booking |
| Service or package is rejected | Check destination, parcel and service eligibility | Select an approved alternative or hold for a service decision |
| Response is interrupted | Search available shipment and carrier records using the identifiers you have | Retrieve an existing label if found; escalate an outcome that remains unclear |
| Label exists but printing failed | Check the existing shipment and tracking number | Reprint through the platform’s supported workflow |
Not every platform exposes the same identifiers or controls. Use the configured account's procedure for searching, reprinting and retrying.
Common Causes of Failed Label Requests and Actions
- Missing Required DataCheck order and parcel details against shipment request. Correct source values before retrying.
- Rejected Service or PackageVerify destination, parcel dimensions, weight, and service eligibility. Choose an approved alternative or hold for decision.
- Interrupted ResponseSearch shipment and carrier records using identifiers. Retrieve existing label if available; escalate unclear outcomes.
- Label Exists but Printing FailedCheck existing shipment and tracking number. Reprint using platform’s official workflow.
Confirm the final shipment
Check that the final label matches the physical parcel and selected service. If a replacement shipment was needed, record which booking is active. Follow the provider's cancellation or void process for the earlier booking.
A printed replacement does not itself establish that the previous booking was cancelled. Check the earlier booking's status in the configured platform or carrier account. Use that connection's cancellation or void procedure if needed, and keep the confirmation with the exception record.
Keep the original error and correction in the exception record. Review repeated failures by field, carrier and service so an upstream data or rule problem can be fixed.
