Rate management systems: modelling tariffs that keep changing

Each mode prices on a different basis

Road pricing runs on distance bands, zones or fixed lane prices, with vehicle type and drop count as modifiers. Groupage and parcel work from weight breaks against a scale, where crossing a break can lower the price and the engine must apply the better outcome. Air uses chargeable weight derived from a volumetric relationship, with rate classes by weight band and commodity. Ocean prices per container for full loads and per revenue tonne for consolidated cargo. An engine designed around one of these will misprice the others, which is why single-mode products struggle when a business adds a mode.

Surcharges are where the maintenance burden lives

The base rate is stable; the additions are not. Fuel mechanisms recalculate on published indices, currency adjustments move with exchange rates, and event-driven charges such as waiting time, failed delivery, redelivery, storage, inspection or equipment shortage attach only when something happens. Modelling these as first-class rules with their own triggers, effective periods and applicability conditions is the difference between an engine that reprices accurately and one that produces a plausible base figure requiring manual correction on every invoice.

Validity, versioning and the ability to reprice history

Rates have effective dates, and shipments straddle them. The engine must select the rate valid at the correct moment, which itself needs defining: booking date, collection date, departure or invoice date give different answers, and carriers and customers may use different conventions. Retaining superseded versions is essential, because disputes arrive weeks later and the only defensible answer reconstructs the rate as it stood. Engines that overwrite rates in place cannot explain their own history, and that limitation surfaces during the first serious audit.

Buy and sell in one structure

Intermediaries need cost and price side by side to see margin at the moment of quoting rather than at month end. That means the same shipment attributes drive two rate sets, with different validity, different currencies and different rounding, and margin rules that may be a percentage, a fixed uplift or a floor. Where the sell side is derived from the buy side, changes to purchased rates ripple into customer pricing automatically, which is powerful and dangerous in equal measure. Controls over which derived prices publish without review are worth designing early.

Coverage decay and the metric that reveals it

Loaded rates expire, lanes shift and new customers ask about geography nobody priced. The health measure is the proportion of enquiries or shipments that can be rated automatically without intervention, tracked over time. Falling coverage predicts every downstream symptom: slow quoting, inconsistent pricing between colleagues, margin surprises and invoice disputes. It is also the metric that justifies the maintenance effort, since rate management is a continuous operational activity rather than a configuration completed at go-live.

Frequently asked questions

Why do rating engines end up bypassed by spreadsheets?

Because a structure that cannot express a real tariff forces staff to work around it. The usual culprits are conditional surcharges, customer-specific exceptions and mixed-currency contracts, so those cases should be tested during selection with genuine documents.

Should rates sit in the transport system or in a separate engine?

Embedded rating is simpler and adequate for one mode with stable tariffs. A separate engine earns its place with multiple modes, buy and sell sides, or several consuming applications that must all price identically.

How should charges outside the agreed scope be handled?

Model them as defined pass-through items with evidence requirements, not as free-text lines. Which party bears them normally follows the agreed delivery terms, and recording that term on the shipment lets the engine apply the right treatment consistently.