Pacejet

Pacejet Shipping Release Notes 25.5

To understand release timing, visit our Pacejet Service Status page.


New Features

The new features in this release include:

  • New Templates

  • New Shipment Rule — Set Freight Bill To By Ship Code

New Templates


USMCA Certificate of Origin with Commodities

This template provides a standardized format for documenting origin information for goods traded under the USMCA agreement, including specific commodity details. Entries from the Commodity/International section are grouped by Commodity Description, NAFTA Preference Code, Country of Origin, and HTS Code. The rows are listed in sequence by the grouping.

usmca agreeement certificate of originv2.jpg


Rona Packing List 8.5 x 11

The Rona Template is a Packing List with products listed individually without any grouping, in a portrait layout. The product grouping includes product number, description, quantity UOM, unit weight, weight UOM, UPC Code, unit price, unit cost, and customer product number. This template is not intended for use in Consolidated shipments.

Rona Packing List.jpg


New Shipment Rule — Set Freight Bill To By Ship Code

A new Shipment Rule, Set Freight Bill To By Ship Code, has been implemented. When working with 3PL services, you'll often need different billing addresses for each LTL carrier (Carrier Class of Service in Pacejet). This rule allows for automatic setting of the Freight Bill To address based on the selected Carrier Class of Service, providing more flexibility in managing freight billing for different carriers. This streamlines your shipping process by eliminating manual address changes when switching between carriers that have different billing requirements.

Note: This only applies to prepaid shipments.

This Shipment Rule runs after the rating process completes and a carrier is selected. The rule assigns the appropriate Freight Bill To address from your predefined list based on which carrier service was chosen.


Enhancements

The enhancements for this release include the following:

  • Custom Data—Performance Improvements

  • Terminology Updates for Standardization

Custom Data — Performance Improvements

The Custom Data feature has undergone a significant refactor to address performance issues. This improvement enhances the overall application performance, particularly for customers with large datasets, while maintaining all current customization capabilities.

Terminology Updates for Standardization

To streamline terminology throughout the system, the following updates have been made:

  • Package replaces Container — The system now consistently uses the term Package instead of Container throughout the user interfaces. This change standardizes terminology to align with API usage, improving consistency and clarity for users.

  • Product replaces Item — The term Product has replaced Item throughout the user interface.

  • Shipment Service replaces Special Service — The term Shipment Service has been standardized across the user interface, replacing Special Service. This update aligns the UI terminology with the API, enhancing consistency across the platform.


Bug Fixes

ID

Description

MCS - 6733

We corrected an issue that caused a null reference / "500" error when importing a shipment with missing products.

MCS - 7044

We corrected an issue where the Report Menu list extended past the page footer without a scrollbar.

MCS - 7375

We corrected an issue that prevented users from deleting saved filters containing ampersand (&) characters in their names.

MCS - 7449

We corrected search limitations in ShippingWorkbench by adding "In" and "Not In" operators to the search criteria. For example, users can now filter records using comma-separated values (e.g., Facilities In "8,10") to find matches across multiple specific values.

MCS - 7705

We corrected an issue where QuickShip did not delete the previous packing data when restarting the packing process. Now, orphaned ShipPackDetail records that previously caused errors when using the ShipmentConfirmsContainers API endpoint are prevented.

MCS - 7846

We corrected an issue in Retail Licenses that allowed users to modify templates when no license was available.

MCS - 7848

We corrected an issue where hotkeys that remained active during Scan Pack operations could cause premature shipping.

MCS - 7860

We corrected an issue in LTL PRO Setup where the system treated PRO block numbers as alphanumeric instead of numeric values. Now, probills are prevented from being inadvertently removed from multiple blocks when they share similar numeric sequences.

MCS - 7933

We corrected naming inconsistencies in the Paperwork Workflow for reports. Now, there is a standardized report naming convention applied across all workflow interfaces to provide a more consistent experience.

MCS - 7934

We improved a limitation that restricted Print Trigger names to 20 characters. Now, users can create Print Triggers with names up to 50 characters long without encountering errors.

MCS - 7936

We corrected an issue where Batch Processing did not produce WebSocket log files/messages, and printing was delayed.

MCS - 7937

We corrected an issue where Print Rules using Custom Data at the Shipment Level did not function properly.