Most charging software is designed around a stranger pulling up, tapping a card or scanning a QR code, and paying for a single session. Fleet charging looks nothing like that: the same known set of vehicles and drivers, charging on a schedule tied to shift patterns, billed back to internal cost centers rather than a credit card. A platform built for public charging can technically run a depot - it usually just isn't built for how a fleet actually operates.
How fleet charging differs from public charging
- Known drivers and vehicles, not walk-up traffic. Access control is about assigning a defined set of vehicles or badges to defined chargers, not accepting anyone who shows up.
- Cost allocation, not point-of-sale payment. Sessions need to roll up to a department, vehicle, or route - not a driver's personal card.
- Charging happens on a schedule, not on demand. Vehicles typically need to be ready by a shift start time, which makes visibility into which vehicle is charging, and how close it is to ready, more important than driver-facing convenience features.
- Downtime is an operational problem, not just a revenue one. A public charger that's down loses a session. A depot charger that's down can mean a vehicle isn't ready for its route the next morning.
- Multiple depots, one operation. A fleet running several depots needs one consolidated view of vehicles, chargers and costs across all of them - not a separate login per site.
What to actually require from a platform
- Reservations and scheduled charging. The ability to assign a vehicle to a specific connector for a planned charging window, rather than treating every session as a first-come, first-served walk-up.
- Badge or RFID-based access control. Assigning drivers or vehicles to specific chargers without requiring a consumer-facing mobile app for every driver in the fleet.
- Corporate accounts and centralized billing. Sessions charged to a company account, with invoicing and cost allocation by vehicle, department or route - not a personal payment method per driver.
- Role-based access for fleet and depot staff. A fleet manager needs a different view and set of permissions than a depot technician or a finance user pulling cost reports - not one shared login for everyone touching the platform.
- Site and zone hierarchy across depots. One consolidated view across every depot location, organized by region, site and connector, instead of a separate deployment or dashboard per depot.
- Real-time monitoring and alerting. Because a down charger threatens next-shift vehicle readiness, not just a missed transaction, alerting needs to reach operations immediately - see the real cost of charging downtime for why this matters more for a fleet than it looks on paper.
- Exportable reporting and an audit trail. Cost allocation, utilization by vehicle or depot, and a full record of administrative actions - the data a fleet finance team actually needs to close the books.
- API and webhook access. A way to connect charging data into whatever fleet management or telematics system already tracks vehicles and routes, instead of forcing dispatch to check a second, disconnected system.
What not to expect from a public-charging platform
A platform built primarily for public, walk-up charging tends to assume one payment method per session and one brand-new account per driver - neither of which fits a fleet with a fixed roster of vehicles billed to the company. Retrofitting cost-center billing, badge-based access and multi-depot reporting onto software that wasn't designed for it is usually possible, but it's a workaround, not a feature - worth asking about directly during evaluation rather than assuming it's covered because “billing” appears on a feature list.
Where this fits a broader platform
None of the requirements above are fleet-exclusive - they're the same operations, commerce and access capabilities any multi-site charging business needs, applied to a depot instead of a public site. Fleet operations is one of the use cases CarChargeOS is built for alongside public and workplace charging; see the full capability set on the platform page and enterprise page.
Frequently asked questions
Can a public charging platform be used for a fleet depot?
Technically, often yes - but cost allocation, badge-based access and multi-depot reporting are usually bolted on rather than designed in, so it's worth confirming those specific capabilities exist rather than assuming a general-purpose CSMS covers them.
Do fleet drivers need the same mobile app as public drivers?
Not necessarily. Badge or RFID access is often a better fit for fleet drivers than requiring every driver to create and use a consumer-facing app account, especially where the vehicle - not the individual driver - is what needs to be tracked and billed.
What matters most for a single-depot fleet vs. a multi-depot fleet?
A single depot can often get by with straightforward scheduling and access control. Multiple depots add a real requirement for consolidated, cross-site reporting and role-based access - without it, a fleet ends up managing each depot as a separate system rather than one operation.