๐Ÿ“ฆ Shipping Order Processing

There are two main options how to integrate the shipping order and label creation into your shipping process. This decision is crucial for which API calls you are implementing.

Option 1:

  • You can create data for all physical packages first and then print all labels at once at the end of the packing process.

Option 2:

  • Or you can print labels one by one per package, i.e. as soon as the first package is physically created, a label can be be printed, then second package, second label etc.. The shipment will be left open for further package processing during the day. Finally, with the last package or a separate API call the shipment needs to be closed.
  • Prerequisite is single-package handling being activated in the account setup of the carrier configuration. You configure the so-called single package handling under Carrier configurations โ€“ Accounts โ€“ Single pkg. handling field group: enable option. If this option cannot be activated, it is not supported by the interface of the carrier.

Printing labels at once at the end of the packing process

Use case

In some cases, processes allow that all shipping data is available and finalized. No changes are expected anymore.
This provides an easy context and makes it possible to ship by just sending one API call. With this one call you can create the shipment, include packages and items, complete the shipment, and request documents to be returned in the response.


  • The overall number of packages is already known when you start printing labels. It is possible to print total values on the labels, e.g. "1 of 5", "2 of 5" as package counter or even total weight of the shipment.
  • This is often preferred by the carriers, especially LTL carriers.

Overview of the necessary API calls

createShipment: create shipment containing all packages, request all label documents, parameter doCompletion = true

Printing labels one by one per package

Use case

Many of our customers know very early in the shipping process where and with which carrier (and service) they want to ship. However, they may know only very late the details like the total number of packages, exact total weights, dimensions, etc. Once each of the packages is ready, it is processed and the label should be printed. The shipment remains open until the very last minute for further packages to be added.
You simply need to create the shipping order with createShipment, add the packages with processShipment, and once you are done send another processShipment to complete the shipping order. You can also complete the shipping order with the last package, i.e. with the last processShipment call.


  • Allows you to add packages one by one to the shipping order. Therefore, you can delete packages or repack them easier, without cancelling the whole shipping order.
  • You get labels right away (no need to buffer or risk of having unlabeled packages)
  • You will not be able to print total values on the labels, e.g. "1 of 5", "2 of 5", except you know the total package number or total weight of the shipment already with the first package.

Overview of the necessary API calls

  1. createShipment: create shipment without packages or with only the first package
  2. n times: processShipment: add a package, request label documents
  3. When shipment status in ERP is closed, then processShipment with paremeter doCompletion = true

Whatโ€™s Next