TMS Dynamic Tariff Rating Engines: Multi-Tiered Density & Commodity Classification Architectures

Strong Tower Consulting has spent more than 18 years helping asset-based carriers design, tune, and implement these rating architectures inside Truckmate, McLeod, TMW, and custom SQL-based platforms. The following is a direct architectural overview of how a production-grade, multi-tiered density and commodity classification engine is constructed and maintained.

The Core Rating Pipeline

A modern carrier TMS rating engine follows a deterministic, auditable pipeline:

1. Capture shipment attributes from EDI 204, customer portal, or order entry (weight, dimensions, NMFC, commodity description, pallet count, stackability).
2. Calculate dimensional weight and density (weight divided by cubic feet).
3. Determine base freight class using NMFC lookup cross-referenced with calculated density.
4. Apply carrier-specific exception ratings and density discount tiers.
5. Layer on accessorial logic (fuel surcharge, detention, layover, tarp, linear foot, pallet overhang, etc.).
6. Apply any customer-specific discount or contract multiplier.
7. Return final line-haul and total charge; write to billing and driver settlement records.

Database Schema Foundations

Enterprise TMS platforms store tariff data in highly normalized SQL structures. A typical schema includes the following core tables:

Performance is achieved through composite indexes, materialized views that pre-calculate common lane-density combinations, and in-memory caching layers for the most frequently rated 3-digit ZIP pairs.

Multi-Tiered Density Discount Logic

Instead of a single discount off a published class rate, sophisticated carriers implement true multi-tier density pricing. A representative tier structure might look like this:

Additional logic automatically adds linear-foot charges when a shipment occupies more than 12 linear feet on a 53-foot trailer, or applies a configurable surcharge (for example 15%) when average pallet height exceeds 72 inches with overhang.

Integration With Driver Settlement and Accounting

The rating engine must feed both the customer invoice (EDI 210) and the driver settlement module. Strong Tower recommends maintaining a single source of truth for all rating rules so that the revenue figure used for driver pay exactly matches the billed amount (less any commission or fuel surcharge pass-through). This prevents the common reconciliation problems seen when separate rating engines are used for billing versus payroll.

Fuel surcharges are typically calculated using weekly EIA averages or a carrier-specific table keyed by region and fuel price tier. Detention is accrued based on EDI 214 stop timestamps and free-time rules stored per customer or lane. All of these values flow into the final settlement calculation inside the TMS.

Implementation Best Practices

Carriers that achieve the highest contribution margins follow these practices:

• Maintain tariff versions with effective dates rather than overwriting rules.
• Store every rating calculation result with a full audit trail (input values, rule IDs, final rate).
• Expose a rating API endpoint inside the TMS so that pricing can be called from load planning, customer portals, and EDI transaction sets.
• Run nightly regression tests against a library of historical loads to ensure tariff changes do not create unintended margin erosion.
• Integrate the rating engine with SQL data-mining routines that identify lanes where density-based pricing is consistently underperforming published tariffs.

Frequently Asked Questions

How does a multi-tiered density rating engine calculate freight class and dimensional weight in a TMS?

The engine first captures actual shipment dimensions and weight from the load tender (EDI 204) or carrier TMS order entry. It then computes density as (weight / (length × width × height)) × 1728. Using the NMFC tariff table stored in the TMS, it maps the calculated density and commodity description to the appropriate freight class (50 through 500). Finally, it applies any carrier-specific exception ratings, pallet overhang multipliers, and linear-foot decking charges before returning the final line-haul rate.

What database structures are typically used to store multi-tiered carrier tariffs?

Most enterprise TMS platforms (Truckmate, McLeod, TMW) store tariffs in normalized SQL tables: TariffHeader, TariffLane, TariffDensityTier, TariffClassRate, TariffSurcharge, and TariffCommodityException. Density tiers are usually stored with effective dates, minimum weights, density breakpoints (0-1, 1-2, 2-4, 4-6, 6-8, 8-10, 10-12, 12-15, 15+ lb/ft³), and corresponding rate-per-hundredweight (CWT) or flat rates. Indexes on origin/destination 3-digit ZIP, effective date, and commodity NMFC code are critical for sub-second rating performance.

How are fuel surcharges, detention, and driver settlement rules integrated with the rating engine?

Modern TMS rating engines expose a modular pricing pipeline. After the base density/class rate is calculated, the engine sequentially applies: (1) fuel surcharge (EIA or carrier-specific table lookup by region and fuel price), (2) accessorials such as detention (hourly after free time), (3) pallet overhang or linear deck charges, and (4) any negotiated discount percentages. The final total is written to the load billing record and becomes the revenue figure used by the driver settlement and transportation accounting modules.

Why do many carriers choose to maintain their own tariff rating engine instead of relying solely on third-party rate engines?

Carrier-specific density discount structures, commodity exceptions, pallet programs, and multi-tiered minimum charges are often too complex for generic third-party engines. Maintaining an internal engine inside the TMS gives complete control over margin logic, allows real-time testing against historical EDI 210/214 data, and ensures the exact same calculation is used for both customer billing and driver pay. This prevents margin leakage that commonly occurs when external rating services are used in parallel with internal settlement systems.

Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Carriers never have to buy our software. Our only product is better decisions.

Whether you run Truckmate, McLeod, TMW, or a custom platform, our independent systems architecture expertise can help you design a tariff rating engine that protects margins, eliminates rating disputes, and scales with your operation. Call 763-244-1373 or request a systems assessment today.