--- title: "Winter '25 Transportation Profile Processing Logic" slug: "winter-25-transportation-profile-processing-logic" tags: ["Compiled from User Guide", "Admin", "Transportation Profiles", "Winter '25"] updated: 2025-02-05T17:58:12Z published: 2025-04-30T17:25:22Z canonical: "documents.revenova.com/winter-25-transportation-profile-processing-logic" --- > ## 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 '25 Transportation Profile Processing Logic ## **Overview** ## Transportation Profile Processing Logic When a TMS Load is created and worked, there are several Transportation Profiles that can impact the process: - The **Customer** Account’s Transportation Profile. - The **Bill To** Account’s Transportation Profile. - The **Stop Location** Accounts’ Transportation Profiles. - The **Global** Default Transportation Profile. - The **Carrier** Account’s Transportation Profile. The following details how these Transportation Profile (TP) records and associated routing guide information (if present) interact with the Load during it's lifecycle: 1. Stop Creation 1. The Stop’s **Appointment Required** field is copied from the **Location** TP. 2. If null, the Stop’s **Instructions** field is copied from the **Location** TP. 2. Stop Creation/Update 1. If null, the Stop’s **Shipping/Receiving Hours** field is copied from the **Location** TP. 3. Load Creation/Update 1. A Transportation Profile for the Load is searched for in this order: **Customer →** **Global**. If null, the Load’s Payment Terms field is copied from the TP (if present there)**.** 2. If null, the Load’s Customer Bill To field is copied from the **Customer** TP. 3. The Load’s **Tax Exempt** field is copied from the **Customer** TP. 4. The **Customer TP Customs Brokers** records are examined for any cross-border loads, and the appropriate one assigned to the load. 5. The C**arrier TP Carrier Remit To** is populated when a load is tendered to a Carrier. 4. Load Accessorials 1. If **Default Accessorials** are defined for any stop account’s Transportation Profile, they are automatically added to the load on creation. 5. Stored-Rate Customer Quote Auto-Creation 1. A Transportation Profile for the Load is searched for in this order: **Customer →** **Global**. 2. Lane/Rate matches for the Load from the TP are searched for and used to construct quote(s). 3. TP Fuel Surcharge is used to calculate the quote’s fuel surcharges, if present. 4. TP Accessorial charges are used, if present. 6. Carrier Quote Auto-Creation 1. A Transportation Profile for the Load is searched for in this order: **Customer →** **Global**. 2. Carrier Service/Lane/Rate matches for the Load from the TP are searched for and used to construct quote(s). 3. If a Carrier is in the **Carrier Exclusion** object for a given customer/global Transportation Profile, it is not considered. 4. For Stored Rate Quotes: 1. The Fuel Surcharge associated with the Carrier Service from the TP is applied. 7. Customer Invoice Creation 1. The Load’s **Bill To TP** is used to determine the invoice’s **POD Required** and **Billing Method** values. 8. Load Tender 1. A Transportation Profile for the Load is searched for in this order: **Customer →** **Global**. 2. The TP defines which Carrier Service record is used to determine tendering method and carrier contacts. 9. Tender Document Creation 1. A Transportation Profile for the Load is searched for in this order: **Customer →** **Global**. 2. The TP determines which tender documents to produce, if present. 3. Else, the **Product Configuration** global setting determines which documents to produce. 10. Bill of Lading Creation 1. The SCAC field from the **Carrier** TP is displayed on the Bill of Lading. 11. Carrier Equipment Type and Cargo Carried 1. Carriers can be filtered in/out of the Available Carrier list via the Carrier Equipment Type related list and the Cargo Carried picklist on the **Carrier** TP.