Advanced cost calculation gives you greater flexibility when configuring operational costs and revenue logic. This feature enables users to fully customize how cost and revenue values are generated, supporting more advanced pricing models and internal cost formulas.

By offering complete control over calculation methods, Advanced cost calculation helps businesses model profitability more accurately, whether you track cost per distance, per stop, per weight, or incorporate custom revenue structures.

The default eLogii cost calculation feature supports the most common cost calculation use cases and is ideal for businesses with a straightforward cost and revenue approach. The Advanced Cost Calculation feature is more suitable for businesses with more complex cost and revenue calculation rules
​

At the moment, this feature is not available by default and can be made available on request. If enabled, it can be accessed through Configuration ⇒ Cost calculation, and the interface should look like this:

There are 3 sections within the advanced cost calculation feature:

In this section, you can define the foundation of your cost model by selecting which financial layers to include. You can enable cost calculations, revenue tracking, profit analysis, or any combination of the three, depending on your operational needs.

Additionally, you can choose whether to display cost, revenue, or profit in the system (Task card, cost calculation analytics).

Here, you can configure cost preferences at the asset level by defining calculations for Vehicles, Drivers, or both. You can choose from predefined models that compute costs based on operating time (hours), distance (kilometers), or flat daily costs. Each model can be applied independently or combined, allowing you to activate two or all three cost dimensions simultaneously to reflect your real-world commercial logic.

If your cost model is not based on hourly, daily, or distance-traveled rates, you can leave the default unit fields blank and introduce a custom cost input instead. You can adjust parameters to reflect your unique operational logic without applying time- or mileage-based cost.

All the cost parameters are completely editable, even the predefined models. Each of the fields has a specific function:

Key - Name used for API calls when referring to the field.

Name - Displayed name of the cost calculation. This is what users see.

Unit - Indicates the currency used for the cost calculation.

Included in total - Whether this cost calculation should be included in the total calculation analysis.

Type - Whether it should be calculated for each unit or in total.

Round to unit - Rounding options include to nearest, round up, and round down. Users can also choose not to apply any rounding.

Based on - An additional parameter, the calculation will be based on. It is a completely optional field, and the available options are Distance, Duration, Capacity unit, Number of stops, Number of Tasks, and Number of Items. If none of these are suitable, eLogii allows its users to use a JSON Expression to specify which parameter to take into account for cost calculation.

Value expression - This field is available only in case the Expression option is chosen within the Based on field. If anything else is chosen, this field is uneditable.

Calculated Expression - This is used to define the core formula that stores the base cost value (such as a driver’s rate per kilometer), and instructs the system how that cost should be calculated when generating routes. This field acts as the main source of truth for how cost computation is performed.

Tiers - This field allows you to introduce conditional cost brackets when your business model applies different rates at scale. For example, you can set progressive values based on factors such as distance, duration, or number of stops. One tier can be used, or multiple tiers can be combined to mirror real-world pricing complexity.

Together, these options give you full control over cost calculations while ensuring accurate financial modeling within the route planning engine of eLogii.

Much like the Cost section, the Revenue section mimics the configuration options, but it applies them to revenue calculation. Both revenue and cost calculations can be used in tandem.

If the cost and revenue calculation is set up directly in Configuration, the premade cost/revenue calculation template can be selected to apply to any Vehicle or Driver.

If certain Drivers or Vehicles require their own pricing logic, you can configure a fully custom cost calculation rule tailored to their case. This rule is applied exclusively to the selected Driver or Vehicle, ensuring their unique operational costs are accurately captured.