Shipment Connector

Release note - October 2026

Shipment Connector for Business Central Cloud

Released version: 5.10.0.0

Changes in this release

[Fix] Warehouse Shipments No Longer Create a Duplicate Waybill on the Source Document

Creating a Warehouse Shipment multiple times from the same Sales Order or Transfer Order no longer results in an extra, incorrect waybill on the source document itself.

What has been done:

Fixed an issue in Shipment Core where running “Create Warehouse Shipment” more than once for the same Sales Order or Transfer Order could cause a waybill to also be created directly on the order, in addition to the one on the resulting Warehouse Shipment
The system now checks whether a Warehouse Shipment (and its waybill) already exists for the order before creating a new one

Usability notes:

Re-running “Create Warehouse Shipment” on an order will no longer leave behind a stray, duplicate waybill on the order
Reduces the risk of confusion or incorrect shipments caused by having two waybills in play for the same order

[Update] Validation Removed for Currency Code on Customs Lines

Customs Lines no longer require the Currency Code to match a value already known to the system.

What has been done:

Removed the built-in validation check on the Currency Code field on Customs Lines

Usability notes:

Prevents unnecessary validation errors on Customs Lines when a currency code is used that the system would otherwise have rejected
No action is required — the field still works as before, just without the extra validation step

[Update] Expanded Regional and Platform Support

Shipment Core has extended its regional coverage and underlying platform support.

What has been done:

Added support for France
Upgraded Shipment Core’s base platform to Business Central 28

Usability notes:

Customers operating in France can now use Shipment Connector
Ensures Shipment Core stays current and fully compatible with the latest Business Central Cloud releases

[Update] Journal Customs Lines Now Use the Same System as Waybills

This change applies specifically to the nShift Ship connector.

Customs lines created from a Shipment Journal are now handled with the same customs system already used for regular waybills.

What has been done:

Changed the customs line handling on Shipment Journals for nShift Ship to use the same Customs Line system as waybills, instead of a separate, journal-specific structure

Usability notes:

Customs information entered on journals is now handled consistently with waybills, reducing the risk of differences between the two flows
No action is required — existing journal customs data continues to work

[Fix] Converting a Device Request to a Shipment Journal No Longer Fails for Long Service Codes

This fix applies specifically to the Shipmondo connector.

Converting a Device Request into a Shipment Journal no longer fails when a service has a code longer than 20 characters.

What has been done:

Fixed an error that occurred when converting a Device Request to a Shipment Journal if one of the services involved had a code longer than 20 characters
The conversion now looks up the service using its full Shipmondo code instead of the shortened Code field

Usability notes:

Device Requests can now always be converted to Shipment Journals, regardless of how long the underlying Shipmondo service code is
No action is required — the fix is applied automatically

[Update] Comments Can Now Be Sent with Shipments

This change applies specifically to the nShift Webshipper connector.

A comment can now be included when sending a shipment to nShift Webshipper.

What has been done:

Added a new “Comments” property to the shipment data sent to nShift Webshipper, populated from the waybill’s Receiver Description

Usability notes:

Any text entered in the Receiver Description field on the waybill is now passed along to nShift Webshipper as a comment on the shipment
No setup is required — this happens automatically whenever a Receiver Description is filled in

[Fix] Redownloading Platform Data No Longer Resets Existing Additional Services

This fix applies specifically to the nShift Webshipper connector.

Redownloading platform data from nShift Webshipper no longer overwrites information you’ve already customized on Additional Services.

What has been done:

Fixed an issue where redownloading platform data could reset the Name, Shipment Code, Attribute Name, and Attribute Type on existing Additional Service entries back to their default values
These fields are now only set the first time an entry is created, and are left untouched on subsequent downloads if they already contain a value

Usability notes:

Any customizations made to Additional Services will now be preserved when platform data is redownloaded
No action is required — the fix is applied automatically

[Update] New Periodic Shipment Status Report and Updated Address Selection on Journals

This change applies specifically to the nShift Transsmart connector.

The nShift Transsmart connector now includes a report for periodically refreshing shipment statuses, along with a simplified way to select addresses on Shipment Journals.

What has been done:

Added a new report that can be scheduled to periodically download the latest status for shipments from nShift Transsmart
Replaced the separate “Select Sender” and “Select Receiver” actions on Shipment Journals with a single, combined “Pick Address” action

Usability notes:

Shipment statuses can now be kept up to date automatically, without needing to open each shipment manually
Selecting an address on a Shipment Journal is now a single, more streamlined action instead of two separate ones

Upgrade Considerations

Shipment Core has been updated to version 5.10.0.0 — no manual steps are required upon upgrade
The nShift Ship connector has been updated to version 5.10.0.0 — no manual steps are required upon upgrade
The Shipmondo connector has been updated to version 5.10.0.0 — no manual steps are required upon upgrade
The nShift Webshipper connector has been updated to version 5.10.0.0 — no manual steps are required upon upgrade
The nShift Transsmart connector has been updated to version 5.10.0.0 — no manual steps are required upon upgrade
Shipment Core now requires Business Central 28 or newer on Cloud
No breaking changes have been introduced in this release