LIFECYCLE PLANNING · ENGLISH BUYER GUIDE
Agree the support timeline before placing a long-term charger order
By Xiaochong Energy · · 6 min read
A supplier's “end-of-life” notice can leave a procurement team with several unanswered questions: Can we still order? Will an accepted order be delivered? Can installed units be repaired? Will software support continue? Treat these as separate decisions before committing to a multi-year charging rollout, not as one ambiguous date discovered after the pilot.
This is an original procurement checklist, not a notice that any Xiaochong model is being discontinued, a guaranteed product lifespan or a standard service commitment. Exact availability, notice periods, licensing and support require written project confirmation. It does not approve continued operation, electrical work or local compliance.
1. Ask what is ending, and for whom
Record the exact model, variant and affected hardware or software revision. Ask whether the notice concerns a complete product, one supplied component, a software release or a third-party service. “The charger is supported” is insufficient if different organisations own the controller software, operator platform and payment integration.
The public IEC 62402:2019 abstract describes obsolescence management across an item's life cycle, including planning, responsibilities and resolution. That general principle motivates early procurement questions here. This article does not reproduce the paid standard or claim IEC 62402 compliance for Xiaochong.
Use the asset register to identify affected installed units. Keep a separate list of pending orders and intended expansion quantities: an installed fleet, an accepted purchase order and an uncommitted forecast may need different decisions.
2. Separate the dates in the supplier response
Request a dated response with an owner and conditions for each milestone. “Not yet agreed” is more useful than a guessed date. The following fields are proposed contract-review questions, not universal industry deadlines.
| Milestone | Question to resolve |
|---|---|
| Notice issued | Who receives the notice, which configurations are affected, and how is receipt acknowledged? |
| Last order | When must a purchase order be accepted, and are quantity, cancellation or allocation conditions attached? |
| Final delivery | What delivery arrangements apply to accepted orders, and what remains conditional? |
| Repair or parts availability | Which identified items and service routes remain available, until when, and subject to what stock or capacity limits? |
| Software and technical support | Which releases, fixes, documentation and support channels are covered? Separate each dependency and supplier. |
| Project review point | When must the buyer choose a continuation, migration or replacement plan before a required service ends? |
Do not infer a notice period from the warranty period. A warranty promise, a spare-parts quotation and a software-support statement describe different obligations. Link the relevant agreement and any exceptions rather than copying a single “supported until” date into every field.
3. Make notices reach the people who can act
Name a procurement recipient, an operations recipient and a backup contact. Agree the notice channel and how contact changes are maintained. A message to a former employee or an unread general mailbox should not be the only way the project learns that a decision is needed.
Ask the supplier to identify the affected order or configuration references, the reason for the notice at an appropriate level, the proposed options and the deadline for a buyer response. Private design details need not be made public. The buyer needs enough controlled information to assess the impact and route the question to qualified reviewers.
Record notices for external dependencies separately. A backend subscription, a payment service or connectivity arrangement may have a different owner and term. Use the software and licence cost checklist for scope questions; do not assume that buying hardware purchases unlimited access to every service.
4. Compare responses before making a last-time purchase
A final purchasing opportunity is a decision point, not a reason to order an arbitrary number of spare units. Compare the options using your actual installed population, planned expansion, support dependencies and review deadlines. Ask for a written quotation and confirm the conditions before committing funds.
- Continue with the current configuration: identify the support that remains and the unresolved dependencies. Do not describe an unsupported function as covered.
- Purchase a defined reserve: confirm approved part identity, storage requirements, warranty timing, permitted use and how the reserve will be tracked. Stock alone is not a repair or software-support capability.
- Move future orders to a successor: request a comparison against the agreed project requirements, qualification scope and commercial terms. Do not assume a similar name or cabinet proves equivalence.
- Plan replacement or migration: identify the site work, data handover, acceptance, training and service interruption to be reviewed. No cost saving or seamless migration is promised by this checklist.
Separate equipment price from the cost of the accepted transition: documentation, necessary reviews, integration, approved field work, testing and training. Record who supplies each estimate and what remains unknown. Avoid presenting a speculative total as a fixed project budget.
5. Use a fictional notice to test the decision process
Imagine a future notice says that an agreed charger variant will accept no further orders after a stated date, while repair requests and software questions follow separate terms. These are fictional circumstances, not a Xiaochong announcement. Ask your team to locate the affected site units, pending orders, notice recipients and required decisions.
Can procurement distinguish an accepted order from a forecast? Can operations identify which installed revisions are affected? Can the responsible technical team find the documents needed to assess a proposed successor? Does someone own the decision if a required third-party service ends earlier than the hardware support?
Write down each missing answer and assign a review date. This desktop exercise does not replace product testing. The configuration-change guide covers baseline and substitution approvals; this checklist focuses on the notice, deadlines and decision ownership that trigger that work.
6. Keep AC and DC SKD support timelines separate
AC EV charger SKD kits and technical documentation: agree the selected AC model, supplied component list, assembly-document revisions and the notice process for changes in availability. Confirm who maintains the approved assembly and repair instructions for the locally produced configuration.
DC EV charger SKD kits and technical documentation: agree the DC configuration, supplied power/control scope, software dependencies and responsibility for updated integration, testing and maintenance information. Ask which component or software notices affect an assembled unit and who assesses that impact.
Xiaochong recruits overseas businesses interested in local charger production or assembly, with SKD components, production/assembly technical support and repair/maintenance technical support within an agreed project scope. Available AC or DC technical documentation is free on request. Hardware, unrestricted source code, all intellectual property, certification, training, repair labour and exclusive territory rights are not automatically free. Exact models, components, document revisions, language, licensing and testing/support deliverables must be agreed for the project.
Buyer questions
Does the last-order date mean every installed charger must stop operating?
No. Last order, final delivery, repair availability and software support are different milestones. Request the applicable dates and conditions for the exact model and configuration; continued use requires the responsible operator's safety and compliance review.
Does keeping spare parts guarantee continued charger support?
No. A stored part does not guarantee approved compatibility, repair capacity, software support or access to a required service. Agree those dependencies separately and review storage and support conditions.
Is a support-notice checklist a guaranteed Xiaochong service term?
No. This is a buyer's proposed scope. Notice periods, availability, licensing, costs and support commitments must be confirmed in the actual project agreement.
Reference reviewed 4 October 2026: IEC's public abstract for IEC 62402:2019. The proposed milestone table and fictional exercise are original buyer guidance, not quotations of standard clauses or evidence of product certification.
Request an AC or DC lifecycle-support scope
Send your country, company, AC or DC track, intended model, pilot and planned expansion quantity, and local technical capability. Request free available AC or DC technical documents plus written confirmation of availability, notice contacts and support boundaries. Use the RFQ brief builder to organise the questions; it provides no electrical, contractual, security or regulatory approval.
Review the official partner programme, AC/DC SKD technical-output scope and procurement guide. Only owner-approved documents may be shared. Qualified local personnel must review electrical, installation, testing, repair and compliance decisions using model-specific documentation.
xc0225888@163.com · Sales 1: +86 137 1772 6888 · Sales 2: +86 134 2580 6997