Yesterday 30-April-2026 we deployed below changes and fixes to our Accept environment.
The release to Production is scheduled Tuesday 5-May-2026.

API / DevDocs changes (nShift Transsmart Developer Documentation)

• When doing a rate call, in some specific cases the service returned an internal error 500, for instance when mandatory input values are missing. This is solved now by showing a correct error message.

• The rate engine was case sensitive which resulted in not returning rates for zones that were not inserted with capitals. This is solved now, although zones should always be in capitals, by making the rate engine case insensitive for zones.

• The rate engine (carrier select) now supports cost center configuration in Routing Rules. In a routing rule you can specify that a different cost center should be used for that route. This was currently not supported by the carrier select engine; the result was that the costs are calculated with the given cost center instead of the one that the routing rule has specified. This is adjusted now.

Location select / PUDO changes

• For the following carriers, location select is activated:

  • PPL - Professional Parcel Logistics (country CZ)

  • GLH - MyGLS Hungary (country HU)

  • DUA - DPD UK API (country UK)

  • DHS - DHL Sweden (country SE)

• In the API endpoint /v2/locations/ we have added the parameter pudoType which can be filled with values "shop" and/or "locker". Some carriers provide this value in their response and for those, it's possible to for instance only show shops when you sell products which are too big for a locker.

MyTranssmart dashboard changes

• When manually creating a shipment for which the book or print action resulted in an error, the page would reload to the shipment overview page and you would need to re-enter all shipment data. This is solved now; when showing an error, you will remain in the shipment details page with all values filled, so can fix the error and book or print the shipment directly again.

• In the shipment details page, when adding or editing a package line, there was no validation on the fields Quantity and ShipmentLineId. This is adjusted now.

• In the printer settings, we have made selecting printers optional instead of mandatory and added a ‘clear’ icon. The reason that no everybody has either a ZPL or PDF/laser printer and therefore should be able to leave it empty.
  

• For Single Sign-on, when using OpenID we’ve made a change in the hierarchy for using a user name/email address to the IDP.

• We have added the possibility to turn off Single Sign-on for a specific user without the need to turn it off for the account.
  

• When adding a subaccount, it was not directly visible after creation; you first needed to log out and in again. This is solved now; after adding a subaccount the token is directly refreshed so the new account is directly visible.

• An email address is only supposed to exist once per environment but we’ve found out duplicate email addresses exist. We found out 2 scenarios that could result in this and we’ve solved those. In case duplicate users/email addresses exist, one of those must be deleted in order to properly work in the MyTranssmart dashboard.

• In the landing page, fixed a small issue when striking through a value in one of the donuts; when changing the date suddenly another value was disabled (different value on the same position). This is solved now by removing the strike through when changing the date.

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.