Fuel surcharge explorer
Presenter settings

Only needed to save changes. Held in memory for this page.

A separate demo workspace is created when you first save.

Open detailed managementAPI reference

A WORKING MODEL

How does a fuel price
become a surcharge?

Two inputs feed a lookup. The result belongs to a period.
Explore what is shared, what varies, and what happens when either input changes.

EXPLORE A SERVICE AND MARKET

Loading the published examples…

Loading the four elements…

THE FOUR ELEMENTS

Follow the relationship, then inspect the detail.

Published evidence   Supplied example
01

Stored lookup table

Published bands

Loading table…

Inspect the full table and its source

See table versions and effective periods

These applicability periods demonstrate version selection. They are not verified official scale-effective dates.

02

Fuel reference input

Supplied example

Loading source…

—

API inputFile / CSVManual entry

Each route supplies dated numbers to the same calculation. Live benchmark retrieval is not connected in this demo.

Inspect the observations and source

bands
+
reference
03

Calculation / lookup

Prepare the reference. Select the applicable version. Find the matching band.

    EXAMPLE RESULT
    —

    A saved result adds a dated record →

    Inspect the API explanation
    

    04
    Published surcharge history
    What was published for each period stays available.
    Actual imported publications
    Published rates are evidence in their own right. The supplied example is not claimed to reproduce these rates.
    Inspect publication provenance
    Saved demo updates
    Preview only. Nothing has been saved.
    

    Loading source context…
    

    TWO DIFFERENT UPDATE PROCESSES
    Change the input. Or change the rules.
    

    

    

    INPUT → LOOKUP → DATED RESULT
    A new reference creates the next update.
    The lookup rules can stay the same while the fuel reference changes. A weekly service repeats this each week; local methods may update monthly.
    Preview uses the backend without saving. Storing an update preserves its observations, selected table and calculation trace.
    

    Supply dated observations from a file or another system
    Dates and values are submitted to the input API. Source and unit follow the selected service.
    See the input API request
    

    

    

    SERVICE AND LOCAL DIFFERENCES
    The same four elements. Different assignments.
    Changing a service can change the fuel benchmark, result unit and table. A local market can add a different source or reference method. Several markets can share a table.
    NL/BE sharing is an explicit demo assignment supported by matching captured bands. Production ownership is not inferred. Only the representative scenarios shown here are executable.