Cost Parameters

Configure internal cost parameters in Sixième Étoile — fuel price, consumption fallback chain, toll costs, driver costs, and staffing costs used in margin analysis and RSE compliance.

Overview

Cost parameters define the internal operational costs used by the platform for margin analysis and RSE (Responsabilité Sociale des Entreprises) compliance checks. Unlike pricing parameters that affect client-facing amounts, cost parameters are internal inputs that never appear on quotes or invoices.

These parameters feed the "shadow calculation" visible in the dispatch RSE compliance indicators and the profitability reports.

Fuel Parameters

Parameter	Purpose	Allowed values	Effect
`defaultFuelPricePerLiter`	Default fuel cost used when no live price is available	Decimal > 0 (e.g. `1.75` = €1.75/L)	Used in cost-of-operation calculations for all vehicles unless overridden
`collectApiKey`	API key for the CollectAPI fuel price service	String (API key) or empty	If set, the platform automatically fetches the current diesel price daily and uses it instead of `defaultFuelPricePerLiter`

Fuel Consumption Fallback Chain

The platform resolves the fuel consumption rate for a specific vehicle in this order (first match wins):

Vehicle.fuelConsumption — consumption rate set on the individual vehicle record
VehicleCategory.fuelConsumption — consumption rate set on the vehicle's category
OrganizationPricingSettings.defaultFuelConsumption — organization-wide default
Hardcoded platform default (12 L/100 km) — only if no org-level default is configured

Parameter	Location	Purpose
`fuelConsumption` (per vehicle)	`Vehicle` record	Individual vehicle consumption override
`fuelConsumption` (per category)	`VehicleCategory` record	Category-level consumption rate
`defaultFuelConsumption`	`OrganizationPricingSettings`	Organization-wide fallback

Toll Parameters

Parameter	Purpose	Allowed values	Effect
`tollCostPerKm`	Estimated toll cost per kilometer	Decimal ≥ 0 (e.g. `0.08` = €0.08/km)	Used when exact toll calculation via Google Routes API is unavailable; provides an approximation for cost analysis
`tollSource`	Source used for toll data	`ESTIMATED` or `GOOGLE_ROUTES`	`ESTIMATED`: uses `tollCostPerKm`. `GOOGLE_ROUTES`: uses real toll data from the Google Routes API integration (requires API key configured in integrations settings)

Driver and Vehicle Running Costs

These costs are part of the "shadow" cost-of-operation calculation and inform the operator's margin analysis dashboard.

Parameter	Purpose	Allowed values	Effect
`vehicleWearCostPerKm`	Vehicle wear and maintenance cost per km	Decimal ≥ 0 (e.g. `0.15` = €0.15/km)	Added to fuel cost per km to form the total vehicle running cost
`parkingCostPerMission`	Average parking cost per mission	Decimal ≥ 0 (e.g. `5.00` = €5 per mission)	Added to the cost side when computing the mission cost of operation
`driverDailyAllowance`	Daily meal and expense allowance per driver	Decimal ≥ 0 (e.g. `17.00` = standard French VTC allowance)	Included in driver day cost for multi-day missions

Staffing Costs

Staffing costs apply when a mission requires double crew, relay drivers, or multi-day operation. They are configured on OrganizationPricingSettings:

Parameter	Purpose	Allowed values	Effect
`hotelCostPerNight`	Hotel cost per night per driver	Decimal ≥ 0 (e.g. `85.00` = €85/night, default)	Used in cost analysis for overnight and multi-day missions requiring accommodation
`mealCostPerDay`	Meal allowance per driver per day	Decimal ≥ 0 (e.g. `17.00` = standard per diem)	Added to daily driver cost for each day of a multi-day mission
`secondDriverCostPerDay`	Daily cost of a relay/second driver	Decimal ≥ 0 (e.g. `200.00` = gross daily rate)	Used when `crewType = DOUBLE_CREW` or `RELAY_DRIVER` to compute the extra staffing cost

Configuring Cost Parameters

Go to Settings → Tarification → Paramètres de coût (screen N-09).
Update the relevant fields.
Save. Changes take effect on all subsequent cost analysis calculations; existing quotes and missions retain their previously computed cost data.

Setting Up Live Fuel Prices

To enable automatic fuel price updates via CollectAPI:

Obtain an API key from CollectAPI.
Enter the key in the collectApiKey field.
Save. The platform will fetch the current diesel price at midnight each day.
If the API call fails, defaultFuelPricePerLiter is used as fallback.

How Cost Data Appears in the UI

Cost parameters are surfaced in two places:

Trip analysis panel (quote cockpit) — shows the estimated cost breakdown alongside the client price, enabling the operator to see the margin on each quote line.
RSE compliance indicators (dispatch) — uses cost data alongside the minimum wage threshold to flag missions where driver revenue may fall below the legal minimum.

Cost data is never included in PDF invoices, client-visible quotes, or the agency portal.

Practical Tips

Set defaultFuelConsumption immediately. If you do not configure this, the platform uses 12 L/100 km as a generic fallback. This is often inaccurate for luxury vehicles or minibuses. Set a realistic default that matches your fleet's typical consumption.
Use Vehicle.fuelConsumption for outliers. If one vehicle in your fleet has a significantly different consumption (e.g., a hybrid or an older diesel), set its consumption directly on the vehicle record.
Review hotelCostPerNight and mealCostPerDay annually. These values affect the RSE compliance check for multi-day missions. Update them when hotel or per-diem rates change.
Enable CollectAPI only if fuel cost accuracy is important for your margins. For most operators, a manually updated defaultFuelPricePerLiter (reviewed monthly) is sufficient. The CollectAPI integration adds complexity and requires ongoing API key management.

Cost Parameters

On this page