Request a Demo

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

Name
Email
Phone
Company

System Updates

New updates and improvements to Brokerware.

New Features and Enhancements:

Enhancement: Mainfreight

  • Updated Rating API to their latest.
  • The API setup will now only have 2 fields: Customer Code and Subscription Key.
  • If you have a current subscription key that was given for Tracking and Dispatching, this will be the current value to use in the Subscription Key field.

Enhancement: LCR - Save/Recall API Rating Request/Response via Shipment Profile

  • Added the ability to recall the API Rate Request/Response info on the shipment profile that is also found on the LCR.
  • This can be found in the Rate Quote section using the <> to bring up the Request/Response modal.
    • NOTE: If a user reruns the LCR and selects an updated rate or a new carrier rate, the request/response info will be updated with the last rate selected.
  • If the API carrier rate does not include a Rate Quote number, users can still recall this info using the <> on the shipment profile.
  • If a non-API carrier rate is selected, the <> will be hidden.

Enhancement: Mass Rater

  • Added the ability to set a Processing Limit and Minutes to Delay value prior to processing a file.
  • This is required to be filled out in order to continue with setting up a file to be mass rated.
  • This is to help with timeouts occurring on the carrier's end due to the volume of requests hitting their APIs all at once.
  • The Processing Amount Limit allows the user to set the number of rates to be rated within the Minutes to Delay value.
    • EX: Carrier XXX has a limit of 350 rates for every 15 minutes. The user can set the Processing Amount Limit to 350 and the Minutes to Delay to 15 so that the Mass Rater will run 350 rates, then pause for 15 minutes - repeating until the sheet finishes.

Enhancement: EDI 210 Matching

  • Added logic to not reset the scroll bar on the page upon matching a record.

Enhancement: Shipmind

  • Added Tooltips for Tracking and Delivery options.

Enhancement: Bazaar

  • Added functionality where any document type uploaded to the seller's load as 'Public' will now be reflected on the buyer's load as "Staff" for the View Permission.
  • This will allow sellers to upload any/all types of documents to pass over to the buyer and the buyer does not need to worry about certain docs being viewed by customer logins.

Bug Fixes:

XPO Logistics

  • Fixed rating issue where Excessive Length accessorial was not returning a rate when the load was marked as palletized or not.

Saia Freight

  • Updated tracking link for PRO numbers linked with Saia.

ECHO Logistics

  • Fixed rating issue where ECHO's integration was not returning rates with the latest ECHO credentials.
  • Fixed rating and E-Dispatching issue where the Guaranteed rate was being indicated as a commodity line. This is now corrected to be an accessorial on the load.
    • NOTE: After this update, if there are past shipments with ECHO and the Guaranteed rate is still reflecting as a commodity line, please remove this line and run the LCR again. Users will run into a rating error because the Guaranteed rate is technically not a commodity and cannot reflect a class value.

Tax Air

  • Fixed Delivery Appointment accessorial mapping.

TForce Freight

  • Fixed rating issue where rating type "Density" was not rating correctly.

ABF Freight

  • Fixed tracking issue where loads were not being updated to reflect In Transit status.

FragilePak

  • Fixed tracking issue where the PRO Number was not properly being used to track shipments.
  • Fixed E-Dispatching issue where the pickup request was not passing some notes.

Mainfreight

  • Fixed E-Dispatch issue where fields were missing upon sending the pickup request. These included Pickup Ready Time, Delivery From Time, Class, Reference Numbers and accessorials.

WWEX

  • Fixed E-Dispatch issue where the phone number extension for the shipper and consignee was not being included.
  • Fixed issue where E-Docs were coming through the API after E-Dispatching while the "Enable Electronic Documents" setting was disabled.

Bazaar

  • Fixed issue where the data from the carrier's API via the seller's end was pulling the wrong PRO #.

PO Reference

  • Fixed display issue for the customer tool "PO Reference #" where the "Placeholder" text was not displaying within the field when viewing the full form.

QBO Sync

  • If using the QBO sync and a PO Reference value exceeds 30 characters, the system will truncate the PoReference string due to QBO limits.

Historical Fuel

  • Fixed issue where historical fuel entries were not saving correctly for schedule types.

Logistiq

  • Fixed issue to increase the Shipment Value limit to 1 million.

Cargo Cover

  • Fixed issue where the nameAssured will now be sent as the Customer Name of the load and the countryISO.
  • Fixed issue where the currency on the insurance certificate will be reflected from the currency set on the customer's profile.

Report Builder

  • Fixed issue where category "Commission Type User" on Shipment reports was not pulling back data correctly based on Carrier or Customer Sales Rep.

Global GetLoads API

  • Fixed issue where the remitTo and remitAddress were not pulling.

Customer Upload Logo

  • Fixed issue where if a customer logo was uploaded, from the staff login side, the customer logo was not appearing when visiting the customer profile.

Advanced Required Fields

  • Fixed issue where if "Shipment Value" was set as a required field, $0 was acceptable. Logic has been updated so that users now need to have a value greater than 0 in this field if it's set to required.

Custom Reference Fields

  • Fixed issue where the calendar pop up modal for date/time custom reference fields was getting cut off if the position was at the bottom of the screen.
  • Fixed issue where the date indicated in a date/time custom reference field was not matching what was displayed on the BOL document.

Default Product

  • Fixed issue where if a default product is set, the info was not appearing in the full or short form.

Delivery Notifications

  • Fixed issue where the origin address was showing as the destination address in the Delivery Notification email.

Accessorials by Pickup/Drop

  • Fixed issue where if an accessorial was assigned to an address book entry for drop points it was being added on any stop regardless if it was a pickup or drop.
  • This occurred when the user used the ZIP code field to search up address book entries and selected the address using this function.

BW App

  • Fixed issue where dates and times showed discrepancies between the app and TMS.