Freight Table Setup Guide
Learn how to configure freight rate tables based on your operations.
Written by Jess Hamilton
Updated at March 10th, 2026
Table of Contents
Start Here
Use this guide to understand how freight tables should be designed based on your freight billing model.
This article explains:
- The difference between Primary Carrier freight pricing and Delivering Carrier freight pricing
- When to create carrier-specific freight tables
- How the system determines freight table precedence
- How to avoid configuration conflicts
For step-by-step instructions on creating freight tables in the system, see the How to Configure Freight in Titan Logistics article.
Freight tables determine the freight cost applied when fuel is delivered from a terminal to a location. These tables control both:
• Accounts Receivable (AR) – what your customer is charged for freight
• Accounts Payable (AP) – what you pay the carrier that hauled the load
Freight tables are configured by Source Region (Rate Group) and then applied to Terminal → Location combinations for each Fuel Group (Product category).
Before configuring freight tables, it is important to consider how your organization charges freight operationally, because this determines how the tables should be structured in the system.
Operational Freight Model
Most fuel distributors follow one of two freight billing models.
1. Standardized Freight Based on the Location’s Primary Carrier
In this model, the freight rate charged to the end customer is based on the location’s primary carrier, regardless of which carrier actually delivers the load.
This approach keeps the billing experience consistent and predictable for the customer, even when a different carrier is used due to availability, scheduling, or operational needs.
When using this model:
• AR freight tables are created with the Carrier field left blank
• The freight rate is determined by Terminal → Location → Fuel Group
• AP tables are created for each carrier to determine what the system pays the delivering carrier
This model ensures the customer experiences stable freight pricing even if the operational carrier changes.
2. Freight Based on the Delivering Carrier
In some operations, that do not use the primary carrier logic to keep billing consistent, the freight charged to the customer changes depending on which carrier delivers the load.
When using this model:
• AR freight tables are created per carrier
• The freight rate will vary depending on the delivering carrier
• AP tables are also created per carrier to track carrier payables
This approach means freight billed to the customer can change depending on the carrier used for delivery.
Important: Freight Table Precedence and Configuration Conflicts
Because the system supports both operational models, the way freight tables are configured should align with how your business chooses to charge freight.
Before creating freight tables, it is important to understand how the system resolves situations where multiple AR tables could apply to the same lane – and why this should never occur.
A configuration conflict can occur if the same Location + Terminal + Fuel Group combination appears in:
• an AR table where Carrier is blank, and
• an AR table where Carrier is populated
Example:
Table |
Type |
Carrier |
Location |
Terminal |
Fuel Group |
|---|---|---|---|---|---|
Table A |
AR |
-- |
L2 |
T1 |
Gas |
Table B |
AR |
C2 |
L2 |
T1 |
Gas |
In this situation, the system has two possible AR freight rates that could apply to the same delivery.
The system resolves this using lookup precedence.
AR Freight Lookup Order
- Carrier + Location + Terminal + Fuel Group
- Carrier Blank + Location + Terminal + Fuel Group
Because the carrier-specific configuration is more specific, it will take priority.
Result
• If Carrier C2 delivers → the system uses the carrier-specific AR table
• If any other carrier delivers → the system uses the carrier-blank AR table
This means the carrier-specific AR table acts as an override to the standard AR freight rate for that lane.
If this overlap is created unintentionally, it may cause freight charges for the same location to vary depending on which carrier delivers the load.
Primary Carrier Freight Logic
Many fuel distributors prefer to keep freight billing stable for the end customer, even when operational needs require another carrier to deliver the load.
To support this, the system allows AR freight tables to use Primary Carrier Logic.
When the Carrier field is left blank on an AR freight table, the system treats that table as the standard freight rate for that lane.
During invoicing, the system determines the AR freight rate based on:
- Location
- Terminal
- Fuel Group
The delivering carrier does not affect the AR rate.
Example:
Location L1 has a standard AR freight rate.
- If Carrier C1 delivers → AR uses the standard rate
- If Carrier C2 delivers → AR still uses the same standard rate
Only the AP freight changes depending on the carrier that actually hauled the load.
Carrier-Specific AR Freight Tables
Some operations charge freight based on the carrier that delivered the load.
In this case, AR freight tables can be configured per carrier.
Example setup:
Table |
Type |
Carrier |
|---|---|---|
AR Table – C1 |
AR |
C1 |
AR Table – C2 |
AR |
C2 |
When configured this way:
- If C1 delivers → AR uses C1 table
- If C2 delivers → AR uses C2 table
This means the customer freight rate will change depending on the delivering carrier.
Freight Table Lookup Logic
The system determines which freight rate to apply using a lookup precedence rule.
AR Freight Lookup
- The system first searches for an AR freight table matching:
- Delivered Carrier
- Location
- Terminal
- Fuel Group
- If no carrier-specific AR table exists, the system uses the AR table matching (primary carrier business case):
- Carrier Blank
- Location
- Terminal
- Fuel Group
Carrier-specific AR tables therefore act as overrides to standard freight pricing.
AP Freight Lookup
AP freight always reflects the carrier that actually delivered the load.
The system searches for:
- Delivered Carrier
- Location
- Terminal
- Fuel Group
Choosing the Right Setup
When configuring freight tables, first determine how your organization charges freight.
If You Want Stable Customer Freight
Create:
- AR tables with Carrier blank
- AP tables for each carrier
Result:
- Customer freight remains consistent.
- Carrier payments vary by carrier.
If You Want Freight to Follow the Delivering Carrier
Create:
- AR tables per carrier
- AP tables per carrier
Result:
- Customer freight varies depending on the delivering carrier.
Creating a Freight Table
Tip: Detailed step-by-step instructions are included in the How to Configure Freight in Titan Logistics article.
Navigate to Freight Service > Freight Rates > Create Freight Rate.
Complete the following fields.
Table Name
Free text field used to identify the freight table.
Example: Rate Group 142 – ABC Transport
Table Type
Choose whether the table applies to Customer Specific or Standard
If Customer Specific is selected:
- Select the Customer
- The Location list will automatically filter to locations belonging to that customer
- Each location in the system is assigned to a customer during initial setup, allowing the system to filter locations appropriately.
Select Location(s)
Choose the locations the freight table should apply to.
Freight rates are ultimately calculated at the Terminal → Location level.
Select Carrier(s)
Choose the carrier associated with the freight table (if you bill based on the carrier who delivered).
Leave Carrier blank WHEN
- You are creating standard AR freight tables using primary carrier logic. This means the freight rate charged to the customer does not depend on which carrier delivered the load. Instead, the freight rate is standardized for the lane.
Select a Carrier WHEN
- You want the freight rate to apply only when that carrier delivers the load.
Carrier selection is required when creating:
- AP freight tables
- Carrier-specific AR tables
Select Source Region(s)
The Source Region represents the freight rate grouping.
A rate grouping is a collection of terminals located in the same geographic area that generally have similar freight costs to a group of locations.
When a Source Region is selected, the system automatically loads the Terminals assigned to that region.
Select Terminal(s) / Bulk Plants
The terminals associated with the selected Source Region will appear automatically.
Freight rates will be configured for each Terminal → Location combination.
Account Type
Choose whether the table applies to Accounts Receivable (AR) or Accounts Payable (AP).
AR tables determine the freight charged to customers.
AP tables determine the freight paid to carriers.
Effective From / End Date
Defines when the freight table becomes active.
The End Date is optional and can be left blank if the table should remain active indefinitely.
Fuel Groups
Select the Fuel Groups (product categories) that the freight table applies to.
Examples include:
- Diesel
- Gas (Regular / Midgrade / Premium)
Each selected fuel group will appear as a column in the freight rate table.
Generating the Freight Table
After entering the configuration fields, select Generate Table.
The system will generate a Terminal → Location freight matrix.
Each row represents a lane between a terminal and a location.
Example structure: Terminal | Location | Diesel Rate | Gas Rate | Assumed Miles
Users then enter the freight rate for each fuel group.
Entering Freight Rates
The most important values entered in the freight table are the freight rates for each Terminal → Location lane.
Example:
Terminal |
Location |
Diesel Rate |
Gas Rate |
|---|---|---|---|
Baltimore East |
Nat'l Arboretum |
0.1263 |
0 |
Baltimore East |
Marty Baldwin |
0 |
0.2739 |
Rates are typically entered in USD per gallon.
Assumed Miles (Optional)
The Assumed Miles field can be entered for reference purposes.
This value does not control freight calculations but can help explain how a freight rate was derived.