A new Hazardous Information section has been added to the Create and Edit product screens. This is only applicable for products that have the Hazardous flag set to true. With this feature added, you can edit and manage the hazardous information of your products and use it when creating a shipment for carriers that accept dangerous goods.
Each tracking account screen now can receive tracking events after the ‘Delivered’ event to enhance the customer’s visibility of their Royal Mail shipment tracking. With it, customers can easily manage their settings through the Add, Edit, and View tracking account screens for Royal Mail, ensuring they receive timely and accurate push notifications on their shipments—and can still choose to receive the events recorded after the delivered event. This enhancement features the logic update of the Sapient system to generate push payloads for Royal Mail tracking accounts based on the newly defined UI setting and the time elapsed since a ‘Delivered’ tracking event.
The Create Shipment API response now includes the ‘PartnerDetails’ field. This field is populated when a partnerLabel is used and left blank when a partnerLabel is not used for the shipment. For more information on creating a shipment, please refer to the API reference page and the Royal Mail API section.
The integration has been updated to allow customers to create shipments of dangerous goods belonging to any class. The previous restriction limiting dangerous goods to Class 9 has been removed. Customers can now create dangerous goods shipments of any accepted class, provided the UN code is in the list of accepted products and the class is in the list of approved classes. The existing ID8000 category remains mandatory only for Class 9 products.
The Tracking Webhook system has been updated to classify all HTTP responses from the carrier API outside the HTTP 200-299 range as errors and return the corresponding error response. Additionally, the retry mechanism has been revised to cease retry attempts to fetch tracking data from the carrier API after 24 hours of continuous failure, following specific retry intervals.
The information about manifested containers is now stored in the database for future reference. A new field called ‘Container Status’ has been added to all the relevant Container APIs to store and retrieve the container information based on status. The ‘Container Status’ can either be ‘Active’ or ‘Manifested’. Customers can only add or remove shipments from containers with an ‘Active’ status. Containers can only be manifested if they have an ‘Active’ status. Containers in the ‘Manifested’ status cannot be deleted. For example, in the Get Containers API, the query parameters in the API request have been updated to include the optional parameter 'containerStatus,' and the API response now includes the containerStatus field populated with the container's status, either 'Active' or 'Manifested'. For more information on managing shipments in a container, please refer to the API reference page and the Sapient Core API section.
The Swagger Documentation for the Royal Mail Get Collections Timeslot endpoint has been updated in the Section Description. This section now includes information on creating collections, obtaining collection timeslots, and cancelling collections for Royal Mail shipments.
The Type 3 pre-advice file has been updated to include Container ID. For shipments in a container, the Detail Supplement Record (03) is populated with the supplement code "SO" and the Container ID (truncated to 40 characters if necessary). For shipments not in a container, the Detail Supplement Record (03) will not contain the supplement code “SO”.
Create Shipment endpoint has been updated to include USA Army Post Office (APO) county codes for destination address.
The destinations include:
