Skip to main content
Create Shipment only saves a Pending shipment. Send Shipment books it with the carrier, creates the Label, and uses a billable shipment on your plan. There is no confirmation dialog and no extra form: you review the overview, then click the header button. Walkthrough with printing: Labels and printing. Creating the pending row: Create a shipment.
Send Shipment and Send order book a live label on your carrier account and count toward Shipments this period. Do not send until addresses, weight, product, and (if required) service point are correct. You cannot edit a shipment the same way after it is Dispatched.

​
Send Shipment vs Create Shipment

​
What to confirm before you send

Open Shipments, click the Pending row. Header action: Send Shipment. Review Overview (there is no second step): Shipment Information Carrier Information — Carrier, Product, Services (pencil while pending/draft/error). Apply a shipping rule if the Shipping rule card still says Manual setup. Addresses — Sender, Receiver, and Service Point when the product needs one. Shipment parties, Pick a service point. Package Details — weight, dimensions, order lines (including Country of origin and Tariff). Customs and documents. Printer settings / Shipping rule — only on Draft or Pending. Optional; labels still generate without a printer.
Pending shipment detail with Send Shipment in the headerPending shipment detail with Send Shipment in the header

Pending shipment — Send Shipment in the header books the carrier with no extra confirm step

1

Open the pending shipment

Status must be Pending. Draft is not sendable until it is pending.
2

Check overview

Parties, product, parcels, printers, service point. Fix data while you can still edit.
3

Click Send Shipment

The button reads Sending… and is disabled while the request runs. On success: toast Shipment sent successfully, status Dispatched, Send Shipment disappears, Documents gets a Label.

​
When the button shows or hides

Create Return Shipment can appear on a Dispatched Outbound shipment when the rule has a return rule and auto-create is off — that is not send. Inbound and returns.

​
Send order (batch)

When an order already has shipments, the order header action is Send order (not Create Shipment). It books every Pending or Error shipment on that order in one request.
  • Disabled with tooltip No shipments ready to send when nothing is sendable
  • Label while working: Sending…
Toasts: Each shipment card also has Send / Sending… for a single row (orders.shipment-send). Same booking path as Send Shipment.
Order Shipments tab with Send order in the header and a pending shipment cardOrder Shipments tab with Send order in the header and a pending shipment card

Send order books every Pending or Error shipment on the order; each card also has Send

There is no separate “batch send” screen on the shipments list. Multi-send is Send order (or the public API batch send).

​
Retry Send, errors, Request Logs

If the carrier rejects the booking, status becomes Error. Header: Retry Send. Banner title: Shipment failed to send. Each error line is the localized code first (so “Invalid Refresh Token” from a carrier becomes a credential fix), then (CODE), then the carrier’s own message underneath when it differs.
Shipment error banner Shipment failed to send with Retry Send in the headerShipment error banner Shipment failed to send with Retry Send in the header

Retry Send after a failed booking — Shipment failed to send with the reason and Request Logs

Common send failures: Fix the data, then Retry Send. A successful retry still uses a credit. Void/cancel-label is not on this screen — Hold, cancel, or delete.

​
Request Logs

Request Logs sits on the error banner (and on the right of Overview when there are logs but no errors). Hidden when logs is empty. Modal title: Request Logs. Subtitle: Request and response data for debugging. Close: Close. Each entry: Plus endpoint, duration in ms, HTTP status badge (destructive if error or status ≥ 400). Expand for Error, Request JSON, Response JSON, and timestamp.
Request Logs modal with request and response data for debuggingRequest Logs modal with request and response data for debugging

Request Logs lists Client, Zippendo API, and Carrier API calls with status and expandable JSON

​
Credits

Each successful send (including Retry Send that succeeds) counts as one shipment on the plan. Download or Print of an existing label does not. Settings → Pricing (team switcher Manage) → Current Usage:
  • Title: Current Usage
  • Shipments this period with / shipments used
  • Allow overage shipments — when off, sending pauses at the included cap; when on, extras are billed as overage
Settings Pricing Current Usage with Shipments this periodSettings Pricing Current Usage with Shipments this period

Current Usage counts sent shipments, not label downloads

Next: Labels and printing and Customs and documents.