A new optional attributes entry, eori, is now supported on the receiver and importer parties
for PostNord shipments that require customs. It lets you declare the
buyer's EORI number, and it is sent on to the carrier with the customs documentation.
The customs product identifiers m_pid, ns_pid and s_pid on objects in the customs.goods
array are now also supported for PostNord and Bring, and are passed on to the carrier.
A new optional attribute is now supported on shipments booked with DSV Road products.
It is declared through the existing attributes arrays:
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 DSV as a single number.
For parcels where no 'pallet_places' is indicated, the default value of 1 per colli is used, which is how it has been calculated in the past.
Parcels with more than one quantity act as a multiplier for the indicated 'pallet_places', meaning that the below example would result in a total of 3.0.{
...
"parcels": [
{
"weight": 250000,
"quantity": 2,
"attributes": [
{ "name": "pallet_places", "value": "1.5" }
]
}
],
...
}
Find the full specification in our Shipments API reference.
A new optional attributes entry, nuf, is now supported on the importer party for shipments to
Norway. It lets you declare the Norwegian NUF number (Norwegian-registered foreign business) that
customs and VAT should be billed to, and it is sent on to the carrier with the customs
documentation.
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.
We have introduced two new endpoints that allows you to hold (pause) and unhold (resume) sales orders.
We have introduced two new endpoints:
GET /statistics/invoices — aggregated statistics for your invoices and credit notes, e.g. spend by category, and net/VAT/gross totals.GET /user_ledger_entries — your account statement: individual balance movements (refills, charges) with a running balance.See the API reference for /statistics/invoices, and here for /user_ledger_entries.
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.
You can now request a specific DPI for ZPL labels via a new optional label_dpi query parameter on GET /shipments/{id}/labels.
200300If 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.
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.