Digital framework agreements — rate card and indices

7 min read

A digital framework agreement is a multi-year transport contract between forwarder and consignee (or between consignee and direct carrier) managed entirely on a platform — no longer in Word or Excel exchanged via email — with structured rate card, automatic fuel indices, coded tariff zones, immutable versioning and every change tracked in audit log. For a forwarder working with large consignees, the framework agreement is the backbone of the business: it typically covers 60-80% of volume on pre-negotiated rates, leaving spot only for peaks and anomalies. Yet in most European mid-market operators the framework agreement still lives as signed PDF + Excel rate sheet manually updated, with all the resulting problems.

Why Excel is no longer enough

Five problems known to procurement at large consignees and traffic managers at forwarders.

Fragile versioning. "What was the agreed rate on March 12?" → search the email attachment from March 11. If the attachment is missing, the data is lost. No immutability.

Manual fuel indices. The agreement provides for tariff revision on diesel price variation (formula like "every +5% diesel on the index, +3% on the tariff"). Manual calculation = delays, errors, disputes.

Inconsistent tariff zones. "Is Bologna zone 3 or zone 4?" → 3 different forwarders answer with 3 different zone maps. Costly reconciliation.

Costly fiscal audit. Tax authority or auditor verification requires reconstructing the rate applied to a specific shipment 2 years ago. Time: man-hours.

Spot shipments out of control. Without the digital framework, the traffic operator easily falls back on spot rates when the agreement would cover the shipment. Result: eroded margin.

What a well-designed digital framework agreement contains

Six structural elements that separate a real framework agreement from a "digitized" PDF.

1. Structured rate card — not a PDF but a parametric set of rows by origin zone, destination zone, vehicle type, goods type, weight/volume bands, optional accessory services (tail-lift, multi-stop, ADR).

2. Fuel indices in formula — tariff revision is an automatic function of an external index variation (e.g. national MIT diesel index, Brent USD index). The platform reads the index from an official source and applies the agreed formula.

3. Coded tariff zones — zones are first-class platform entities, shared between forwarder and consignee. No longer "attached postal-code list" but structured coding living in a single registry.

4. Immutable versioning — every change to the agreement creates a new version with timestamp, author, motivation. Previous versions remain consultable (read-only). No PDF "overwriting".

5. Approval workflow — change to the rate card is not applicable until both parties have digitally signed the new version. Audit trail is complete.

6. Automatic shipment-to-agreement mapping — when a new shipment arrives, the platform automatically maps it to the applicable agreement row (by origin, destination, vehicle, period). Only out-of-scope shipments go to spot rates.

Migrating from Excel — what's needed operationally

Process inversion (from PDF+Excel to platform) is less traumatic than it seems if managed in phases.

Phase 1: import existing rate card. Current Excel imported into platform with assisted parser. The platform normalizes zones, vehicle codes, weight bands. The forwarder validates the result. Time: 1-2 work days.

Phase 2: external index linking. The fuel index and other indices agreed with the consignee are linked to public sources. Automatic revision formulas are tested on a 12-month historical to validate the result.

Phase 3: digital signature workflow. New version of agreement digitally signed by forwarder and consignee. Previous versions remain accessible read-only for audit.

Phase 4: automatic shipment mapping. Incoming shipments mapped by the platform to applicable agreement row. Exceptions (out-of-scope spot shipments) flagged in dashboard.

Margin effect

Three concrete items where digital framework agreements improve business margin.

Reduction of accidental spot shipments. The traffic operator no longer needs to "find" the right rate in Excel: the platform maps the shipment to the applicable agreement. Accidental spot shipments (paying +10-15% over rate card) are reduced.

Timely tariff adjustment. If the fuel index rises, the new tariff applies from the next week — not a month later when someone remembers. Margin doesn't silently erode.

Fast fiscal audit. Tax verifications on shipments from 2-3 years ago become a dashboard query, not a weeks-long activity. Admin office cost lowered.

FAQ

Can I digitize an existing framework agreement without renegotiating?

Yes. Digitization typically happens by importing the existing rate card Excel as a "snapshot" of the current version. Actual renegotiation can happen later. The platform improves operational management without requiring contract renegotiation.

What happens to previous versions of the agreement?

They remain consultable read-only. Each new version is digitally signed, timestamped, and linked to the previous one. For a fiscal audit you can reconstruct exactly which tariff was in effect at any past date.

Can the fuel index follow different sources?

Yes. The tariff revision formula is configurable: it can follow the national MIT diesel index, Brent USD index, ICE Gasoil index, or a mix. The platform reads values from official sources and applies the formula. Forwarder and consignee agree the source and formula at setup.

Are tariff zones shared with the consignee?

Yes if the agreement is bilateral (forwarder ↔ consignee): zones become a shared registry, avoiding inconsistencies. If the agreement is internal to the forwarder (with the carrier), zones are internal. The platform supports both configurations.

How are accessory services (tail-lift, multi-stop, ADR) handled?

As additional parametric rows in the rate card. Example: "+ €30 for tail-lift use", "+ €15 per multi-drop stop after the first". These rows are applied automatically when the shipment contains the corresponding flag, without manual operator intervention.


Want to see migration of a concrete Excel framework agreement onto a platform? Request a private demo on the forwarders page or read the article on exclusive carrier networks.

Share

Subscribe to the newsletter

The next posts straight to your email. One-click unsubscribe.

Related posts