Today 21-August-2025 we deployed below changes and fixes to our Beta environment. 

The release to Accept is scheduled Monday 25-August-2025.

The release to Production is scheduled Tuesday 26-August-2025.

Support for 300 (and 600) dpi printers

From now on, we also support the usage of a 300 (or 600) dpi label printer! 
In MyTranssmart in the My Printers section, we now check the resolution of the selected ZPL printer. When saving, we store that resolution value to the Printer settings of that user:

This means that when now printing a label in MyTranssmart, it will automaticaly print the label in 300 dpi resolution.

In the API, for both shipment API action PRINT as for the printing API, for rawJob = true, we have added the parameter dpi with values 203, 300 and 600 which reflect the ZPL printer resolution. When the parameter is sent in with 300 or 600, it will print the label in the desired resolution.

Notes: 

• If rawJob = false, our printing solution SmartPrint is used and we therefor look at the dpi setting of the logged-in user's printer or at the dpi setting of the printer that is sent in as parameter printer_zpl.
• If rawJob = true, a custom printing solution is used and we do not look at the user or printer. We return a 203 dpi label by default unless you send  in the parameter dpi=300.
• In MyTranssmart we show the resolution of the ZPL printer in brackets behind the printer name like this: 
  
  but be aware that in the API parameter printer_zpl you don't add this value. Example in this case is:
  /v2/prints/ACCOUNTCODE/shipment_reference?&rawJob=false&spc=device$@device&printer_zpl=ZDesigner ZD421-300dpi ZPL
  
  More information with all ins- and outs will follow soon via the Zendesk knowledge base.
  
  Disclaimer: we have tested many different labels, but we still strongly advice to first validate the label of your carrier(s) and compare them to see if the result is as expected. In case of differences, please reach out to use with the examples and details (which carrier etc) and then we will investigate if we can improve this functionality.

DevDocs changes

• We have adjusted the documentation by correcting the maximum sizes for fields carrierStatusCode (32) and costCenter (32).

API changes

• We have implemented the Act on Behalf functionality for the Book by bookingprofile request call (/v2/shipments/{{accountCode}}/BOOK/{{bookingProfileCode}}.

• We have fixed an error for the Book by bookingprofile request call, stating "Missing setting" when (another) booking profile code contained the " character.

• When doing a rate request call, we calculate the pickup date based on the input data and transit times, and we use that calculated pickup date to calculate the expected delivery date. Before, we did not send back this calculated pickup date in the response call, so the requester might not understand how the expected delivery date was calculated. This is changed now; in the existing response field “pickupDate” we now send back the calculated pickup date.

MyTranssmart dashboard changes

• We have implemented Crowdin as (AI/ML) translation tool and have improved the current translations for English (en), Dutch (nl), German (de) and French (fr). Besides that, we have added six languages: Danish (da), Finnish (fi), Norwegian Bokmal (nb), Swedish (sv), Polish (pl) and Spanish (es)!

• In menu Manifest when printing or downloading a manifest list, it could generate an error 500 if there were shipments with empty T&T URL. This is solved now.

• In the Change Log table the option Show batch did not not show information when field Change by was a parent user or database user. This is solved now.

• When downloading a report, for some fields it could show value “No column definition found” instead of showing an empty value. This is solved now.

• When a (sub) account is being added, the system will now by default add a Client Carriers configuration record for qualifier PORTAL_INTEGRATION_ENABLED with value “1”.

• Our insurance partner Cover Genius has changed the IPID url in the disclaimer due to a new insurer.
  
   

Help shape the future of nShift Transsmart

We are 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. The interview takes about 30 minutes. 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 plan a meeting.