--- title: "Spring '26 Transportation Profile Processing Logic" slug: "spring-26-transportation-profile-processing-logic" tags: ["Admin", "Expanded Content", "Spring '26", "Transportation Profiles"] updated: 2026-09-02T14:22:48Z published: 2026-09-02T14:22:48Z canonical: "documents.revenova.com/spring-26-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. # Spring '26 Transportation Profile Processing Logic When a Load is created and updated, different Transportation Profiles can impact the process for several records: - The [**Global Default Transportation Profile**](/previous-releases/docs/global-default-transportation-profile) - The **Customer Transportation Profile** - The [**Carrier Transportation Profile**](/previous-releases/docs/carrier-transportation-profile) - The **Stop Location** Account’s Transportation Profile - The **Customer Bill To** Account’s Transportation Profile > [!NOTE] > **Note**: The **Location** field in the Stop object and **Customer Bill To** field in the Load object are both Account lookup data types. However, it is the Transportation Profile *connected* to the Account that will impact the Load process. ## Load Object The **Customer** and **Carrier Transportation Profile** impacts the creation and update of a Load object. ### Load Creation During Load creation, the Load object inherits some fields and related records from the **Customer Transportation Profile**: | Customer Transportation Profile (Field/Record) | Load (Field) | Data Type on Load | | --- | --- | --- | | Payment Terms | Payment Terms | Picklist | | Default Customer Bill To | Customer Bill To | Lookup(Account) | | Tax Exempt | Tax Exempt | Checkbox | | Customs Broker (**Record**) | Customs Broker (**Field**) | Lookup(Account) | See the [Customs Brokers](/previous-releases/docs/customs-brokers) article for more information about setting up customs brokers for cross-border loads. > [!WARNING] > **Payment Terms Note**: If the **Customer Transportation Profile** has a blank value for the Payment Terms field, the logic cascades to the [**Global Default Transportation Profile**](/previous-releases/docs/global-default-transportation-profile) and uses that value for the Load’s Payment Terms field instead. If both Transportation Profiles have a blank value for Payment Terms, the Load’s Payment Terms field is determined by the **Product Configuration** [Global Setting](/previous-releases/docs/global-settings). ### Load Update When a Load is tendered to a Carrier, the **Carrier Remit To** field on the **Carrier Transportation Profile** populates on the Load. ## Stop Object The **Stop Location** Account’s Transportation Profile impacts the creation and update of the Stop object. ### Stop Creation Only During Stop creation *only*, the Stop object inherits some fields from the **Location** Account’s Transportation Profile, depending on whether the Stop is a Pickup or a Delivery stop: | Customer Transportation Profile (Field) | Stop (Field) | Data Type on Stop | | --- | --- | --- | | Pickup Appointment Required | Appointment Required | Checkbox | | Delivery Appointment Required | | Default Pickup Instructions | Instructions | Long Text Area(2000) | | Default Delivery Instructions | See the [Stop Configuration Detail](/previous-releases/docs/stop-configuration-detail) article for more information about creating stops during Load configuration. ### Stop Creation and Update During Stop creation or update, the Stop object inherits either the **Shipping Hours** or **Receiving Hours** field from the **Location** Account’s Transportation Profile and populates it in the Stop object's **Shipping/Receiving Hours** field. | Customer Transportation Profile (Field) | Stop (Field) | Data Type on Stop | | --- | --- | --- | | Shipping Hours | Shipping/Receiving Hours | Text(11) | | Receiving Hours | ## Load Accessorials For every **Stop Location** Account’s Transportation Profile, if the Transportation Profile has defined [**Default Accessorials**](/previous-releases/docs/default-accessorials), those accessorials may automatically be added to the **Load Accessorials** related list in the Load record. ![The Default Accessorials in the Transportation Profiles can impact the Load Accessorials in the Load record.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Logic Load Accessorials.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) > [!CAUTION] > **Warning**: Some accessorials depend on whether the Stop is a Pickup or Delivery. If the Transportation Profile has a **Delivery** Default Accessorial (for example, *Lift Gate Delivery*) but the Stop is a **Pickup**, then the Default Accessorial is not added to the Load Accessorials related list. For example, when configuring a Stop and you select either *Same as Customer* or *Account Address* and then select an Account in the **Location** field, the TMS will go to the Transportation Profile associated with the selected Account. If the accessorial’s type matches the Stop’s type (Pickup or Delivery), then that **Default Accessorial** record will be added to the **Load Accessorials** related list for the Load. The [Default Accessorials](/previous-releases/docs/default-accessorials) article contains more information about configuring default accessorials for a Transportation Profile. ![The default accessorials defined in the Transportation Profile will be automatically added to a Load if the Transportation Profile is a Stop](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Default Accessorials.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) ## Rate Entries [Rate entries](/previous-releases/docs/rate-entry-detail) stored in the Transportation Profile are searched for and used to construct quotes for a Load automatically. The **Rating Source** field in the Transportation Profile determines whether to search for matching rates only in the **Customer Transportation Profile** or for rates in the **Global Default Transportation Profile**. ![The Rating Source field in the Transportation Profile determines to search only in the Customer Transportation Profile or include Global.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Rating Source Field.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) For more information about rate entries, see the [Rate Entry Detail](/previous-releases/docs/rate-entry-detail) article. ### Customer Quote Auto-Creation Rate entries with the **Category** field as *Customer* are stored in the **Customer Transportation Profile** in the **Customer Rate Entries** related list. ![The Category and Transportation Profile fields determine the related list for the specified Transportation Profile for the Rate Entry.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Customer Rate Entry.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) The matches for customer rate entries start in the **Customer Transportation Profile**. If the customer on the load has customer rate entries with a **Lane** that matches to the Load, then those rate entries are used to construct the customer quote automatically. ![A Rate Entry that matches from the Customer Transportation Profile to the Load automatically creates a Customer Quote record.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Customer Quote Auto-Creation by Rate Entry.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) Suppose the **Rating Source** field in the Customer Transportation Profile is set to *Customer + Global Rates* and there are no customer rate entry matches in the **Customer Transportation Profile**. In that case, the matches for customer rate entries are also searched in the **Global Default Transportation Profile**. > [!WARNING] > **Note**: For multiple **Customer Rate Entries** in a Transportation Profile that matches a Lane, see the [Stored Rate Support](/previous-releases/docs/stored-rate-support-1-1) article for more details. ### Carrier Quote Auto-Creation Rate entries with the **Category** field as *Carrier* are stored in the **Customer Transportation Profile** in the **Carrier Rate Entries** related list. The **Carrier Service** field is additionally required to create a carrier rate entry. ![The Category and Carrier Service fields determine the related list for the specified Transportation Profile for the Carrier Rate Entry.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Carrier Rate Entry.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) The matches for carrier rate entries start in the **Customer Transportation Profile**. If the customer on the load has carrier rate entries with a **Lane** that matches to the Load, then those rate entries are used to quote the carrier automatically. For example, you can see if you successfully quoted a carrier automatically with a Carrier Rate Entry with a success toast message: ![When a carrier has been successfully quoted with a carrier rate entry, the message will describe the type of request and to which carrier.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Carrier Quote Auto-Creation by Rate Entry.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) If the **Rating Source** field in the Customer Transportation Profile is set to *Customer + Global Rates* and there are no carrier rate entry matches in the **Customer Transportation Profile**, then the matches for carrier rate entries are also searched in the **Global Default Transportation Profile**. > [!WARNING] > **Note**: For multiple **Carrier Rate Entries** in a Transportation Profile that matches a Lane, see the [Stored Rate Support](/previous-releases/docs/stored-rate-support-1-1) article for more details. #### **Carrier Exclusions** If the Customer or Global Transportation Profile searched and matched has a Carrier record in the [**Carrier Exclusions**](/previous-releases/docs/carrier-exclusions) related list, then that carrier is not considered when automatically generating carrier quotes with rate entries. ![Carriers can be excluded from automatically creating carrier quotes with rate entries in the Carrier Exclusions related list.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Carrier Exclusion.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) ## Customer Invoice When a Customer Invoice record is generated, some fields are inherited or populated from the **Customer Bill To** Account’s Transportation Profile from the Load: | Customer Transportation Profile (Field Name) | Customer Invoice (Field Name) | Data Type on Customer Invoice | | --- | --- | --- | | POD Required | POD Required | Checkbox | | Billing Method | Billing Method | Picklist | | Customer Invoice Day | Invoice Date | Date | | Invoice Terms | Invoice Due Date | Date | For more information about the Customer Invoice fields populated from the **Customer Transportation Profile**, see the [Customer Invoice Generation](/previous-releases/docs/customer-invoice-generation#fields-populated-from-the-transportation-profile) article. ## Load Tendering The **Customer Transportation Profile** impacts the document tendering process for a Load. If the Customer Transportation Profile doesn’t define the logic, then it cascades to the **Global Default Transportation Profile**. If the Bill of Lading document is tendered, then the **Carrier Transportation Profile** impacts certain document fields. ### Field: Tender Documents The **Tender Documents** multi-select picklist field in the Transportation Profile determines the documents emailed to the carrier during load tendering. ![The Tender Documents field in the Transportation Profile determines what documents to tender to the carrier during load tendering.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Transportation Profile Tender Documents Field.png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D) If the **Customer Transportation Profile** has values in the Tender Documents field, then those documents will be tendered to the carrier. If the value is blank in the **Customer Transportation Profile**, then the logic cascades to the **Global Default Transportation Profile** and uses that value to tender documents instead. If both Transportation Profiles have a blank value for the Tender Documents field, the **Product Configuration** [Global Setting](/previous-releases/docs/global-settings) determines which documents to tender for the load. ### Field: SCAC If the Bill of Lading document is tendered and the **SCAC** field in the **Carrier Transportation Profile** has a value, then that field is displayed on the document. ![The Bill of Lading document displays the carrier's SCAC.](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Bill of Lading SCAC Field(1).png?sv=2026-02-06&spr=https&st=2026-07-29T01%3A50%3A51Z&se=2026-07-29T02%3A05%3A51Z&sr=c&sp=r&sig=iLlmrZBqMeJnGmiNEqwNsEXtPBI671%2Fv6%2B4GjyKBxHg%3D)