EV charger warranty vs service SLA: who gets the site charging again?

1. Ask for two documents, not one reassuring number

Request the equipment warranty and the proposed service-level agreement (SLA) or support scope separately. Identify the contracting entity, equipment serial numbers, coverage start, duration, location, exclusions and claim process. If no restoration commitment is offered, keep that gap visible instead of interpreting warranty duration as a repair deadline.

An industry example makes the distinction clear: ChargePoint's published service explanation distinguishes its parts-only standard warranty from an additional package covering labour, parts coordination and proactive support. Its stated response and resolution targets are also separate. Those are that provider's published offerings, not Xiaochong terms, a universal market requirement or confirmation of availability in your country.

For every supplier, turn broad phrases such as “full support” into a responsibility list. Ask what is included, what is optional and what remains the owner's responsibility. Have the relevant commercial and legal professionals review the actual agreement before commitment.

2. Define the service clock from incident to restoration

A reply to an email does not mean a technician has arrived. A technician arriving does not prove the charger is usable. Ask the parties to define each milestone, the evidence that records it and who owns the next step.

Ask explicitly about paused clocks, weekends, local holidays, site-access delays and responsibilities outside the supplier's control. This is not a recommendation for a particular response period. The right scope depends on your operating window, local service capability and the written offer.

3. Compare the uncovered cost, not just the replacement part

Build a small scope matrix for parts, labour, technician travel, freight, return shipping, customs handling, local taxes, diagnostic visits, retesting and approved software support. Do not assume that a “free replacement” includes these other items. Ask how an uncertain diagnosis or a returned unit with no reproduced fault will be handled.

For each cost line, request an included/excluded/optional answer, a responsible party and the applicable quotation. Keep planned maintenance distinct from corrective repair. Also separate accidental damage, installation issues and supplier defects rather than assuming the same coverage applies to every interruption.

ChargePoint's service page presents monitoring, response time, parts and on-site labour as identifiable service features. Use that separation as a procurement question, not as evidence that another supplier includes them. Xiaochong's warranty, travel, training and labour terms must be agreed for the specific project.

For cross-border orders, ask who holds revision-matched spares and who is authorized to fit them. Our spare-parts readiness guide covers that inventory decision; this checklist focuses on the service obligation and the record needed to verify completion.

4. Make an uptime percentage explain its denominator

Before comparing any uptime promise, ask what is being measured: a cabinet, an individual connector, payment availability, the communications link or a successful customer charging session. Ask for the reporting period, eligible operating hours, exclusions and treatment of missing telemetry. A green dashboard alone does not answer all of these questions.

Consider an invented example with two connectors, each scheduled for 100 hours, with no excluded hours. If one connector is unusable for 20 hours while the other remains usable, simple connector-hour availability would be (200 minus 20) divided by 200, or 90%. A different metric asking only whether at least one connector is usable at the site could show 100%. Both calculations use the same hypothetical event, but answer different questions. Neither is a Xiaochong performance result or a prescribed contractual formula.

Keep full-service outages, partial capacity, payment failures and external power interruptions distinguishable in the report. The agreement should explain how each is classified. Do not silently remove inconvenient events or treat missing data as evidence of successful charging.

5. Walk one realistic incident through the proposed support chain

Before the order, hold a desk-based review: a customer cannot start a session on one connector during the required operating window. Who receives the report? Which safe observations can the site contact provide? Who separates vehicle, charger, backend and payment responsibilities? Who tells the operator what is still uncertain?

Use the exercise to expose ownership gaps, not to provoke a live failure. Do not disconnect safety devices, force connectors, open energized cabinets or grant unnecessary remote access. Agree a secure route for relevant diagnostics and avoid uploading personal customer information, credentials or unreviewed internal files to public forums.

Write an escalation contact for each dependency and name one incident coordinator. Even where separate contractors retain their own scopes, the operator needs a clear way to learn what happens next. A case number, current owner and next-update commitment are more useful than several disconnected email threads.

6. Require restoration evidence and a clean handover

Define the authorized return-to-service evidence with the technical team. Record the affected equipment, approved work performed, relevant replaced-part revisions, software or configuration changes and any limitations that remain. If only part of the service has returned, record partial restoration instead of closing the whole incident.

Keep the original detection time, acknowledgements, dispatch history and acceptance record together. Review repeat incidents periodically to see whether a recurring symptom needs a different investigation. This is evidence management, not a claim that an error code uniquely identifies the failed component.

At handover, retain an owner-accessible service record, approved operating documents and the escalation route for warranty expiry or provider changes. Use the RFQ planning tool to organize the procurement brief; attach the service-scope questions separately. The tool does not issue a contract, verify a provider's SLA or approve repair work.

Related operating checks

• Incident evidence before a reset
• Backend exit and handover readiness
• Factory and site acceptance evidence

Primary manufacturer service pages reviewed 17 September 2026. The comparison framework and numerical example are original procurement guidance. Referenced brands do not endorse Xiaochong, and their service terms do not apply to Xiaochong orders.