--- title: "Winter '26 Stored Rate Support" slug: "winter-26-stored-rate-support" tags: ["Admin", "Expanded Content", "Lanes and Zones", "Rate Entry", "Winter '26"] updated: 2026-06-02T15:32:53Z published: 2026-06-02T15:32:53Z canonical: "documents.revenova.com/winter-26-stored-rate-support" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Winter '26 Stored Rate Support Create stored/negotiated rate entries with the [Rate Entry Detail](/previous-releases/docs/winter-26-rate-entry-detail) Lightning Web Component (LWC) from TMS Admin or related lists in the [Transportation Profile](/previous-releases/docs/winter-26-customer-transportation-profile#rate-entries) and Lane records. To view a list of all customer and carrier stored rates in the TMS, go to **TMS Admin** → **Rate Entries**. ![You can create, edit, or delete rate entries from TMS Admin. Filter the view by creating a new view.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Global Rate Entry View.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) ## Lanes in Rate Entries In the Rate Entry Detail LWC, the **Lane** field is required to create a Rate Entry. Search for a Lane or create a new Lane with the **New** button, which will open the [Lane Detail](/previous-releases/docs/winter-26-lane-detail) LWC. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Rate Entry Lane Field(1).png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) > [!NOTE] > **Note**: One Lane can be used for several different Rate Entry records, but a Rate Entry can only have one Lane. ### Match Priority The **Match Priority** field for the Rate Entry is automatically set based on the Lane selected. The value of the **Match Priority** field matches to the Lane’s **Match Priority** field. > [!NOTE] > **Note**: The Rate Entry’s **Match Priority** is automatically populated from the Lane selected but can be overridden in the [Rate Entry Detail](/previous-releases/docs/winter-26-rate-entry-detail#required-fields) LWC. > > The Lane’s **Match Priority** is automatically populated and cannot be changed. Use the matrix in this section to see how the value for the Lane’s **Match Priority** is determined. If a Lane has any **Origin** or **Destination Type** that is not *Zone*, then the match priority uses the following values based on the type selected in the [Lane](/previous-releases/docs/winter-26-lane-detail) LWC. ![The values come from the Lane LWC for either the Origin Type or Destination Type fields.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Lane Origin-Destination Type.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) | Origin/Destination Type | Value | | --- | --- | | Location | 10 | | Postal Code | 40 | | Zip5 | 60 | | Zip3 | 80 | | City/State | 100 | | State | 120 | | Country | 140 | If a Lane has an **Origin** or **Destination Type** that is *Zone*, then the match priority uses the following values based on the **Zone Type** in the [Zone Detail](/previous-releases/docs/winter-26-zone-detail) LWC. > [!NOTE] > **Note**: The **Category** field must have the *Rate Entry* value for the Lane using this Zone to be available to select when setting the **Lane** field for a Rate Entry. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Zone Type Values.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) | Zone Type | Value | | --- | --- | | Location | 20 | | Mixed | 30 | | Postal Code | 50 | | Zip5 | 70 | | Zip3 | 90 | | City/State | 110 | | State | 130 | | Country | 150 | The **Match Priority** field is calculated based on the sum of the **Origin** and **Destination** **Type** of the Lane. For example, if a Lane has **Origin Type** as *Zip5* and **Destination Type** as *Zone* (where the **Zone Type** is *Mixed*), the values to be added together are 60 and 30, respectively. Therefore, the **Match Priority** field is set to 90. Use the following matrix to see how the Lane sets the **Match Priority** value. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/image(9).png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) #### Match Priority Use Case If two Rate Entry records match when generating a stored rate Customer Quote, the TMS compares the **Match Priority** field from both Rate Entry records. The Rate Entry with the lowest value in the **Match Priority** field is used in the Customer Quote. For example, if one Rate Entry record has the **Match Priority** set to 120, and the other Rate Entry record has the field set to 80, then the Rate Entry record with **Match Priority** as 80 is included in the Customer Quote. > [!NOTE] > **Note**: Stored rate entires take precedence and apply first before any Accessorial [Carrier Markup](/previous-releases/docs/winter-26-carrier-markup-groups#markups-and-rate-entries). When a Carrier Quote is created and saved manually, any matching Carrier Markup Group is applied to generate the Customer Quote, even when a customer stored rate entry is available. ## Fuel Surcharges The Rate Entry record specifies the **Fuel Surcharge** when the **Rate Type** is *Freight+Fuel* or *Fuel*. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Rate Entry Fuel Surcharge.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) Therefore, the fuel surcharge schedule can vary by the other fields defined in the Rate Entry, such as **Category**, **Carrier Service**, **Lane**, and **Mode**. See the [Fuel Surcharge Setup](/previous-releases/docs/winter-26-fuel-surcharge-setup) article to set up the schedule for the **Fuel Surcharge** field in the Rate Entry. ## Accessorial Negotiated Rates All stored/negotiated rates should be set up as a Rate Entry with a **Rate Type** set to *Accessorial* and specifying the Accessorial. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Rate Entry Accessorial.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) See the [Rate Entry Detail](/previous-releases/docs/winter-26-rate-entry-detail#accessorial-rate-entries) article for more information about Accessorial Rate Entries. ## Rate Calculation Rate Entries can have a **Base**, **Minimum**, or **Maximum** calculation defined, and the TMS uses the following logic when calculating the cost for a quote: - If the **Base Rate Calculation** is greater than (>) the **Maximum Charge Calculation**, use the **Maximum Charge Calculation**. - If the **Base Rate Calculation** is less than (<) the **Minimum Charge Calculation**, use the **Minimum Charge Calculation**. - If the **Base Rate Calculation** is between the **Minimum** and **Maximum Charge Calculation**, use the **Base Rate Calculation**. See the [Rate Entry Detail](/previous-releases/docs/winter-26-rate-entry-detail#base-rate-calculation) article for more information about how pricing is determined for these calculations. ## RFP Support The TMS supports Customer and Carrier RFPs, including the bulk import of Lanes and Rate Entries via a CSV file upload to efficiently set up, respond, and operationalize RFP-based stored rates. > [!WARNING] > **Caution**: Uploading matrix-based rate entries is currently not supported. To set up matrix-based rate entries, such as for deficit rating, see the [Rate Entry Detail](/previous-releases/docs/winter-26-rate-entry-detail#calculation-axis-setup) article. In the [RFP Banner](/previous-releases/docs/winter-26-rfp-banner) LWC, select the **Upload Rate Entries** button, define the rate entry type, and upload the CSV file. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/RFP Upload Rate Entries.png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/RFP Define Rate Entry Type(1).png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) If a Lane does not exist when uploading and creating Rate Entry records with the RFP Banner LWC, the TMS automatically creates the Lane record as part of the upload process. If the uploaded CSV file contains values for the optional **Expected Load Volume** and **Shipper Comments** columns, those values will be associated with the Rate Entry record. ![""](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Rate Entry Optional Features(1).png?sv=2026-02-06&spr=https&st=2026-06-02T15%3A02%3A50Z&se=2026-06-02T15%3A17%3A50Z&sr=c&sp=r&sig=blprdR%2BnsOFB6wbxwqmeu2REjofycjiiP4B36vJ%2Fbts%3D) A feature in Salesforce that enhances the user experience by providing interactive and customizable components within Salesforce applications. Revenova uses Lightning Web Components to deliver features that can be tailored to suit your specific needs and preferences.