Void Labels and Correct Shipments
Void a label, fix a shipment, and recover from a wrong purchase without paying twice.
Once a label is created, shipment details are locked for edit. If something is wrong, the usual path is void (when allowed), then fix and re-label. This article covers the CLI path.
In this article, we will load a shipment, void a label when needed, reprint without re-purchasing, and note refund honesty.
Real-World Example
We printed a label with the wrong service. We need to void it if the carrier still allows, then ship again with the correct details.
Before We Begin
This article assumes that:
- You have a shipment with a purchased label
- You have read Safety Model
- You have rehearsed once with Test Without Spending
Web app void flows are documented on postsale.com/help. Here we stay on terminal commands.
1. Inspect the shipment
Here's how:
postsale shipments get <shipment_id>
# or all shipments for an order:
postsale shipments get --reference <order_id>Confirm tracking state and that you have the right id before voiding.
2. Void the label, which requests a carrier refund
postsale labels void --shipment-id <shipment_id> --yes
# or
postsale run "void the label on shipment <shipment_id>" --yesPractice first:
postsale run --dry-run "void shipment <shipment_id>"Success looks like a voided label state in the response or agent summary. Carriers can still deny voids (in transit, outside window).
Warning
Void is money-moving. The CLI does not guarantee a refund. Confirm carrier and account rules if money matters.
3. Correct and ship again
Typical pattern:
- Void if needed
- Fix order/shipment details (updates may still write under dry-run; use care)
- Create or rate-shop as needed, then purchase again with
--yes
Follow Ship One Order with the CLI.
4. Reprint without purchasing again
If the label is fine and you only need the PDF again:
postsale labels reprint <shipment_id>
postsale labels reprint <shipment_id> --output ./label.pdfReprint is read-only. It is not a free re-purchase.
Good to Know
| Symptom | Likely cause | What to do |
|---|---|---|
| Exit 64 | Missing --yes | Authorize intentionally |
| Void rejected | Carrier rules | Check tracking; use carrier portal / support |
| Need PDF only | Wrong tool | Use reprint, not purchase |
| Unsure of refund | Carrier-dependent | Do not assume CLI refund success |
Additional Reading
On this page
Related