Ask Flux
Help Center
How can we help?

eMSP Customer - Deprecate default retail package property

The Default retail package property has been removed from the customer creation process in eMSP to simplify the system and prevent confusion regarding retail package associations with drivers.

What is it that we have changed?

eMSP operators can organize their fleets under their eMSP by creating customers, drivers and tokens.

When creating customers, one of the properties they could previously configure was Default retail package.

ℹ️

The property Default retail package has been removed and is no longer available in the Add/Edit customer flows through EV Portal. Note: Through Platform API, this was not a supported property.

Notion image

The Helpkit related page - Link iconAdd a Customer – EV Portal | Help Center - has been updated.

Why have we changed it?

GreenFlux continuously aims at simplifying the system and remove sources of ambiguity. Previously, when a Default retail package was set at customer level, it was used as the pre-selected retail package when creating a driver under that customer. However, this led to confusion. In several cases, when the default retail package was changed at customer level later on, customers would expect the retail packages of existing drivers to be updated as well - but this was not the case. To avoid these misunderstandings and reduce complexity, we decided to remove this property. Please note this property still keeps being mandatory at driver level.

Did this answer your question?
😞
😐
🤩