Commercial EV Charger RFQ Checklist: 12 Inputs That Prevent Requotes

Start with the operating context.

Give each bidder the same project brief: destination country and site type; vehicle classes and daily energy need; arrival pattern, dwell time and charging window; confirmed available electrical capacity and supply conditions; initial and future charger quantities; bay geometry and cable route; connector and gun count; access, authorization and payment journey; network, OCPP and backend responsibilities; local certification, permitting and accessibility requirements; delivery, installation and commissioning boundaries; and a written acceptance and service plan. Unknown items should be labelled as open decisions rather than guessed.

Good commercial charging decisions connect vehicle use, site conditions and the operator's intended service. The selected equipment can then be reviewed against the final technical, commercial and destination-market requirements.

Planning checklist.

• Business objective, vehicle duty cycle, charging window and measurable throughput target
• Site supply, existing loads, usable capacity, input-voltage conditions and expansion plan
• Parking geometry, equipment position, cable reach, connector mix, gun count and environmental constraints
• User access, unattended payment flow, network, OCPP, DLB, data ownership and cybersecurity responsibilities
• Destination-market certification, permitting, accessibility, metering and local inspection requirements
• Quantity, delivery, installation, commissioning, training, spares, warranty, support and acceptance-test ownership

Use four comparison gates before choosing a quote.

1. Frozen input brief: issue the same dated site, vehicle, power, layout and interface assumptions to every bidder, with unknowns visibly marked.
2. Evidence matrix: ask which exact hardware, firmware, connector, OCPP version, CSMS and payment path each capability statement covers.
3. Exclusions schedule: compare who owns civil and electrical work, connectivity, payment fees, commissioning, approvals, freight, spares and support—not only the cabinet price.
4. Acceptance plan: identify the responsible party and evidence for factory review, site commissioning, backend/payment checks, delivered-energy verification and handover.

These gates are an original buyer-comparison method. They do not certify a product, approve a site design or replace model-specific contracts and acceptance procedures.

How this applies to a commercial charging project.

Xiaochong's local-browser RFQ builder can structure these inputs without automatically transmitting them. The portfolio includes 20–400kW DC configurations, new ultra-slim 60–240kW dual-gun models, 80/120/160/240kW four-gun options, AC destination charging, EVSE analyzers, a project-configured self-service host and OEM/ODM or SKD discussions. Suitable projects can review 260–485V AC input and custom wider input; charging cables are generally 5 metres standard with project-specific longer or shorter options. Every final model, interface and market requirement remains subject to written confirmation.

Images and portfolio references are a useful starting point, but final technical data, dimensions, protection rating, certification, payment integration and delivery terms should be confirmed for the selected model and destination market.

Ask what the warranty and service offer actually covers

A warranty period alone leaves important purchasing questions open. For a charger at a remote depot, the buyer still needs to know who handles the service request, which costs are included and what happens while a repair is pending. Ask each bidder to answer the same scope questions against the exact equipment and destination.

The U.S. Department of Energy's AFDC operation and maintenance guidance explains that warranty plans vary and recommends assigning maintenance-cost responsibility. It also distinguishes response time, repair time and uptime requirements in maintenance contracts. Its procurement checklist includes ongoing operating needs and expenses. Both sources were checked October 28, 2026. They do not establish the coverage or service commitments of a Xiaochong quotation.

Keep the requested term separate from the supplier answer

Try this fictional three-unit example in the RFQ brief builder. Enter the project market, three units and “60 kW per unit requested; feasibility under review.” Add the following text to Site constraints and notes. The 24-month term is a buyer request for this example, not an offered warranty or recommended universal term.

• Revision A, 28 October 2026. Fictional RFQ; 3 units requested.
• Warranty requested: 24 months; supplier confirmation pending.
• Start event, covered equipment and exclusions: supplier to specify.
• Parts, labour, travel, freight and local service: included or excluded, and payer, to be stated.
• Response time, repair time and uptime scope: separate definitions and commitments requested.
• Claim contact, required records and post-warranty support: open. Reviewer and reply date: to assign.

The generated draft should retain these open questions and the three-unit quantity. It cannot interpret a warranty, confirm eligibility for a claim or compare contractual coverage automatically. Review the text before copying; edits clear the old generated result, while a copy already saved elsewhere remains unchanged.

Compare the written scope before comparing the duration

1. Term and equipment: ask what event starts the period, which model and components it covers, and what conditions or exclusions apply. Keep the bidder's wording and document revision attached to the response.
2. Cost and delivery boundary: ask the bidder to mark parts, labour, travel, shipping and local attendance as included, excluded or unresolved, with the responsible payer. Do not treat an unanswered line as included.
3. Service measurement: request separate definitions for initial response, repair completion and any uptime commitment, including the covered hours, locations, measurement period and exclusions. A fast acknowledgement is not evidence that service has been restored.
4. Handoff and review: identify the claim contact, permitted evidence and escalation route. Assign a buyer reviewer and due date to each open item. Keep requested, offered and agreed terms in separate columns in the project comparison record.

This is an original purchasing worksheet. Final coverage depends on the written offer and agreed terms for the selected equipment and market; no repair deadline, availability or cost saving is promised here. Discuss inspection and repair with authorized service personnel. Do not open energized cabinets, perform electrical tests or bypass charging protections to establish a warranty claim. Keep credentials and unnecessary personal data out of the brief.

Match OCPP certificate evidence to the quoted product

A certificate attachment and an “OCPP supported” line answer different questions. Before comparing bids, record what was requested, what the supplier claims, and which product and software the evidence names. Keep an unresolved match open rather than copying “certified” into the approved requirements column.

For a fictional two-charger RFQ, suppose the attachment names Product A, software 1.0, while the quote names Product B, software 2.0. These are invented labels, not actual products or certificates. The mismatch is a clarification request—not proof of certification, and not proof that the document is false.

1. Identify the object: distinguish the charging station from its charging station management system (CSMS). Record the OCPP version, product designation and software version shown in the offered configuration and in the evidence. Ask for a written explanation of differences.
2. Check the official record: use OCA's verification guidance and certified-products list to check the certificate number and listed scope. If a record cannot be located, record the search details and seek OCA clarification rather than declaring the product certified or the document fraudulent.
3. Read the included scope: OCA's OCPP 1.6 certification page distinguishes Core, Smart Charging and Advanced Security. For charging stations, Core is mandatory; Smart Charging and Advanced Security are optional. Do not apply that station profile summary to CSMS or to another OCPP version.
4. Close the procurement question: request applicable documents, an explanation linking them to the offered configuration, the reviewer and a response date. Keep project-specific backend integration, payment, electrical safety and destination-market requirements as separate evidence questions; this certificate check does not approve them.

Keep the request and the evidence status separate in the brief

In the RFQ generator, enter 2 units and a preliminary power request marked under review. Set OCPP / platform requirement to “OCPP 1.6 charging station; CSMS under review” and Certification / tender requirement to “Applicable OCA certificate evidence requested; not verified”. Paste these original example notes:

• Revision A, 19 October 2026. Fictional evidence review; 2 units requested.
• Quote: Product B / software 2.0. Attachment: Product A / software 1.0.
• Certificate number, station/CSMS role and included profiles: supplier to provide.
• Applicability unresolved. Ask for official record and written scope mapping.
• Buyer technical reviewer and response date: to be assigned. No certification conclusion.

The tool preserves these statements as buyer-entered draft text; it does not search OCA, authenticate a certificate, compare software versions or confirm compliance. Review the copied draft before sending and exclude credentials or private certificate-access tokens. This is a desk-based procurement review, not an electrical test or instruction to change equipment software.

Official source review: October 19, 2026. The three OCA pages above provide verification, listing and OCPP 1.6 profile context. The example and clarification workflow are original Xiaochong guidance, not an OCA certification procedure or a claim that any Xiaochong model is certified. Earlier source review dates below remain attached to their original examples.

Three units delivered does not mean three units ready to operate.

Consider a fictional buyer requesting three chargers for one site. The equipment supplier offers delivery, a local contractor is expected to install them, and the operating platform has not been selected. Calling this a “complete charging project” would hide two unresolved handoffs. The RFQ should ask for a response to each boundary, not treat arrival of the cabinets as commissioning evidence.

In the RFQ brief builder, enter 3 as the estimated quantity and a preliminary power request, labelled subject to review. Put this original example in Site constraints and notes; replace every proposed owner with a confirmed project party before relying on it:

• Revision A, 10 October 2026. Request: 3 units; specification under review.
• Equipment delivery: supplier response requested; delivery point and unloading owner open.
• Site installation: proposed local contractor, not appointed; supply assessment and approvals open.
• Platform onboarding: provider not selected; integration scope and recurring fees open.
• Commissioning and handover: owner, acceptance evidence and service contact not agreed.

Copying these lines does not appoint a contractor or create a supplier obligation. The generator preserves the line breaks and order in the preview, clipboard and encoded email/WhatsApp text, making the open responsibilities easier to review. It does not parse the notes into verified facts or check whether a promise has been accepted.

Ask for one response at each handoff.

1. Delivery: ask which equipment and documents are included, where delivery ends, who handles unloading, and what remains excluded. A requested date is not a confirmed lead time.
2. Installation: name the party responsible for site assessment, local works and required approvals. Record dependencies and evidence needed before work starts; leave unknown electrical capacity unresolved. This is a scope discussion, not an installation method.
3. Platform: identify the intended charging backend, equipment/software scope, onboarding owner and one-time versus recurring services. An OCPP label alone does not say who purchases connectivity or completes integration.
4. Handover: agree who reviews commissioning evidence, records exceptions and receives the service documents and support contacts. Separate delivered, installed, commissioned and accepted status; do not label unfinished work complete.

Use the same revision when requesting clarification from each bidder. Keep the original exclusions visible until the parties resolve them in writing. Resetting or editing the form removes the old on-page brief and sharing buttons; copies already in another app are unchanged. Inspect the new draft before sending. Do not include credentials, card data or unnecessary personal information.

Official context, rechecked October 10, 2026: DOE AFDC procurement and installation guidance distinguishes equipment, installation, networking, ownership and project partners. OCA's protocol overview defines charging-station/central-system communication. The example and handoff worksheet are our original planning aids, not a DOE/OCA contractual requirement, certification or site approval. U.S. guidance is background; destination-specific requirements and qualified local professionals control electrical work. No energized testing or protection bypass is part of this workflow.

Two chargers now, six later: keep the optional scope out of the base quote.

In this fictional RFQ, a fleet buyer requests two units initially and wants a separate option for four additional units later. Six is the potential future total, not six extra units and not a confirmed order. No capacity, product selection or savings outcome is implied by this example.

1. Initial request: enter 2 in Estimated quantity. State the requested power range as a buyer requirement, not verified output or available site power.
2. Optional expansion: in notes write “Revision A, 1 October 2026. Initial request: 2 units. Separate option: 4 additional units, potential total 6. Expansion is not committed; site capacity and layout remain under review.” This avoids silently mixing the base price with future equipment.
3. Evidence boundary: leave unknown AC supply information blank. If verified information is available, identify its source and date in notes; the generator cannot verify a survey or a document. An entered voltage does not establish spare capacity.
4. Supplier response: ask each bidder to name the brief revision, separate base and optional prices, and state assumptions, exclusions, quote validity and outstanding model/platform/market evidence. A requested certification or delivery date is not an achieved certification or a supplier promise.
5. Revision control: if initial quantity changes to 3, issue Revision B to every bidder and clarify whether the future total remains 6. Do not compare a Revision A base quote with a Revision B quote without reconciling the scope difference.

The RFQ generator now labels exports as draft buyer inputs, accepts only whole-unit quantities, and clears the old brief and its sharing buttons after an input or language change. Generate and review the new version before copying. Copies already placed in another app do not update automatically. Opening an email or WhatsApp link hands the text to that service or app; final sending remains your action. Keep credentials, card details and unnecessary personal data out of the form.

Planning context rechecked October 1, 2026: DOE AFDC procurement guidance distinguishes near- and long-term requirements, utility coordination and project costs. OCA's protocol overview provides the charging-station/backend communication context. The revision and optional-scope method above is our original buyer workflow, not a DOE or OCA approval, engineering design or contract.

Common buyer questions.

Primary technical sources.

The DOE AFDC operation/maintenance and procurement pages linked in the warranty section were reviewed October 28, 2026. The OCA verification, certified-products and OCPP 1.6 certification pages retain their October 19 review date; the OCA protocol overview retains its October 10 date. The remaining sources are historical background. Product-specific documentation and local requirements still control final decisions.

• U.S. Department of Energy AFDC — Procurement and Installation for EV Charging Infrastructure ↗
• Joint Office of Energy and Transportation — Public EV Charging Infrastructure Playbook ↗
• Open Charge Alliance — Open Charge Point Protocol ↗
• Open Charge Alliance — Security Operations Guide ↗