Today 15-January-2026 we deployed below changes and fixes to our Accept environment.
The release to Production is scheduled Tuesday 20-January-2026.

API / DevDocs changes (nShift Transsmart Developer Documentation)

• DevDocs: for the shipment deletion call we have adjusted the documentation and added information about different responses depending on the call (single vs multi)

• When doing an API call to /v2/rates/{account_number}?action=calculate the result for the fields deliveryDate and deliveryTime could be the text "Not Available" which is not a valid date/time format. We have adjusted this; when the date/time cannot be calculated, we are now not sending back those 2 fields anymore (null). 

• When doing the rates call via the API or the carrier select call via MyTranssmart, it would not give any results for a zip code with 1 character. For country AE, the zip code is not used but it's a mandatory field in our API, so it should also work when sending in e.g. value "1". This is solved now; it will also show rates when the zip code is 1 character long.

MyTranssmart design update

• The MyTranssmart dashboard has gotten some design updates to stay in line with the new nShift house style.

MyTranssmart dashboard changes

• In some specific scenarios, in the shipment details page it would show a Planned delivery date from/to as value "000000" instead of empty or a correct date format. In previous release we fixed this for the Original planned delivery date; this is now also fixed for the Planned delivery date.

• When booking a shipment via the webservice/API, it’s possible to send in customerDocuments on shipment/package level. In MyTranssmart, when zooming into the shipment details page of a shipment with status NEW or BOOK, the customerDocuments were deleted when pressing Book or Print. For Print only if a change was detected. This is solved now; when (re)booking a shipment the customerDocuments will not be deleted.
  Note: when using the duplicate shipment function in MyTranssmart the customerDocuments will not be copied to the new shipment because they belong to the source shipment only.

• In specific scenarios it could occur that the carrier select rates were showing a different price than the actual booking would get. This was related to wrong rounding in staffel calculation. This is solved now.

• Some time back, we added more languages to MyTranssmart. We have now also added the following languages to the Excel shipment download/upload file:

  • Danish (da-DK)

  • Finnish (fi-FI)

  • Norwegian Bokmal (nb-NO)

  • Polish (pl-PL)

  • Spanish (es-ES)

  • Swedish (sv-SE)
    Note: we deployed this change in week 50 of 2025 but needed to roll it back because it impacted the current four languages (EN, NL, DE, FR).

• In Manage account, Email Settings when saving a mail template, an SPF check towards MxToolbox is done via their API. In some cases the checks fails while when checking the domain at the website of MxToolbox, it's correctly configured. This is solved now by saving the template anyway since the issue on MxToolbox's service should not block the process in MyTranssmart.

• In MyTranssmart we have updated the URL behind the Help Center navigation button
  
   

   

   

Help shape the future of nShift Transsmart

We are continuously conducting interviews with our end users to gather feedback. We are particularly curious about experiences of users who work daily in the shipment overview page and shipment details page of MyTranssmart but of course we are interested in every possible feedback we can get. 
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.