Skip to main content

2 posts tagged with "Customs"

View All Tags

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 stucture of each new field.