Overview
The Descartes Pacejet Day & Ross 26.3 release corrects an issue that could cause shipment creation to fail when a product description was too long. For any questions about specific items, please reference the associated number (if provided) when contacting Descartes Customer Support.
Bug Fixes
🟩 Resolved Issue: Shipment Description Length
Day & Ross shipments no longer fail when a product description is long. Pacejet now sources the package description from the LTL classification description and limits it to the carrier's 80-character maximum. Previously, the raw product description was sent, which could exceed the limit and cause Ship requests to fail, and it was the incorrect value to send.
Things to Watch During Implementation
⬛ Descriptions Over 80 Characters Appear Shortened on the Carrier BOL: The Day & Ross BOL shows only the first 80 characters of the LTL classification description, while the Pacejet BOL shows it in full. The two documents will not match for longer descriptions. If you want the carrier BOL to read completely, shorten the description on the classification record.
⬛ Assign an LTL Classification to Every Package: Make sure each package has a classification and freight class assigned. If the classification is missing, the description and class printed on the carrier BOL may not reflect the freight being shipped.
⬛ Ship Date Must Be a Future Date: Day & Ross requires the pickup date to be in the future. Shipments with the current date will fail with a pickup date error.
⬛ At Least One Canadian Address Is Required: Day & Ross does not accept shipments between two U.S. points. Each shipment must have either an origin or a destination in Canada.
⬛ Verify Carrier Settings Before Testing: Confirm the currency code is set to "CAD", and your Day & Ross account number is entered in carrier settings. Missing values cause rating to fail without a message that identifies the cause.
⬛ Check Email Addresses on the Shipment: An invalid email address on the shipment can cause Day & Ross to return a permission error rather than one naming the field. Confirm email formatting if you see an unexpected authorization failure.