10 posts tagged with "Shipments"

unit is an new optional field which has been added to the customs.goods array in Shipment creation requests. This field allows you to specify the unit of measurement for the quantity of goods in your customs declarations.

Supported Units​

• piece (pieces) - default value
• m2 (square meters) - UPS shipments only for now

We expect to add support for more units in the future, on multiple carriers. Follow the progression on Product news

To support the new parties and customs fields introduced in Shipmondo, File integration on the Print Client has been updated accordingly.

These updates align with the recent changes to the Shipments API.

For details about the new and deprecated fields, please refer to the Changelog: Shipments - Parties and customs.

The updates to File integration apply to both JSON and XML files.

In a greater effort to improve customs in Shipmondo, a number of fields have been introduced to shipments:

• parties array
• pickup_details object
• delivery_details object
• service_point_id string
• customs > freight_cost float
• customs > insurance_cost float

At the same time a number of fields have been deprecated:

• sender object
• receiver object
• pick_up object
• bill_to object
• service_point object
• return_to object
• customs > billed_to_custom_invoice_text string
• customs > sender_custom_invoice_text string
• customs > receiver_custom_invoice_text string

There are no current plan to remove these fields, but it is recommended to stop using them from now on, as new features will only be added to parties.

Guides​

Check out the new guide for parties for further details of the structure of parties.

Also check out the new guide for migration to parties from the deprecated address objects.

Also check out the updated API reference for reference of the structure of each new field.

We have introduced customer_number on shipment responses.

customer_number allows you to identify the shipping agreement used for the shipment(s).

The field is available on all response bodies representing shipments. e.g. List all shipments

Since we have introduced Sandbox environment, we have decided to deprecated test_mode on the POST /shipments endpoint.

The date of removal of test_mode is yet unknown, but we highly encourage you to stop using this parameter and use the Sandbox environment instead.

Example​

Before​

POST https://app.shipmondo.com/api/public/v3/shipments

{
  "test_mode": true,
  "product_code": "PN_MC",
  ...
}

After​

POST https://sandbox.shipmondo.com/api/public/v3/shipments

{
  "product_code": "PN_MC",
  ...
}

We have introduced a new field named internal_reference on the parcel objects.

internal_reference allows you to assign a reference to track and identify each parcel within your shipment.

You can specify this field in the request body when creating a shipment. It will be stored with the parcel object and accessible via the API.

We have introduced a new field called additional_reference for shipments.

additional_reference allows you to specify a secondary reference when creating a shipment. This field is optional and can be used to provide additional information or identification for your shipment.

The additional_reference field is introduced at every endpoint relevant to shipments. For more details, please refer to the API Reference.

Note: Unlike reference, additional_reference is not guaranteed to be printed on the label.

We have introduced a new parcel field called stackable for shipments. As of now, this field is relevant for those booking DHL Freight Sweden shipments with the following product codes:

DHLFSE_EUC
DHLFSE_S
DHLFSE_PT
DHLFSE_EUL
DHLFSE_HD
DHLFSE_HDR

stackable allows you to specify whether an individual parcel can be stacked, providing more flexibility and efficiency in handling your shipments. stackable defaults to true if not specified.

The stackable field is introduced at every endpoint relevant to shipments. For more details, please refer to the API documentation.

A new API endpoint has been introduced, enabling creation of shipment for specific a fulfillment.

The reference for the endpoint can be found here API reference - Fulfillment create shipment.

We are introducing a series of updates to our API responses and requests, specifically targeting shipment payloads. These changes are aimed at improving data consistency and ensuring clearer documentation for developers. Here’s a breakdown of the changes you need to be aware of: