Skip to main content
All CollectionsBackoffice support centerChargers
How to Track Charging Session Stop Reasons
How to Track Charging Session Stop Reasons

Learn how to monitor and analyze charging session terminations using the Stop Reason feature in the Back Office.

Lizzie Karmi avatar
Written by Lizzie Karmi
Updated over a week ago

Understanding Stop Reason Tracking

The Stop Reason feature provides detailed insights into why charging sessions end, helping optimize charging operations and troubleshoot potential issues. The system captures standardized stop reasons, ensuring consistent data across your charging network.

Accessing Stop Reason Data

To view stop reason information in the Back Office:

  • Navigate to the "Transactions" tab

  • Click the column menu

  • Enable the "Stop Reason" column, which is hidden by default

Stop Reason Categories

The system tracks the following standardized stop reasons, as defined in the OCPP 1.6 protocol:

  • DeAuthorized: Transaction stopped due to authorization status in StartTransaction.conf

  • EmergencyStop: Emergency stop button activation

  • EVDisconnected: Cable disconnection or vehicle movement from inductive charge unit

  • HardReset: Hard reset command execution

  • Local: Regular termination by the user at the charge point (RFID tap, button press)

  • Other: Miscellaneous reasons

  • PowerLoss: Complete power loss

  • Reboot: Local reset/reboot occurrence

  • Remote: Regular remote termination (smartphone app, exceeding prepaid credit)

  • SoftReset: Soft reset command execution

  • UnlockCommand: Central System unlock connector command

Benefits of Stop Reason Tracking

Stop Reason tracking enhances charging operations through:

  • Detailed monitoring of session termination causes

  • Pattern identification in charging behavior

  • Service quality improvement through termination analysis

  • Enhanced reporting capabilities with completion insights

This feature strengthens the platform's analytical capabilities by providing clear visibility into charging session endings across your network.

Did this answer your question?