14 posts tagged with "Shipments"

You can now request a specific DPI for ZPL labels via a new optional label_dpi query parameter on GET /shipments/{id}/labels.

Supported Values​

• 200
• 300

If label_dpi differs from the shipment's saved label DPI, the label is converted on the fly. If it matches, the label is returned unchanged. This only applies to ZPL formats; other formats ignore the parameter.

For detailed information, see the Shipments API reference.

It is now possible to upload your own documents such as proforma or commercial invoices when creating shipments. The documents will be forwarded to the given carrier, but currently the option is only available for select carriers.

Check the Document Upload guide for full details on how to upload your own documents.

When shipping ADR goods, the gross weight of the goods is now available to define explicitly. This can be done by using the new field gross_weight in the dangerous_goods array.

Find the full specification for the new field in our API Reference - Create a Shipment.

Check the Dangerous Goods / Limited Quantity for full details how to ship ADR goods.

If you need to ship lithium batteries by air, under IATA Dangerous Goods Regulations Section II or IB, you can now book them with Shipmondo. This can be done by using the new service codes IATA_II and IATA_IB. Check the Dangerous Goods / Limited Quantity for full details on requirements

Currently, these services are available for DHL Express and FedEx. We expect to add support on multiple carriers soon. Follow the progression on Product news

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.