Skip to main content

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.

New Shopify Shipping Methods API Endpoint and Code Format

· 4 min read

Effective Date: January 15, 2026

Action Required

This change is only relevant and may require action if you are a partner or customer with your own system (WMS, ERP, or OMS solution) that integrates directly with Shopify to fetch orders, and the webshop simultaneously uses Shipmondo's Shopify app to manage their shipping methods.

In these cases, the change may affect how you identify, parse, and handle shipping method data in your system.

On January 15, 2026, we're releasing an update to Shipmondo's Shopify app that introduces a new format for shipping method codes. This change enables advanced shipping configurations for webshops while providing partners with better access to shipping method details via our API.

What's changing?​

New shipping method code format​

The Shipmondo app stores delivery information in the code field of shipping_lines in Shopify orders. We're transitioning from the existing format to a new, more flexible format.

Current format:

dk_gls_service_point_95433
dk_dao_service_point_1250
dk_dao_private

New format:

SHIPMONDO;{method_id};{pickup_point_id}

Example:

SHIPMONDO;12345;95433

Where:

  • SHIPMONDO = prefix for unique identification of the source
  • method_id = unique ID for a shipping method created in the Shipmondo app (e.g., 12345)
  • pickup_point_id = ID for the pickup/service point (optional, depends on the shipping method, e.g., 95433)

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.

Shipments - `test_mode` deprecated

· One min read

Since we have introduced Sandbox enviroment, 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 enviroment 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",
  ...
}

New Parcel field 'internal_reference'

· One min read

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.

info

internal_reference will neither be displayed on any label nor be transmitted to the carrier.

New shipment field 'additional_reference'

· One min read

We have introduced a new field called additional_reference for shipments.

additional_reference allows you to specify a secondary reference when creating a shipment. This field is optional and can be used to provide additional information or identification for your shipment.

The additional_reference field is introduced at every endpoint relevant to shipments. For more details, please refer to the API Reference.

Note: Unlike reference, additional_reference is not guaranteed to be printed on the label.

New parcel field 'stackable' for shipments

· One min read

We have introduced a new parcel field called stackable for shipments. As of now, this field is relevant for those booking DHL Freight Sweden shipments with the following product codes:

DHLFSE_EUC
DHLFSE_S
DHLFSE_PT
DHLFSE_EUL
DHLFSE_HD
DHLFSE_HDR

stackable allows you to specify whether an individual parcel can be stacked, providing more flexibility and efficiency in handling your shipments. stackable defaults to true if not specified.

The stackable field is introduced at every endpoint relevant to shipments. For more details, please refer to the API documentation.