Portal (mandatory)
In the portal, you will be prompted to upload two CSV files during offer creation. There are templates available for download during offer creation. Find them again in the bottom of the article. We recommend editing the files in a text editor such as TextEdit (Mac) or Editor (Windows), as Excel sometimes corrupts the CSV file. Please save the CSV file as CSV Comma Separated, not as UTF-8 Comma Separated.
eRoamingPricingProducts
This file specifies the pricing products for this pricing model. The first line of this file contains the operator name and the default tariff.
The following values are available for the first line:
| Operator Name | DefaultReferenceUnit | DefaultPrice | DefaultPriceCurrency |
| Name of the operator pushing the data | Default reference unit in time or kWh (possible values are HOUR, KILOWATT_HOUR, MINUTE) | A default price for pricing sessions at undefined EVSEs - the default price must be the same across all flexible/dynamic offers if there are multiple flexible/dynamic offers | Currency for default prices (based on ISO 4217 - for example, EUR, CHF) |
For example:
Mark's Home charging point,KILOWATT_HOUR,5,EUR
Mark's Home charging point is the operator name, and this operator has set a default tariff of 5€ per kWh.
The following lines specify the different tariffs.
The following fields are available for all following lines of the CSV file:
| ProductID |
ReferenceUnit |
PricePerReferenceUnit | ProductPriceCurrency | MaximumProductChargingPower | IsValid24hours | ProductAvailabilityTimes | begin |
end |
AdditionalReference (optional) | AdditionalReferenceUnit (optional) | PricePerAdditionalReferenceUnit (optional) |
| Name of the pricing product | Reference unit in time or kWh (possible values are HOUR, KILOWATT_HOUR, MINUTE) | A price value per the given reference unit | Currency of the defined pricing product (based on ISO 4217 - for example EUR, CHF) | Maximum product charging power (in kW) | "true" if this product is applicable 24 hours a day, otherwise "false" | Day values to be used in specifying periods on which the product is available (possible values are Everyday, Workdays, Weekend, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday) | Opening time (HH:MM) |
Closing time (HH:MM) |
Additional pricing components to be considered in addition to the base pricing (possible values are START FEE, FIXED FEE, PARKING FEE, MINIMUM FEE; MAXIMUM FEE) |
Reference unit in time or kWh (possible values are HOUR, KILOWATT_HOUR, MINUTE) | A price in the given currency |
For example:
Peak,KILOWATT_HOUR,5,EUR,30,false,Workdays,09:00,18:00,PARKING FEE,KILOWATT_HOUR,4
The peak tariff is defined with a base fee of 5€ per kWh for a maximum charging power of 30 kW - this product is not applicable for 24 hours per day, but only applies during the peak hours between 9:00 and 18:00. Additionally, a parking fee of 4€ per kWh applies.
The field AdditionalReference provides the following additional price references which can be used to define a variable component in addition to the base price:
a. Start Fee: can be used in case a fixed price is charged for the initiation of the charging session. This fee will be added to the base price defined in PricePerReferenceUnit.
b. Fixed Fee: can be used if a single fixed price is to be billed irrespective of charging duration or energy consumption (e.g. when all sessions are to be charged a single fixed fee). When used, the base price for the respective ProductID should be set to zero and the price provided as a fixed fee will be the single value billed for all sessions.
c. Parking Fee: can be used in case sessions are to be billed for both parking and charging. When used, the default definition shall be that the Parking Fee applies from SessionStart to SessionEnd.
Note: in Next Generation Pricing we provide the possibility for CPOs to determine when parking starts and when it ends based on different combinations of the SessionStart, ChargingStart, SessionEnd, and ChargingEnd attributes. This means a CPO can choose to define their parking fee from ChargingEnd to SessionEnd rather than the above SessionStart to SessionEnd definition.
d. Minimum Fee: can be used in case there is a minimum fee to be paid for all charging sessions. When used, this implies that the final amount to be paid cannot be less than (but can be greater than) the minimum fee.
e. Maximum Fee: can be used in case there is a maximum fee to be paid for all charging sessions. When used, this implies that the final amount to be paid cannot be more than (but can however be less than) the maximum fee.
eRoamingEVSEpricing
This file specifies which EVSEs in the operator's network are associated with which pricingProduct (specified in the previous file).
For example:
DE*AB7*E840*6587,Peak
DE*AB7*E840*6587,Off peak
DE*AB7*E840*6625,Peak
DE*AB7*E840*2833,Peak
eRoamingDynamicPricing API (optional)
Optionally, you may also implement the eRoamingDynamicPricing API. This API allows EMPs to pull pricingProducts and EVSEpricing from any bilateral offer they subscribe to. CPOs may use it to update their offers and EVSEpricing associations for bilateral offers.
Review the OpenAPI specification on Github for a detailed technical description of the API: