Revenova TMS Release Notes

Winter ’26 Release Enhancements

Brokerage & Fleet Enhancements

Security Enhancements

Revenova consistently seeks to implement the latest industry security policies and practices. The Winter ‘26 release includes additional features to support fraud prevention and stronger data security. In that effort, additions to the Revenova package are likely to impact current User setup and permissions. Thoroughly validate security and permission settings in the sandbox before proceeding with a Production upgrade to prevent disrupting day-to-day business.

The new Required Field Scanner component provides easy searching to determine a User’s access and field permissions.

Artimus™ AI: Truck Postings to Load Board Matching

Previously, Artimus™ AI could create truck postings from text to generate post capacity.

Now, you can turn truck postings into opportunities—for carriers and brokers.

Carriers who share available trucks with Artimus can unlock a load board to find and bid on loads. Brokers gain more truck postings to cover their loads faster, and Artimus helps you match carriers and brokers to loads.

With this new feature, you can look forward to:

• 🧠 Smart Matching: Carriers posting trucks with Artimus to gain access to the RFQ Load Board LWC.

• Lane Preference: Carriers adding Lane Preferences to lanes they prefer to cover, giving brokers key insights into one of their preferred carriers.

• ✅ Broker Advantage: More truck postings mean more options to cover loads quickly.

• ⚙️ Broker Control: Brokers decide which loads and carriers are visible—maintaining full control.

• 💰 Book It Now: Allow carriers to quickly bid on a load at the broker’s proposed rate, making it easier and faster for them to inform the broker they want to cover the load.

How It Works

1. The carrier submits a Truck Posting via Artimus™ AI by emailing the email handler or by using the Text to Truck Posting LWC.

2. If the Carrier Transportation Profile has the Enable RFQ Load Board field checked and the Contact or email address is associated with the Transportation Profile, they will receive a Carrier Load Board email.

   

3. The carrier can access the load board to:

   • Add Lane Preferences,

   • Match the Truck Posting to cover Loads,

   • Bid on matching Loads, and/or

   • Book the Load with the broker’s offer rate.

Encourage truckers to submit their available trucks by using this load board to match them up with suitable loads. Brokers will have control over which loads and which carriers can see the available loads, just as they do now.

New AI Models

Additionally, Artimus now supports the gpt-5 and gpt-5-mini AI Models.

These models are faster and more accurate than previous AI models, thanks to their use of reasoning. AI models with reasoning can solve complex problems, reduce hallucinations, use fewer tokens, and deliver more reliable responses. In short, these new models lead to a better experience for your customers.

Select these new models in the AI Console Configuration.

Automate Appointment Scheduling

We’re proud to announce a powerful new enhancement to the TMS: Automated Appointment Scheduling with Email Loop Integration.

This new functionality eliminates the need for manual scheduling coordination, providing users with a faster, smarter, and fully automated way to manage load pickup and delivery appointments—all within the TMS.

Users can now:

• 📧 Send Appointment Request emails directly from the Appointment Setting view in Fleet Management Console or Load Detail LWC.

• ✅ Allow shippers, consignees, or customers to confirm, decline, or propose new times via a one-click guest page.

• 🔄 Automatically update appointment statuses and times instantly with no manual entry required.

For operations that handle high volumes of appointments, Revenova now offers Auto-Email Scheduling.

Once enabled, the system automatically sends appointment requests to the appropriate contacts based on your configuration. Appointments are intelligently grouped by location and sent in consolidated messages—streamlining communication and improving scheduling accuracy.

Revenova has also introduced additional supporting enhancements to make appointment scheduling simpler and cleaner, such as:

• Filtered Contacts - Only Contacts with the ‘Appointments’ transportation role appear in the Appointment Setting views.

• Load Email Integration - Appointment requests emails automatically respect your default To, CC, and BCC settings.

• Built-In Communication Loop - Confirmed and proposed appointments are automatically reflected in the system, ensuring total data accuracy.

Ready to get started with smarter appointment scheduling? Check out the Appointment Request Setup instructions!

How It Works

1. The Contact that received the Appointment Request email selects the Respond button to enter the appointment guest email loop.

2. The Appointment Request Response LWC populates in the email loop with the Stops for which the internal User is requesting an appointment time.

3. The Contact has options to select depending on whether the request has an initial proposed time:

   • If the internal User initially proposed an appointment time, the Contact can:

     • Confirm the appointment time

     • Decline the appointment time

     • Propose new times

   • If the internal User did not initially propose an appointment time, the Contact can only propose new times.

4. Once the Contact makes their selection or proposals, they select the Save & Submit button.

5. The TMS automatically updates the appointment request information depending on the Contact’s response.

If either the Contact or the internal User confirms an appointment time, the Contact receives an Appointment Confirmation when the Confirmation Method field on the Appointment Request is set to Email Me. The confirmed appointment time is automatically updated in the TMS for the Stop on the Load.

EDI Event-Based REST Architecture

We’re excited to introduce RESTful API endpoints using JSON for the EDI service. That is, EDI Partner VANs call our endpoints to process EDI events more quickly and efficiently with the TMS.

Additionally, the following features are included with the new EDI REST API architecture:

• EDI Transaction Logs: If the REST API is enabled for EDI, inbound and outbound events will always create EDI Transaction records.

• Data Cleanup Job: To handle the increased data from EDI Transaction records, a new data cleanup job is available as a batch process to control how long to retain specific EDI transaction types.

• External Client App: You can now set up and enable multiple EDI providers simultaneously, eliminating the need for a single enabled Partner VAN credential in TMS Admin.

While our existing SOAP (XML) API will continue to be supported as a deprecated API process, REST is now the recommended integration approach. New features, enhancements, and optimizations for EDI will be delivered primarily through the REST API. Customers who remain on SOAP may not have access to the latest capabilities as they become available.

Why It Matters

The EDI REST API architecture was designed to improve nearly every aspect of our EDI integration:

• ✨ Better performance: EDI Partner VANs call our endpoints, resulting in much faster processing and the ability to handle high volumes of transactions. We’ve also added a PATCH endpoint that allows VANs to return the status of an outgoing EDI message.

• ⏩ Simpler, faster development: REST uses standard HTTP methods and widely adopted conventions, making integrations easier to build, test, and maintain across modern frameworks.

• 🔮 Clearer, more predictable behavior: Standardized HTTP status codes and streamlined responses make error handling and debugging more straightforward.

How It Works

1. Set up an External Client App with EDI Partner VANs (Kleinschmidt, Cleo, and/or Custom EDI).

2. Ensure that the API User has the TMS EDI API permission set.

3. Complete the EDI Setup in TMS Admin → Configuration, and ensure that the following fields have these values:

   1. EDI Enabled: Checked

   2. EDI Shipment ID: Load Number

   3. Use REST API for EDI: Checked

   4. EDI Context User (for each connected VAN): API User

4. Configure the EDI Transaction Expiration fields in TMS Admin → Configuration.

5. Run the EDIWatcherJob and DataCleanupJob batch processes to handle queued outbound transactions and remove older EDI Transaction records.

RateIQ+Markup Rate Entries

Our RateIQ LWC delivers real-time carrier market rates based on each customer’s configured data sources.

Now, we’re taking it a step further.

This new feature lets users create new RateIQ+Markup Rate Entries—enabling the TMS to automatically calculate a rate on a non-LTL Load using RateIQ’s market intelligence and markup the price. That is:

• ⚡ Faster quoting leading to more opportunities won

• 📈 Smarter pricing using RateIQ’s dynamic market data with a markup

• 🧠 More automation, less manual work

• 💼 Seamless quoting experience directly within the TMS

Spot a Customer Quote instantly from within the TMS, Customer Portal, or with Artimus™ AI—all while leveraging the pricing power intelligence of RateIQ.

Use the new RateIQ Freight, RateIQ Fuel, and RateIQ Total fields in the Customer Quote record to view the RateIQ market price at the time the quote was generated and without the markup.

These fields are calculated based on the Freight+Fuel and Fuel values in the RateIQ LWC at the time the quote was generated. Check out RateIQ Calculations to see an example calculation.

How It Works

1. In TMS Admin, ensure there are active RateIQ Calculations with configured data sources for non-LTL Modes.

2. In TMS Admin Configuration, set a user for the new RateIQ Rate Entry User field who has access to all RateIQ data sources in the Global Settings section.

3. Create a RateIQ+Markup Rate Entry where:

   • Category = Customer

   • Rate Type = Freight+Fuel

   • Status = Accepted

   • Rate Method = RateIQ+Markup

   Additionally, you can add a fuel schedule in the Fuel Surchage field of the Rate Entry to mark up instead of the RateIQ Fuel value.

4. Create or update a Carrier Markup with the new Markup Basis field set to RateIQ and select the non-LTL Mode it applies to.
   The Mode must match the Mode on the Rate Entry and RateIQ Calculations.

5. Add the Carrier Markup Group that has the RateIQ Carrier Markup to the Customer Transportation Profile.

When a Load is configured and the RateIQ+Markup Rate Entry matches, the TMS calculates the RateIQ Freight and Fuel values and then marks up the Customer Quote based on two settings:

• The Carrier Markup’s value in the Markup Type field.

• The Rate Entry’s schedule in the Fuel Surcharge field, if any.

Load Lock Manager

Manage locked Loads productively with the new Load Lock Manager LWC, replacing the Load Lock Viewer. The enhancements made to the load locking feature allow certain users flexibility in managing these locked Loads.

Users who are Load Locking Administrators can easily view and filter locked Loads in the LWC and perform the following actions:

• 🔓 Unlock Loads and clear the queue

• 🔑 Pass the Load Locks to another User

• ⏱️ View the queue of Users waiting for a Load Lock

Admins can update the User’s abilities to lock Loads, such as limiting the number of load locks a User can hold at one time, as well as restricting the number of times a User can renew a Load Lock.

What’s even better—Users can now join a queue for a locked Load in the Load Lock Status LWC.

Additionally, to view whether a Load is locked from the Load list view, you can add the new Locked field as a field to display.

How It Works

1. Configure the following load locking setting fields for each User:

   • Load Locking Administrator

   • Load Locking Max Count

   • Load Lock Renewal Limit

2. Configure the Load Locking fields in TMS Admin → Configuration:

   • Enable Operations Load Locking

   • Load Locking Hold Time

3. For Load Locking Administrators, select the App Launcher and search for and select ‘Load Lock Manager’.

Load Locking Admins can also use the Load Lock Status LWC in the Load record to perform the same load locking actions.

File Upload Web Service

Revenova now makes it easier than ever for customers to connect with third-party partners and internal IT teams. For example, a document-processing partner can automatically upload PODs, or an insurance provider can push certificates of insurance directly into the TMS as they are issued. With our new RevenovaWebService, files can be uploaded directly into the TMS through a secure endpoint.

Powered by a Salesforce External Client App, this new endpoint securely receives and processes files into the TMS, saving them to custom and packaged objects, giving customers the freedom to tailor integrations to their exact business needs.

This new web service fully respects Customer Invoice Document settings configured in the TMS. This allows users to confirm that all required documents are uploaded and validated before invoicing.

Supported Customer Invoice Document types may be viewed or queried through the TMSReferenceDataService web service.

How It Works

1. Create and configure an External Client App to accept files.

   1. Add a permission set with the appropriate security level for partners uploading files.

2. Configure Customer Invoice Document settings to determine how certain file types are processed by the TMS.

3. Share the service URL with third-party partners so they can begin sending files immediately.

Fleet Enhancements

Consolidate Trip Plan Stops

Smarter Stop Consolidation for Cleaner Trip Plans & Accurate Telematics

We’re excited to introduce a powerful new enhancement for Fleet users in Revenova TMS: Automatic Duplicate Stop Consolidation for Trip Plans when sending route data to Samsara, Catena, and Trimble integrations.

What It Does

When a Load involves both a delivery and pickup at the same physical location—for example, delivering to Dock 12 and picking up from Dock 15 at the same warehouse—Revenova now gives you the option to automatically consolidate those duplicate stops into a single stop when sending trip data to your telematics partners.

This enhancement works seamlessly in the background and ensures that:

• Your Trip Plan in Revenova still shows both delivery and pickup legs

• Your ELD and telematics platforms receive only one clean, de-duplicated stop

Why It Matters

1. Eliminate Driver Confusion

Drivers see one clear, consolidated stop—reducing misunderstandings and keeping the focus on the task, not the tech.

2. Prevent Inaccurate Stop Updates in Catena & Trimble

In geofenced systems, duplicate stops at the same address can create false readings. This can cause:

• Missed departure updates

• Incorrect “incomplete stop” statuses

• With consolidation, arrival/departure tracking stays accurate and aligned with real driver activity.

3. Avoid “Skipped Stop” Errors in Samsara

Samsara’s automated tracking could flag the second stop as "skipped" due to the absence of a second geofence entry. This enhancement ensures your trip data is interpreted correctly every time.

How It Works

You don’t need to change anything—this enhancement operates as part of the existing integration flow. The Trip Plan in Revenova still shows all distinct stops for operational clarity, but your drivers and telematics providers get the simplified, consolidated version.

The Bottom Line

This enhancement simplifies trip data, reduces errors, improves driver experience, and ensures your systems stay in sync—even when things get complex at the dock.

Ready to make smarter stops? You already are.

Miscellaneous Enhancements

• The architecture for several triggers is enhanced for the Winter ’26 release. Thoroughly test that any custom code based on these triggers is working properly. The following triggers are impacted: AccountingInboundEvent, BankAccount, CarrierPayment, Container, and CustomerPayment.

• Multiple enhancements to the MacroPoint tracking integration to support some of the latest features.

  • The MacroPoint integration supports Stop Sequencing to set Stops as arrived and departed in order. For In Transit Loads when a tracking session begins, the Stop arrival/departure date/times are included in the request.

  • Additional Customer and Carrier DOT Number fields are sent to MacroPoint to allow for easier searching and filtering in the MacroPoint Portal.

  • MacroPoint returns a code for Loads hauled by a potentially fraudulent Carrier that is displayed on the Tracking modal.

• Enhance the Customer Invoice Batch Document to use the column label “Rate” for invoices that include a deficit rating from a Customer Rate Entry and “Rate/CWT” for invoices that use an SMC3 Rate Entry.

• The Appointment Time field in the Stop Configuration Detailed and Quote Wizard LWCs displays an appropriate error message regarding the 24-hour time format.

• Update the Default Accessorial field to be optional in the Global Settings section of TMS Admin Configuration.

  • A warning displays about possible integration issues if this field is left blank.

• The Sales Status field on the Load updates correctly for inbound EDI 204 transactions, regardless of the state of the Enable Save and Rate for Load Creation field in TMS Admin Configuration.

• The Rand McNally integration uses the Postal Code field of the Stop to calculate the route mileage if a Stop cannot be validated for a Load.

• Multiple enhancements to Carrier Portal Visualforce pages allow for increased accuracy when quoting Loads or creating Truck Postings.

  • The Load Board is enhanced to allow filtering of Loads for the user logged in as either the Quoting or Tendering Contact for a Carrier Service. Prevent users from submitting quotes for unsupported Carrier Services by enabling the filtering so that only Loads matching the Mode on the Carrier Service are displayed.

  • The Truck Posting page is enhanced to filter out any Equipment Types that do not match the Mode for the selected Carrier Service. Additionally, once a Truck Posting is created, users can submit quotes for Loads with a Mode matching the selected Carrier Service.

• Enhance the TriumphPay Audit integration to send accessorial line item details even when the total accessorial charge is $0 USD.

• An enhancement for the Catena integration supports additional Cycle Override field picklist values. Users may also add picklist field values as new values are supported, as necessary.

• Enhance the Lane IQ LWC to present a PC Miler error message when a user selects a city from the list that PC Miler does not recognize.

  • To add the city/state to the API data set, create a support case in the My Transportation portal for PC Miler. Include your API key and reference the Geocoding Batch endpoint in the support case.

• Enhance the ePayment LWC to display an error message when a User has more than one Advance Payment Authority record in which prevents the Issue button from displaying.

• The LoadAndTruckPostingManagementJob2 no longer includes Load Posting records to DAT and other Load Boards with a Posting Status value of Unposted when unposting Loads.

• Improved several help texts, logos, company names, and other UI enhancements across the TMS.

• Display Line Item details in the Move Stop modal of the Load Detail and Freight Plan Console LWCs with the new Line Item TMS13 field set.

Accounting Seed Enhancements

• Enhancements for EDI REST functionality include a new TMS EDI API Accounting Seed Bridge permission set. To grant the appropriate permissions for inbound and outbound EDI transactions, apply the TMS EDI API Accounting Seed Bridge permission set to the API User for the External Client App.

• Sending bulk Billings supports setting a PDF Format for each Ledger present in a customer org. Customize the bulk Billing PDF document by Ledger for additional customization when sending Billing PDF documents.

PayIQ Enhancements

PayIQ supports creating four new Program Calculation Methods for additional customizability when calculating and paying commissions. Create new PayIQ Programs based on the following criteria.

1. A One-Time Payout at target (bonus).

2. Amount per Load Contributing to Bracket. A progressive/tiered payment schedule where the aggregate margin/revenue tiers are compensated at different Load-based flat rates.

3. Percent of Load Contribution Within Bracket. A progressive/tiered payment schedule where the aggregate margin/revenue tiers are compensated at different percentage-based rates.

4. Percent of Load Criteria After Burndown. A Participant must hit a minimum threshold before receiving compensation.