New shipping order statuses in Carrier Connect: Integration in getShipments/synShipments API

We have introduced two new statuses in Carrier Connect:

• Ready to assign pickup (RDYFORDISPOSE, 450)
• Ready for shipping (RDYFORSHIPPING, 550)

• You can find a complete overview of all statuses and their IDs in the user guide: Which statuses can a shipping order have?

How do you benefit from the new statuses?

The two statuses "Ready to assign pickup (RDYFORDISPOSE, 450)" and "Ready for shipping (RDYFORSHIPPING, 550)" create scope for decoupling operational processes and controlling them in terms of time, for example:

Decoupling data transfer vs. document upload

Depending on the implemented and configured interfaces, you can first transfer shipping order data to the transport service provider and then upload documents in the next step.

HAWB number for air freight

Some document uploads require a HAWB number generated by the transport service provider. With the two statuses, Carrier Connect with the Carrier Event Service option can wait for the response from the transport service provider, extract the HAWB number from event data, and then trigger the document upload.

More flexibility for mandatory fields

Requirements that are only relevant later in the shipping process (e.g. for EDI or document upload) can be requested more specifically in future by Carrier Connect.

Possible impacts with the implementation of the service pack from August 2025 and activation of the new status chain

With the introduction of the two new statuses, it may happen that queries of the "getShipments" interface, which today filters exactly for COMPLETE (400) or DISPOSED (500), no longer return any matches. Corresponding consignments now automatically reach the status RDYFORDISPOSE (450) or RDYFORSHIPPING (550).

Possible solution

• To avoid failures, we have provided you with the client-specific compatibility option Old SO status chain as a temporary workaround to allow you preparation time for the changeover (User administration – Clients - Clients – Select and open client – Package processing sheet – General settings).
• We recommend that you adapt the getShipments API and switch to the new status chain:
  • Include the new statuses "Ready to assign pickup, RDYFORDISPOSE, 450" (instead of "Ready to assign pickup, COMPLETE, 400") and "Ready for shipping, RDYFORSHIPPING, 550" (instead of "Assigned, DISPOSED, 500") in the boStatusIdentCode filter.
  • If you use follow-up processes based on the reported boStatus in the getShipments response, integrate the new statuses here too.
  • Check other subsequent processes and adjust them if necessary.

• Here you can find the API documentation for getShipments and syncShipments.