Request a Demo

Talk to one of our TMS experts about how we can help streamline your freight brokerage operation:

Name
Email
Phone
Company

BrokerWare System Updates

System Updates

New Features & Enhancements

Zip Codes

  • Added validation to support valid formats of 5 digit or 9 digit zip codes.

Hide Mark Delivered & Invoiced button

  • New global default that will hide the "Mark Delivered & Invoiced" button from the full form.
  • Link to Knowledge Base Article: Staff Admin Global Defaults

Omit Non-Hazmat Carriers from LCR

  • Added new logic where if a carrier's profile does not have an active and current Hazmat certificate indicated, the carrier will 'fail' in the LCR.
  • This will help prevent users from selecting carriers that are not Hazmat certified within the system.
  • Link to Knowledge Base Article: Omit Non-Hazmat Carriers from LCR

Shipment API

  • We’ve updated the Shipment APIs to support ISO 8601 timezone offsets. You can now send local date/time values with explicit offsets, ensuring accurate scheduling across regions and timezones.

Download Documents Directly from Shipment Profile

Bug Fixes

Priority One

  • Mapped Pennsylvania High Cost Fee for Saia Freight rates.
  • Fixed MISC charge mapping for Estes rates.

Central Transport

  • Fixed E-Dispatch issue where the pallet count in the request was sending as 0 when Pallets as Package Type was used, but not marked as 'Is Palletized".
  • Fixed issue where electronic documents were mislabeled as E-BOL.

Edit Commodity modal

  • Fixed display issue where the Billed and Cost fields were not aligned when using shipment mode Truckload and its Stop Number values.

Tile Configuration

  • Fixed issue where the Booked - Not Covered tile was not matching the tile configuration setup if changed.

Email Quotes from LCR

  • Fixed issue where if insurance was added to the shipment, the insurance value was not indicated on the downloadable PDF in the Email Quotes tool.

Create Shipment API

  • Fixed an issue where accessorials were not applied when creating shipments via the API using loadPoint / dropPoint codes that reference saved locations.