Skip to main content

16 posts tagged with "Shipments"

View All Tags

DACHSER - Pallet places, goods groups and order groups

· One min read

Four new optional attributes entries are now supported on shipments booked with DACHSER products. They are declared through the existing attributes arrays:

  • order_group (shipment level) - free text.
  • goods_group and goods_group_quantity (parcel level) - these two belong together. If only one of them is given on a parcel, the shipment is rejected with an error naming the missing field.
  • pallet_places (parcel level) - accepts up to two decimals (e.g. 0.25 for a quarter pallet). Values are summed across all parcels and sent to DACHSER as a single number. If no parcel declares the attribute, nothing is sent - so declare 0 explicitly if you want to report zero pallet places.
{
  ...
  "attributes": [
    {
      "name": "order_group",
      "value": "A"
    }
  ],
  "parcels": [
    {
      "weight": 250000,
      "attributes": [
        { "name": "goods_group", "value": "B" },
        { "name": "goods_group_quantity", "value": "2" },
        { "name": "pallet_places", "value": "1.5" }
      ]
    }
  ],
  ...
}

DACHSER expects specific values in goods_group and order_group - agree these with DACHSER, as Shipmondo does not validate them.

Find the full specification in our Shipments API reference.

Customs product identifiers - M-PID, NS-PID and S-PID

· One min read

The EU has introduced a requirement to provide product identifiers for goods imported into the EU. New attributes entries are now supported on objects in the customs.goods array, letting you declare them: m_pid (assigned by the seller or platform), ns_pid (a non-standardised manufacturer identifier) and s_pid (a standardised manufacturer identifier, such as an EAN or ISBN).

Product identifiers are accepted today for DHL Express, FedEx, UPS and unspecified-carrier shipments, with a couple of carrier-specific requirements. See Product identifiers (PID) for EU import for the full details.

Request a specific label DPI - new query param for Labels

· One min read

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.

Upload Documents

· One min read

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.

IATA - Lithium Batteries shipped by air

· One min read

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

Customs goods unit - new field for Shipments

· One min read

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

Parties and customs - File integration

· One min read

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.

Shipments - Parties and customs

· 2 min read

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.