How to Evaluate EV Charger Vendors for Fleet Electrification

# How to Evaluate EV Charger Vendors for Fleet Electrification

Most vendor evaluation guides treat EV chargers like office equipment: compare specs, check certifications, pick the lowest price. That works for a single workplace charger. It fails for a fleet depot where a down charger strands vehicles, misses delivery windows, and burns driver hours.

Fleet electrification changes the evaluation criteria. You are buying uptime for a duty cycle that repeats every day. A charger that works 19 days out of 20 is a retail amenity; in a bus depot it is a missed route. This guide covers the fleet-specific criteria that general procurement checklists miss.

Why fleet vendor evaluation is different

A single-site buyer worries about installation cost and whether the charger works. A fleet buyer worries about:

• Duty cycle mismatch: a charger rated for 8 sessions per day will fail at 20 sessions.
• Uptime math: 97% uptime sounds good until you calculate that 3% of 100 chargers is 3 chargers down every day.
• Scalability: the vendor who can deliver 10 chargers may not be able to deliver 100 with the same firmware revision.
• Service model: a 48-hour response time is fine for a retail charger. It is a crisis for a bus depot.

The general 7-point checklist (see our supplier evaluation guide) covers certifications, price, and warranty. This article covers what is different when the buyer is a fleet operator.

Fleet-specific evaluation criteria

1. Duty cycle match

Fleet duty cycles vary by vehicle type. Get this wrong and you buy chargers that are either underutilized or overwhelmed.

Ask the vendor: what is the rated duty cycle of this charger model? Not the electrical rating, the mechanical one. How many connect/disconnect cycles per day is the connector rated for? What is the expected contactor life at 20 sessions per day?

A charger rated for 100,000 connector cycles sounds durable until you do the math: 20 sessions per day is 7,300 cycles per year. At that rate, the connector lasts 13 years. But if the vendor's cycle rating assumes 5 sessions per day, the same charger may fail in 3 years.

2. Uptime track record, not uptime promise

Every vendor promises 97% uptime. NEVI requires it as a minimum. But fleet operations often need 99% or better. The difference between 97% and 99.2% is the difference between 11 days and 3 days of downtime per charger per year.

Ask for:

• Uptime data from existing fleet deployments, not lab tests.
• Mean time between failures (MTBF) for the power modules and the connector.
• Mean time to repair (MTTR) for common faults, and whether the vendor stocks spares regionally.
• A reference customer with a similar duty cycle who will take your call.

We publish our Sinopec deployment numbers: 100+ sites, 400+ ports, 180 kW average per port, 99.2% uptime. That uptime figure includes scheduled maintenance. Ask any vendor for their equivalent number, and ask how they calculate it. Some vendors exclude scheduled maintenance from downtime; others do not.

3. Scalability path

Fleet electrification is rarely a one-time purchase. You start with 10 vehicles, prove the model, then scale to 50 or 100. The vendor must be able to scale with you.

Modular architecture matters here. A charger built from 30 kW or 40 kW power modules lets you add capacity without replacing cabinets. FBK POWER's split-type DC cabinet uses this approach: a 480 kW system is 12 or 16 modules in a shared chassis. If you need more capacity next year, you add modules within the cabinet's rated ceiling, not a new charger.

Ask the vendor:

• Can I add power modules to this charger in the field, or does it require a factory retrofit?
• Is the firmware revision locked to the hardware revision, or can I update modules independently?
• What is the lead time for expansion modules?
• If I buy 10 chargers now and 40 more next year, will they be the same firmware and hardware revision?

For a deeper look at scalable architecture, see our guide on scalable EV charging infrastructure for fleets.

4. Software integration and backend flexibility

Fleet charging is a software problem as much as a hardware problem. The charger must integrate with your telematics, your dispatch system, and your energy management platform.

OCPP 1.6J is the baseline. It enables remote start/stop, smart charging profiles, and status reporting. Without it, you are locked into the vendor's proprietary backend, which may or may not integrate with your fleet management system.

Ask the vendor:

• Is OCPP 1.6J supported natively, or is it a gateway translation?
• Which third-party backends have you integrated with? (Monta, Driivz, SteVe are common; there are others.)
• Can I switch backends without replacing the charger firmware?
• What is the API rate limit for real-time status polling?

We ship OCPP 1.6J as standard on all DC chargers. We do not bundle a mandatory software subscription. That is a deliberate choice: fleet operators should own their data and choose their backend.

5. Service model and spare parts logistics

A fleet charger is a production asset. When it fails, you need a service model that matches your operational tempo.

Ask the vendor:

• What is the guaranteed response time for a critical fault?
• Do you stock spare power modules regionally, or do they ship from overseas?
• What is the warranty on power modules vs. the enclosure vs. the connector?
• Can my technicians replace a power module, or does it require a factory-certified technician?

For context, a third-party factory audit for orders above $500K typically costs $8,000-15,000. That audit should include a check of the vendor's spare parts warehouse, not just the production line.

Scoring framework for fleet buyers

Use this weighted scoring framework to compare vendors. Adjust weights for your operation.

A vendor that scores 5 on price but 2 on uptime is a bad fleet choice. The weights reflect that.

Red flags fleet buyers miss

1. The vendor's reference site is a single charger

A vendor with 50 installations of 1-2 chargers each has retail experience, not fleet experience. Ask for a reference with 20+ chargers at a single site.

2. Firmware updates require downtime

If a firmware update takes the charger offline for 30 minutes, that is 30 minutes of stranded vehicles. Ask if updates are hot-swappable or require a maintenance window.

3. The warranty excludes wear items

Connectors, cables, and contactors are wear items. A 5-year warranty that excludes them is a 5-year warranty on the enclosure only. Read the warranty schedule, not the marketing summary.

4. The vendor cannot name their module supplier

If the vendor assembles chargers from purchased modules but cannot name the module manufacturer, you have a supply chain risk. Ask: who makes the power modules, and can I buy spares directly if you go out of business?

5. The pilot program is a demo, not a trial

A real pilot puts chargers into your operational rotation for 3-6 months. A demo puts a charger in the parking lot for a week. If the vendor will not agree to a real pilot, they do not trust their hardware.

Pilot program structure

Before you commit to 50 chargers, run a structured pilot. Here is the structure that works.

Duration

3-6 months minimum. You need at least one full utility billing cycle to see demand charge behavior, and one seasonal temperature swing to see thermal performance.

Scope

• 2-4 chargers, matching your planned production configuration.
• 5-10 vehicles, rotating through the chargers on their normal duty cycle.
• Integration with your existing telematics and dispatch, even if manual.

Metrics to track

• Uptime: charger available / total hours.
• Session success rate: completed sessions / attempted sessions.
• Energy delivered vs. vehicle SOC gain (efficiency check).
• Demand charge impact: peak kW with and without load balancing.
• Driver feedback: ease of use, connector ergonomics, fault reporting.

Decision gate

At the end of the pilot, you should be able to answer:

• Does the charger handle our duty cycle without overheating or derating?
• Does the OCPP integration work reliably with our backend?
• Is the vendor's service response time acceptable?
• What is the actual cost per kWh delivered, including demand charges?

If the vendor cannot support a pilot with these metrics, they are not ready for fleet scale.

Bottom line

Fleet vendor evaluation is a different discipline from single-site procurement. The criteria that matter are duty cycle match, uptime track record, scalability path, software integration, and service model. Price matters, but it is 10% of the decision, not 50%.

Use the scoring framework to compare vendors objectively. Run a real pilot before you scale. And if you want a reference point for what fleet-scale reliability looks like, review our Sinopec case study: 100+ sites, 400+ ports, 99.2% uptime.