An EV charger quotation is only useful when it describes the equipment, software, documentation, and support your project will actually receive. Before shortlisting a manufacturer, connect every essential requirement to a specific model, a verifiable document, and an agreed acceptance criterion.
For distributors and importers, the decision includes repeatable supply and responsibility for the destination market. For commercial projects and fleets, it also includes the charging schedule, site constraints, operating platform, and recovery when equipment needs attention. OEM/ODM buyers need a further boundary: exactly what can change, who owns the resulting design, and which changes require fresh evaluation.
Use this checklist to build a comparable request for quotation (RFQ), review supplier evidence, and decide whether to proceed to a sample or pilot order. The decision rules below are procurement recommendations. They do not establish any supplier’s certification or replace a destination-specific compliance assessment.
1. Define the project before comparing manufacturers
Give each supplier the same requirements sheet. Otherwise, a lower quotation may simply exclude something another supplier included.
The U.S. Department of Energy’s charging infrastructure procurement checklist identifies project scope, utility coordination, networking, ownership, delivery, and ongoing costs as planning considerations. Its guidance is a U.S. reference, rather than a universal specification for other markets.
Build a one-page requirements sheet
Include:
- Destination country and project location; identify each market separately for a multi-country purchase.
- Use case: fleet depot, workplace, commercial parking, public charging, or distribution stock.
- Vehicle models or vehicle requirements to be evaluated, parking arrangements, and charging windows.
- Expected daily energy demand, number of charging sessions, and simultaneous charging needs.
- Site electrical information already confirmed by the project team; list unresolved supply constraints explicitly.
- Proposed connector, cable, mounting, environmental, and accessibility requirements for local review.
- Operating platform, user access, payment and reporting requirements, where applicable.
- Initial quantity, forecast quantities, required delivery milestone, and budget boundaries.
Ask suppliers to mark each requirement included, optional, not supported, or requires clarification. Require a document or test reference beside each essential technical response.
Ask for a configuration, not just a power label
Request the complete orderable model code and a dated configuration sheet. Ask the manufacturer to distinguish total equipment output, output per connection, and proposed behavior when vehicles charge simultaneously. Have the project engineer review those answers against the actual use case and site constraints.
Treat an unconfirmed requirement as an open item. Do not let a generic catalogue become the final specification by default.
2. Verify evidence against the exact model and market
A certificate logo or an undated sales PDF is a starting point for a question. Your procurement file should identify the document issuer, covered product, applicable scope, and connection to the configuration being purchased.
Create a model-to-document register
For each proposed model, request:
- Legal manufacturer name, manufacturing location, and the entity issuing the quotation.
- Model code, hardware revision, firmware version, and relevant options.
- Current datasheet, installation documentation, operating instructions, and maintenance information.
- Applicable declarations, certificates, listings, and supporting reports for the destination market.
- Document numbers, issue dates, revision details, scope limitations, and an issuer verification route where available.
- An explanation of any difference between the model on the document and the model on the quotation.
Where evidence covers a product family, ask the supplier to identify the exact covered variant and permitted options. Refer unclear coverage to the issuer or a qualified destination-market reviewer before treating the requirement as satisfied.
Keep different forms of evidence separate
For products subject to CE marking, the European Commission describes the manufacturer’s responsibilities for conformity assessment, technical documentation, the EU declaration of conformity, and marking. Use its manufacturer guidance to frame document questions; the applicable legislation and assessment route still need to be identified for the product.
Ask a compliance reviewer to record which documents are required for your proposed configuration and destination. Keep that assessment separate from voluntary certificates, company-level quality-system documents, and software conformance evidence.
For the UK, North American destinations, Australia, Middle Eastern countries, Southeast Asian countries, South American countries, and Türkiye, commission a separate requirements review for the relevant country and project. Do not copy an EU evidence checklist into every market and assume it is sufficient.
Hold point: an essential model-to-document mismatch remains unresolved. Keep the supplier under review and withhold the procurement approval that depends on that evidence.
3. Test the operating workflow with the intended platform
Specify what the operator needs to do, then ask the manufacturer to demonstrate it with the proposed equipment and software configuration.
If OCPP is part of your requirements, request the version and implementation details. The Open Charge Alliance offers independent OCPP conformance certification, including programs for OCPP 1.6 and 2.0.1. Verify any claimed certificate against the relevant product and scope. Separately, require evidence that your intended operating workflow works with your chosen platform.
Define observable acceptance scenarios
Agree which scenarios apply, who will witness them, and what constitutes a pass:
- A permitted user can start and stop a session through the intended access method.
- The operating platform receives the session records and fields your reporting process requires.
- The agreed behavior during a communications interruption is demonstrated, followed by reconnection and record reconciliation.
- Remote diagnostics and the agreed update process can be demonstrated by authorized personnel.
- Any required charging limits or allocation controls behave as specified in the project test plan.
- Where required, payment and reporting workflows can be reviewed end to end with the relevant service providers.
Record the model, hardware revision, firmware, platform version, setup, result, and unresolved defects. Treat a supplier demonstration as evidence for that tested configuration, rather than proof of every possible integration.
Clarify software ownership and access
Ask who controls administrator access, configuration backups, operational data, and software subscriptions. Request the terms for data export, platform changes, update support, and service discontinuation.
For security review, request the manufacturer’s documented approach to access control, update authorization, vulnerability reporting, and support duration. Have your IT team assess the answers. Avoid accepting an undefined “secure platform” statement as the contractual requirement.
4. Separate OEM/ODM customization from standard supply
For a private-label order, attach a customization schedule to the quotation. “OEM available” leaves too many decisions open.
Put every requested change in a scope table
For each change, record the deliverable, responsible party, approval step, added cost, schedule dependency, and evidence that needs review. Consider:
- Branding, labels, packaging, manuals, and language versions.
- Enclosure or mechanical changes.
- Cable, connector, communications, or other configuration options.
- User interface and platform integration work.
- Tooling, drawings, design files, and intellectual-property ownership.
- Responsibility for reviewing conformity documentation after a change.
Ask the supplier to distinguish a standard option from a new development task. Request written confirmation of whether the proposed change affects the evidence supplied for the standard product.
Freeze the approved configuration
Identify the approved sample and revision in the order documentation. Agree how component, firmware, manufacturing-location, or design changes will be notified and reviewed before supply.
Distributors and importers should also settle territory, branding rights, technical-document access, and responsibility for customer support. Record negotiated terms rather than assuming they follow automatically from a private-label arrangement.
5. Review production controls and sample acceptance
A successful sample is useful, but your purchase also needs a way to connect subsequent units to the approved configuration.
Ask for a description of production controls relevant to the proposed model: configuration identification, inspection records, unit traceability, nonconformance handling, and shipment release. Where a factory review is appropriate, define its scope and who will conduct it. Photographs can support a discussion; they do not resolve questions about the quoted production process on their own.
Agree acceptance before placing the order
Create an acceptance plan covering documentation, configuration, software integration, packaging, and agreed functional checks. Technical and electrical testing should be defined and performed by appropriately qualified personnel under an approved procedure.
For every acceptance item, write down:
- The requirement and reference document.
- The test or review method and responsible person.
- The expected result and evidence to retain.
- The process for resolving a failure.
- Whether the issue blocks shipment, site acceptance, or final payment.
Keep factory acceptance and site acceptance distinct in the contract. Assign responsibility for prerequisites such as site readiness, platform access, commissioning support, and availability of the intended vehicles.
6. Compare lifecycle cost and recovery responsibilities
Ask for an itemized commercial response with a consistent boundary. The DOE procurement guidance treats equipment, installation, operation, and maintenance as cost considerations. Use that distinction when comparing offers, while obtaining project-specific local estimates.
Request included, excluded, and recurring costs
Compare hardware and options, freight and delivery terms, locally assessed import costs, platform subscriptions, communications, payment-service charges where relevant, commissioning support, training, spares, and maintenance. Mark unknown amounts as unresolved rather than entering zero.
Ask for quote validity, minimum order quantities, sample terms, payment milestones, and the assumptions behind delivery dates. These are terms to obtain from each supplier, not figures to infer from its website.
Define what happens after a fault
Request written warranty coverage and exclusions, the warranty start point, claim evidence, escalation contacts, and allocation of diagnostic, labor, freight, and replacement costs.
Ask which parts can be serviced locally, what training or authorization is needed, how spares will be identified, and what availability commitments the supplier will make. Distinguish an initial support response from diagnosis, dispatch, and restored operation when negotiating service commitments.
For a fleet or commercial site, have the operator describe its contingency plan during a service interruption. Include that operational consequence in the purchase review without inventing a financial saving or downtime guarantee.
7. Use evidence gates before a supplier score
Set mandatory requirements before reviewing quotations. Examples include acceptable destination-market evidence, the required configuration, successful essential integration scenarios, and written acceptance of critical commercial terms.
Use three outcomes for each gate:
- Pass: the requirement is supported by reviewed evidence.
- Open: an owner and due date are assigned to a specific missing item.
- Fail: the response does not meet the requirement.
Only compare suppliers for the next approval stage once its mandatory gates pass. For the remaining trade-offs, use evaluation categories that fit your project: operational fit, customization scope, production controls, support, delivery confidence, and lifecycle cost. Set any weights before scoring and record the evidence behind each judgment.
A missing mandatory document should stay visible as a gate. It should not disappear inside a favorable average score.
Copy this checklist into your RFQ
Ask each manufacturer to return a response with attachments against these items:
- ☐ Exact orderable model, configuration, hardware revision, and proposed firmware.
- ☐ Requirement-by-requirement response with exceptions and optional items identified.
- ☐ Model-to-document register for the named destination market.
- ☐ Explanation and verification route for any certification or conformance claim.
- ☐ Proposed platform integration and witnessed acceptance scenarios.
- ☐ Software access, data export, recurring fees, update support, and exit terms.
- ☐ OEM/ODM scope, ownership, approval steps, and change-notification process.
- ☐ Sample plan, production traceability, acceptance evidence, and failure-resolution process.
- ☐ Itemized quotation, delivery assumptions, payment milestones, and exclusions.
- ☐ Warranty, service responsibilities, spares proposal, and escalation contacts.
- ☐ Open-item register naming the owner, evidence required, and decision deadline.
Before approving the next purchase stage, review the open-item register with procurement, engineering, operations, and the destination-market compliance reviewer. Advance the order when the evidence supports that stage’s decision.
Prepare a sourcing discussion with MegaEVSE
Use the checklist to assemble your destination market, application, vehicle requirements, site constraints, quantities, timeline, and any OEM/ODM scope. Then contact MegaEVSE to discuss the proposed requirement and request model-specific documentation and a written scope.
This guide does not assign certifications, protocol support, compatibility, or performance to any MegaEVSE model. Confirm those details for the exact configuration under consideration.
Sources
- U.S. Department of Energy, AFDC: Procurement and Installation for Electric Vehicle Charging Infrastructure. Used for the planning and cost-category context; U.S. scope.
- European Commission: CE marking responsibilities for manufacturers. Used for the narrow explanation of manufacturer documentation responsibilities; product applicability requires separate review.
- Open Charge Alliance: OCPP certification. Used for the description of its conformance certification programs; no MegaEVSE certification claim is made.
Sources checked on 2026-10-14. The RFQ structure, evidence gates, acceptance-record suggestions, and commercial review questions are editorial recommendations.











