Skip to main content
All CollectionsRelease Notes2024
April 11th, 2024 Release Notes, Version 24.07
April 11th, 2024 Release Notes, Version 24.07

An overview of new features and bug fixes released on April 11th, 2024 for Shipwell version 24.07

S
Written by Shipwell TMS Support
Updated over a week ago

Carrier Profile Enhancement

We're excited to announce enhancements to the carrier profile page within the Shipwell platform! These updates provide a more organized view of carrier information and introduce a refreshed Analytics tab for data-driven carrier insights.

Enhanced Carrier Profiles

  • Improved Organization: The carrier profile page has been reorganized to provide a more intuitive layout, making it easier to find the information you need.

New Analytics Tab

  • Carrier Scorecard and Analytics: The Analytics tab offers valuable insights into carrier performance through the default carrier scorecard and other analytics. This data empowers you to make informed decisions when selecting carriers for your shipments.

These updates lay the groundwork for future advancements in carrier management. Stay tuned for the upcoming introduction of carrier credential management and onboarding functionalities within the carrier profile.

Routing Guide (Workflow) Status Enhancements

We’ve updated the workflow status to be more descriptive of what is currently happening with the step in the workflow. For example with a tender, you will see:

  • Accepted

  • Rejected

  • Revoked

  • Expired

Examples shown below:

If there is an error with the workflow you will see why that step failed and marked with a warning. In this example, the carrier’s insurance coverage amount limit was not enough for the tender to occur and that step was skipped.

Charge Code Standard and API Endpoint

Charge Codes and Standardized Reference Data

We're excited to announce a significant update to Shipwell's charge codes and reference data, designed to empower you with greater efficiency, consistency, and flexibility in managing your transportation costs across new modes like ocean, drayage, and air freight but enhance existing modes such as Intermodal, Rail, LTL, FTL, and Parcel.

Introducing a Robust Charge Code Standard

Shipwell is now introducing a comprehensive version of the charge code standard which will be updated quarterly. The current version of the standard is v3 and it was created in 2024Q1. This enhanced standard offers several key benefits:

  • Standardized API Integrations: Seamless integration with carrier and third-party integrations ensures effortless data exchange and simplifies your workflows.

  • Expanded Reference Data: The new standard provides a wider range of pre-defined charge codes, encompassing commonly encountered fees like stop-off charges (SOC), cleaning charges (CLN), and vehicle ordered but not used (VOR, with alias TONU for "Truck Ordered, Not Used"). This eliminates the need for manual code creation and ensures consistency across your shipments.

  • Flexibility for Future Growth: The standard is designed to be adaptable, allowing us to incorporate new charge codes as the transportation landscape evolves. This ensures you'll always have the tools you need to accurately reflect your shipping costs and match to third parties in integrations, invoicing, and analytics.

Accessing the New Charge Code Standard

The charge code standard is available at {{evironmentBaseUrl}}/reference-data/charge-codes/ (where {{environmentBaseUrl}} is a URL like https://sandbox-api.shipwell.com, https://api.shipwell.com, etc.). This easy-to-access location for charge codes empowers you to explore the available codes, understand their meanings, and incorporate them into your shipping processes. The endpoint has standard searching, filtering, pagination and performance consistent with Shipwell's v3 API standard. The response below shows an example response:

Mapping to/from EDI/API Connected Carriers

Shipwell's charge code standard will be used to map charge line items from carriers connected via EDI, AP, and via Shipwell's portal. Additionally, any new carrier EDI connection will use this EDI standard. The following diagram provides an example of an accessorial received by an API-connected carrier that maps to Shipwell's standard and provides consistent invoicing and settlement.

Analytics Changes

Analytics reports such as accessorials, costing, and additional charge line item derived reporting will have expanded granularity and filtering.

Simplifying Your Shipping Management

By leveraging Shipwell's enhanced charge codes and standardized reference data, you can expect to:

  • Reduce Time Spent on Manual Coding: With a wider selection of pre-defined codes, you'll spend less time creating custom entries, streamlining your workflows.

  • Improve Cost Accuracy: Consistent and standardized charge codes ensure your shipping costs are accurately reflected, leading to better budgeting and financial control. Carriers will be instructed that these charge codes are part of the Shipwell standard and EDI, API, and carrier integrations will map to these standard codes.

  • Enhance Communication and Collaboration: Standardized codes facilitate clear communication with carriers, partners, and internal teams regarding transportation charges.

Address Book Updates

We've improved the address book user experience to allow the input of Latitude and Longitude from the top-level versus manually inputting an address. You will now see the exact location and the associated latitude and longitude.

Additionally, we've added the PICKUP_APPOINTMENT accessorial to the address book so that when quoting, this will correctly pull back as part of the rating/tendering process. The figure below shows the pickup accessorial added to the Accessorials input field.

API Changes

Added Charge Codes Standard and capability: See above for details on powerful new charge codes standard and reference data.

  • The new charge codes standard is backwards compatible with any previous charge codes and is additive to available charge codes

  • The charge codes standard is planned to be updated quarterly with additions over time based on customer needs.

Data Science/Analytics Model Updates

Added Power unit to Data Share/Builder User

Increased number of rows that can be shown in a table, e.g. Shipment’s List, and downloadable as a report to 5k, can not be increased any more. Just the table can be up to 100k rows.

Identified issue where Looker queries were using Fivetran Warehouse causing data transfers to be blocked

Other Minor Enhancements and Bug Fixes

Bug or Enhancement

Severity

Description

Bug

Sev 2

Shipments showing incorrect dates. - TR

Bug

Sev 2

RFP to Contract Conversion Missing Stops Origin/Destination

Bug

Sev 2

Contracts bug

Bug

Sev 2

Pro # updating in Shipwell prior to Dispatch

Bug

Sev 3

Default Dashboard not Defaulting

Bug

Sev 2

Shipment RDWLXC will not Archive

Bug

Sev 2

Shipwell not absorbing Priority1 carrier tracking updates

Bug

Sev 3

[BE] Adjust applicable-contract logic to allow blank equipment type to match on all equipment types

Bug

Sev 2

Invalid Event payload for the purchase_order.updated event

Bug

Sev 3

UPS Parcel instant rates for Multiple items/Packages returned is not the total for the shipment

Bug

Sev 2

LTL Time Error for R&L and RoadRunner

Bug

Sev 2

Intra-Canadian Shipments should not be marked as international

Enhancement

-

Netsuite order updates to shipment

Bug

Sev 2

UPS Shipments not booking with selected account

Bug

-

[opus] Unable to Bulk Edit Dates on Dashboard with more than 2 stops

Bug

Sev 3

Shipment Dashboard not displaying first pick/last drop correctly on Multi-Stop Shipment

Bug

Sev 3

Shipwell Order Importer Custom Data Not Importing Correctly for v2 Orders

Bug

FCFS appointment information isn't updating automatically after rescheduling

Bug

User Permissions for "Customer" View

Bug

Deactivate BE restrictions from users.view_company_users permission

Enhancement

Set multiple selection to 'Order #' Filter for v3 Oqders

Enhancement

Apply new shipments.view_financials permission to shipment routes

Bug

Sev 2

Not Able to Change/Add Custom Data

Bug

Sev 2

Bill could not be submitted to Quickbooks

Enh

Allow transportation release events to be subscribed to via webhooks

Enhancement

[iOS] Refactor Shipwell Application Permissions and Allowing for Dock Scheduling Dock Worker Access for Users that also had broader shipper permissions

Did this answer your question?