Skip to main content
All CollectionsRelease Notes2024
April 25th, 2024 Release Notes, Version 24.08
April 25th, 2024 Release Notes, Version 24.08

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

S
Written by Shipwell TMS Support
Updated over 7 months ago

Enhanced Location Management with Latitude/Longitude

Shipwell's address book location management just got a boost! You can now manage latitude and longitude (lat/lon) directly on the main page. This lets you see lat/lon information during location searches and even set locations using these coordinates. Plus, the address line now displays both the lat/lon and the corresponding country code for even greater precision.

Additionally, we’ve now include a new Location Type called Pool Point.

Pool Point: The location acts as a consolidation center for a specific region. Shipments from various origins are grouped together based on their destination area. These consolidated shipments are then sent out for line haul or for final delivery. Note that this will be used further in optimization in the Shipwell platform. For external APIs/Integrations a Pool Point will be mapped to a Business with a Dock or Forklift by default if that integration does not support Pool Points.

Additional Organization Added to Carrier Profile

Shipwell has added Rates to the carrier profile side panel. This is one of a series of improvements to the Carrier Profile page.

API Changes

  • The financial charge-codes reference data standard will be available via the API and in the API Reference data to allow API users to view this data along with other existing reference data.

  • Updated corrogo for v3 orders to update the .items. shipping_requirements.combined_handling_unit_info.net_weight into .items. shipping_requirements.combined_handling_unit_info.weight

Data Science/Analytics Model Updates

  • TOTAL_WEIGHT was not being calculated correctly for the shipment summary table if line items had a mix of “LB” and “KG”. We fixed the calculation and also added a TOTAL_WEIGHT_KG and TOTAL_WEIGHT_LB in Looker.

  • Reports in Looker are not meant to be real time. There are two data pipelines that get data from AWS to Looker. One happens on a 15 minute cadence, the other on a 30 minute cadence, so expect data to be in the reports within 60 minutes, but that is not assured.

Other Minor Enhancements and Bug Fixes

Bug or Enhancement

Severity

Description

Enhancement

-

Add PER HOUR rates into the rate tables using bands

Bug

Sev 3

Unable to View Shipments Dashboard - Error Present

Bug

Sev 2

Separate P44 tracking jobs from general tracking jobs

Bug

Sev 2

Shipments showing incorrect dates

Bug

Sev 2

UnKnown Error on Shipment Change- Fedex Parcel

Bug

-

[Amazon] booking wrong dates behavior

Bug

-

Dispatch Spinner Not Hidden

Bug

-

Set linear_dimension_count and handling_unit_count to null when the fields get removed

Bug

Sev 1

Unable to add new carrier when fiCarrierProfileTags flag is true

Bug

Sev 2

Fedex invoices failing.

Bug

-

FPM is not rerunning after an invoice has been selected as 'Resolve' - Updated to now have first pass match running continuously when in disputed status

Bug

-

Issue with the partial carrier name matching logic for Settlement First Pass Match - now name match will properly leverage customer configured carrier name instead of FMCSA name as a comparison

Bug

Sev 2

QuickBooks Failed QBO Invoice Creation

Bug

Sev 2

Delay in Label Creation for LTL

Bug

Sev 2

Reference #'s not pulling over into Shipment Creation

Bug

Sev 2

After removing NMFC Code and subcode from v3 order then it won't let me save the page

Bug

-

Orders Dropping from Shipments

Bug

-

License error on Scheduler Calendar - BB

Bug

-

Not Able to Remove "Rep" From Address Book

Bug

-

V3 Orders- Clearing Hazmat Checkbox Does not Clear Hazmat Fields

Bug

-

V3 Orders Items- Clearing Out Fields Throws Backend Error

Bug

-

Update create bill interface to allow for user to select transaction date for QB and NetSuite marketplace financial erp integrations

Bug

-

Datetime format issue with v3 order importer


Did this answer your question?