Today 13-Aug-2026 we deployed below changes and fixes to our Accept environment.
The release to Production is scheduled Tuesday 18-Aug-2026.

DevDocs changes (nShift Transsmart Developer Documentation)

• We have added chapters 7.11 to 7.15 which are user management endpoints

  • 7.11 Users retrieval - endpoint to get all users of an account (and subaccounts)

  • 7.12 Users creation - endpoint to create a new user

  • 7.13 Users update - endpoint to update an existing user

  • 7.14 Users deletion - endpoint to delete an user

  • 7.15 Feature set retrieval - endpoint to get all feature sets of the account; when creating a new or updating a user, you need to specify the feature set (role) the user has e.g. Administrator, Standard, Viewonly

API changes

• When creating a shipment via prepareShipment, time fields such as requestedDeliveryTime were handled incorrectly. Seconds were appended to the submitted value even when they were already present, which produced an invalid value and a misleading error message referencing the wrong time format. Time values are now handled correctly and any validation error reflects the documented HH:mm format.

• Rate calculation requests that included a loadmeters value failed with an internal server error ("No min/max shipment weights found"). Loadmeters are now handled correctly in the carrier selection logic and rates are returned as expected.

• When a tracking status update arrived without an estimated delivery date, that empty value was copied over the planned delivery date, clearing it from the shipment. The planned delivery date is now retained when a status update contains no estimated delivery date.

• When retrieving a shipment, the lineNo on each package returned an internally generated number instead of the value you submitted. For example, sending 101 returned 1. The value you submit is now returned unchanged, and it is also shown and reused correctly when a shipment is rebooked in MyTranssmart (see below).

Location select / PUDO changes

• For the following carriers, location select is activated:

  • INA - InPost API

MyTranssmart dashboard changes

• The line number is now visible for each package on the shipment details page and can be edited in the package details. Previously, a line number sent in through an integration was not shown in MyTranssmart and was lost when a shipment was rebooked or duplicated — a new number was generated instead. The original line number is now kept and included when the shipment is saved or rebooked.
  

• Parent accounts using Streamed Status can now choose to receive status updates for their own shipments only, excluding those of child accounts — while the default behaviour of including child account updates remains unchanged.
  

• You can now delete a SmartPrint connection directly from the connection list, and see at a glance whether each connection is online or offline. This makes it easier to clean up connections that are no longer in use and to spot a connection that is not available.
  

• In the shipment detail page, deleting a selected package could in some cases also remove a second package line, which was not selected anymore. This is fixed; only the packages you have selected are now deleted.

• A status check is now available for SSO client configurations. It confirms whether the authentication service has successfully started your SSO application — meaning the metadata was retrieved and the client configuration was accepted. This makes it easier to see at a glance whether an SSO setup is active, instead of having to diagnose failures without feedback.
  

Help shape the future of nShift Transsmart

We are continuously conducting interviews with our end users to gather feedback. We are curious about experiences of users who work daily in the MyTranssmart dashboard.
The interview takes about 30 minutes via a Teams call or we can even plan a visit to your office/warehouse. Your input is very valuable to make our product even better suited to your needs. Interested? Contact us via mail and we will reach out to you.