Controlling via car or charger
Axle can control EV charging through either a smart charger or the vehicle itself.| Via charger | Via car | |
|---|---|---|
| Connection | Direct to charger API or OCPP | Via car manufacturer API |
| Geofencing | Not required — charger is always at home | Required — Axle only controls charging when the car is at home (boolean signal, no location data needed) |
| Best for | Charger OEMs, white-label apps | Car OEMs, white-label apps |
Choosing a product
A note on terminology: Throughout these docs, we use product to refer to the integration choice you make as a client (Flex Lite or Smart Charging), and proposition to refer to what your end users sign up for — a proposition combines the product with configuration such as reward amounts.
| Smart Charging | Flex Lite | |
|---|---|---|
| How it works | Axle creates full charge plans optimised for flexibility revenue | Axle inserts pauses into your existing charging schedules |
| Integration effort | Medium — requires intent collection and OCPP schedule handling | Low — just 3 API endpoints |
| UX changes | Charging UX built around Axle schedules | Minimal — simply capture customer consent |
| Revenue potential | Higher — full schedule optimisation | Moderate — limited pause-based flexibility |
| Best for | Platforms building charging UX around Axle | Platforms with existing scheduling which want to add flex |
Next steps
Both products share the same starting point to assess eligibility and collect consent:Eligibility & Consent
Gather the information needed to check eligibility and then get consent

