Qargo fuel surcharge: choosing and checking your data

Qargo fuel surcharge calculations depend on the inputs your team maintains. Before updating those inputs, check that the fuel benchmark, units and effective dates match the agreement you are applying. This guide covers preparing the source data and reviewing the result.

Start with the agreed benchmark

A fuel price is only useful for a surcharge calculation when it represents the right thing. Record the exact series your agreement names, including its geography, fuel type and tax treatment. A national diesel average, a regional pump-price survey and a wholesale terminal price can produce different results.

Use a short mapping for each distinct requirement:

Keep the source observation date separate from the date you retrieved the data. Retrieving an older observation today does not make it a new price.

Prepare the update in a review sheet

Keep a working sheet with the source reference, observation period, retrieved value and proposed effective date. Add a note for any conversion or averaging rule. This is your review record, not a claim about Qargo's import schema.

If you maintain several agreements, group identical benchmark requirements so you can check the source once. Keep contract-specific treatment separate. Do not apply the same new value to every customer solely because they use diesel.

Apply the Qargo fuel surcharge update

Qargo documents a bulk grid that accepts values pasted from Excel. Its guide distinguishes this from uploading an Excel file and requires customer-specific indexes to exist before adding their values in bulk. Follow the current Qargo configuration instructions for the destination fields and permissions.

Before saving, compare the proposed changes with your review sheet. Afterwards, inspect a representative order on each side of the effective-date boundary and confirm that it uses the expected input. Start with a test environment where available.

Handle missing or unexpected data explicitly

When an expected observation is missing, flag it for review. Do not silently label the previous observation as current. A repeated value may be correct; the observation period and source publication status help distinguish an unchanged price from a failed refresh.

Check unusually large changes against the publisher. Common explanations to investigate include changed units, a different tax basis, a different geography or a source revision. Keep the previous approved input available for comparison and follow your team's correction process before altering historical values.

Where OilPriceAPI may help

OilPriceAPI provides energy-price data for software and reporting workflows. Check current availability in the UK and European fuel-data overview and European diesel coverage against your exact requirement before choosing a series.

API access can be useful when it removes repeated source collection. A single weekly series may also be practical to maintain directly from its publisher. The useful comparison is the actual preparation and checking work your team performs.

For a separate illustration of surcharge arithmetic, see the fuel surcharge calculator. Its benchmark and method must not be assumed to match your Qargo configuration.

Is there an OilPriceAPI plugin for Qargo?

There is no released OilPriceAPI connector offered by this guide. Direct synchronization would require confirmed support from Qargo and testing with the intended configuration.

OilPriceAPI is independent of Qargo. This guide does not represent a Qargo partnership or endorsement.

Need to assess a data match? Send your benchmark name, geography, units, update frequency and a redacted example of the required output to OilPriceAPI support. We can assess coverage before proposing a workflow.