4 posts tagged with "Customs"

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.

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.