Release note - July 2025
New Shipment Connector version 4.7.0.0
Section titled “New Shipment Connector version 4.7.0.0”Our July release of Shipment Connector features a host of new features and minor bug fixes. We have also added our tables to allow use in BCs retention policy. As always if there are any questions reach out to us at support@xtensionit.com - for the comprehensive list of changes see below.
Features
Section titled “Features”1.1. nShift Ship - Dangerous Goods
Section titled “1.1. nShift Ship - Dangerous Goods”Our new Dangerous Goods apps are now also fully functioning with nShift Ships API allowing users to send ADR/DG Data to nShift Ship and have ADR documentation generated on that basis for the carrier. See more information on our Dangerous Goods system see the following section.
1.2. nShift Webshipper - Request Quote
Section titled “1.2. nShift Webshipper - Request Quote”We have changed the endpoint that is used when requesting quote in Webshipper as it is now possible to get the actual carrier price for the shipments The action for this can be found on your Sales Orders or warehouse shipments via. Actions > Shipment > Request Quote.
1.3. Shipment Connector Tables for BC Retention Policy
Section titled “1.3. Shipment Connector Tables for BC Retention Policy”In order to allow for users to setup a retention policy for Shipment Connector tables we have added the possibility for this. As ongoing long-term users could end up with a lot of data. We have added the following tables to the retention policy:
- Rest Log
- Shipment log
- Waybill Header
Hotfixes
Section titled “Hotfixes”1.1. Added a safety procedures for EXW agreement system (Webshipper & nShift Ship)
Section titled “1.1. Added a safety procedures for EXW agreement system (Webshipper & nShift Ship)”Users using our EXW agreement system for shipments in Webshipper & nShift Ship experienced accidental shipments where they had forgotten to add an EXW agreement on the waybill header. This caused the system to select all the EXW agreements setup and sent them in the API call. This caused in return an error. We have added some safety measures to accomedate this to ensure that users will be prompted if there is no EXW agreement selected.
1.2. Shipment Journal information missing details on Track & trace page.
Section titled “1.2. Shipment Journal information missing details on Track & trace page.”Users have started using the updated Shiment Journal system more frequently which is great! However, it also showed some missing parts in terms of the data that was saved for those shipments such as customer no and name, which is normally saved on default type shipments. We also discovered an error with this that made reprinting the label for a Shipment originated from the Shipment Journal impossible.
1.3. nShift Ship - Customs document Unit of Measure code
Section titled “1.3. nShift Ship - Customs document Unit of Measure code”With shipments containing Customs information to carriers such as UPS & FedEx you have to also inform of a Unit of Measure Code (UoM) for the items This was previously defaulted to the UoM code in your Shipment settings but was used incorrectly. Now this UoM code for Customs is taken from the data on the sales lines.
1.4. Pick-up Date / Shipment Date do not match when selecting a different date manually on Shipment date (Warehouse Shipments)
Section titled “1.4. Pick-up Date / Shipment Date do not match when selecting a different date manually on Shipment date (Warehouse Shipments)”There was a small issue when selecting a Shipment Data on a Warehouse Shipment which could cause a disconnect between the Pick-up Date on the Waybill Header and the Shipment date on the document self - two fields which usually have the same date.