Engineers can obtain complete EV charger supplier documentation by structuring requests around project phases, specifying required formats, and verifying compliance before installation. This guide outlines the exact steps to secure technical specifications and compliance documents.
- Request documents in phases to match installation and commissioning needs
- Specify file formats and language to avoid rework during integration
- Verify that compliance documents match the exact hardware revision
- Use a written checklist to track missing items before commissioning
Why the Request Format Matters
Engineers often receive incomplete data because requests are too vague. A supplier may send a general datasheet when you need the full technical specification sheet, or a generic certificate when you need the specific type-test report. The difference affects commissioning time, utility approvals, and warranty claims.
Start by identifying the documents your team actually needs. A commercial site requires different files than a home unit. A fleet depot with centralized control needs integration manuals and communication protocol details that a standalone unit does not.
Your request should name the exact model, firmware version, and hardware revision. Suppliers often maintain multiple revisions of the same chassis. A charger with a different power electronics module may have different thermal limits or communication endpoints.
For example, a high-power DC unit might be offered in a chassis that supports both 50 kW and 150 kW modules. The electrical cabinet dimensions are similar, but the cooling requirements and IP rating of the internal connectors change. If you request the datasheet for the 150 kW model but receive the 50 kW revision, your installation plan might assume a smaller breaker or a different ventilation clearance. This leads to field errors. Always confirm the hardware revision on the label before asking for the documents.
What to Ask For in the First Request
Begin with a structured email or form submission. List the documents you need in a table or numbered list. This prevents back-and-forth emails and gives the supplier a clear scope.
The first request should cover the baseline technical files. These are the documents you need to design the installation and verify the unit meets site requirements.
| Document Type | Purpose | Typical Format |
|---|---|---|
| Technical Specification Sheet | Electrical ratings, thermal limits, physical dimensions | PDF, DXF |
| Installation Manual | Mounting, wiring, clearance requirements | |
| Commissioning Guide | Setup, firmware flashing, network configuration | PDF, ZIP |
| Warranty Terms | Coverage duration, claim conditions | |
| Safety Datasheet | Materials, hazardous substances |
Do not ask for marketing brochures. They contain rounded numbers and promotional claims. You need the engineering data.
If you are integrating the charger with a central management platform, add a line for the communication protocol documentation. This includes the OCPP version, message sequences, and any proprietary extensions. A vague request for “connection details” often results in a one-page overview that lacks the field-level definitions your software team needs.
Consider the specific integration method. If you are using a cloud-based platform, you may need the MQTT broker details, topic structures, and payload schemas. If you are using a local gateway, you may need the serial port settings, baud rates, and frame structures. Ask for the exact interface version that matches your hardware.
How to Request Compliance and Certification Files
Compliance documents prove the unit is legally sellable and safe for your region. The specific files vary by market. You must name the standard or certification body you require.
For a European deployment, request the Declaration of Conformity and the CE marking certificate. For a North American site, ask for the relevant safety certification marks and test reports. The supplier may have multiple certificates for different models. You need the one that matches your exact unit.
A common mistake is asking for “certificates” without specifying the scope. A certificate for the charging unit does not automatically cover the integrated cable or the internal network module. Ask for the test report that references the full assembly.
If your site is in a region with specific utility requirements, include those in the request. Some utilities require proof of specific protection ratings or ground fault detection capabilities. The supplier’s standard compliance pack may not include these.
For instance, a utility in a specific grid region might require proof that the charger has a residual current device rated for a specific amperage or a specific response time. If you do not ask for the test report that demonstrates this performance, the utility inspector may reject the installation during the final inspection. Request the specific test report that shows the ground fault detection parameters.
Also, check the validity date of the certificates. A CE certificate might be valid for a specific production period. If the unit was manufactured outside that period, the certificate might not apply. Ask for the type-test report that references the specific hardware revision and production batch.
Managing the Integration and Software Handoff
Once the hardware documents are in hand, request the software integration files. This is where projects often stall.
Ask for the full API documentation, not just a summary. You need the request and response structures, error code lists, and heartbeat timing. A missing error code definition can take days to debug on site.
Request the firmware update procedure in detail. You need to know if the update is local via USB, over the network, or through a central platform. You also need the rollback procedure. If a new firmware release breaks a specific feature, your team needs a documented path to revert.
Specify the language. If your team is multilingual, ask if the documentation is available in a specific language. Translated manuals often lag behind the original by months. The technical data may be outdated.
When requesting API documentation, ask for the latest version. API specifications change frequently. An older version might miss new endpoints or changed error codes. If you are building a custom application, you need the source data, not just a PDF screenshot. Ask for the JSON schema or OpenAPI specification if available.
Also, request the data dictionary for any proprietary protocols. If the charger uses a custom telemetry format, you need to know the bit fields, data types, and scaling factors. Without this, your monitoring software will display incorrect values, such as showing power in watts when the unit is reporting in kilowatts, or displaying a negative value for a positive measurement.
How to Verify the Documents Before Installation
Do not rely on the supplier’s word that the files are complete. Check them against your project checklist.
First, verify the model number and hardware revision on every document. A datasheet for Revision A will not match the unit you received if it is Revision B. The serial number on the unit casing should match the warranty card.
Second, check the electrical ratings. Compare the rated power, current, and voltage in the datasheet with the utility service agreement. If the charger is rated for a three-phase supply, confirm the installation manual matches your site’s available power.
Third, review the commissioning guide. Read it through before the installer arrives. If the guide is missing a step for network configuration, ask the supplier to clarify before the unit goes live. A missing step during commissioning causes rework and delays.
Pay close attention to the physical dimensions and mounting requirements. The datasheet might list the width, height, and depth, but the installation manual might specify the clearance required for ventilation. For example, a rear-cooled unit might require a specific distance from the wall to allow airflow. If you ignore this, the unit may overheat and trigger thermal derating, reducing its output power.
Also, check the IP rating. The datasheet might state an IP65 rating, but the installation manual might specify that the rating is only valid when the service door is closed and the cables are correctly sealed. If you plan to install the unit in an open carport, you need to confirm that the specific configuration meets the environmental requirements.
Common Mistakes in Supplier Requests
Engineers make several avoidable errors when requesting documentation.
The first is asking for “all documents.” Suppliers interpret this as a vague request and send a zip file with outdated marketing materials. Be specific. List the document names.
The second is not specifying the file format. If you need editable CAD files for the electrical room layout, ask for DWG or DXF. If you need the communication spec, ask for the latest version. A PDF is fine for reference, but you need the source data for integration.
The third is ignoring the revision date. A document from two years ago may reference a firmware version that is no longer supported. Always check the date on the certificate and the datasheet.
Another mistake is not specifying the region. A charger might be certified for one country but not another. If you do not specify the target market, the supplier might send the generic European documentation, which lacks the specific safety marks required for your local grid code.
Also, avoid using generic terms like “spec sheet.” Instead, write “Technical Specification Sheet for Model X150-Rev C.” This removes ambiguity and forces the supplier to provide the correct file.
Final Verification Step
Before you sign off on the documentation package, run a final check.
Open the technical specification sheet and locate the model number. Confirm it matches the physical unit. Check the date. Open the installation manual and verify the wiring diagram matches your site’s electrical design. Open the compliance file and confirm the standard number is correct for your region.
Keep a copy of this checklist in your project folder. If a warranty claim arises later, you will have proof that the unit was documented and verified before installation.
If the supplier cannot provide a specific document, ask why. The answer will tell you if the unit is ready for your market or if you are dealing with a prototype that has not passed final certification.
For example, if a supplier cannot provide a CE marking certificate for a specific model, it may be because the model is still in the testing phase. In this case, the unit should not be installed in a commercial setting. Confirm the certification status in writing before proceeding with the installation.
How to Follow Up on Missing Items
Suppliers often miss items in the first round. Do not wait. Send a follow-up email within three business days if a document is missing.
List the missing items by name. Do not say “please send the rest.” Say “Please send the OCPP 2.0.1 message specification and the firmware update guide.”
If the supplier cannot provide a file, ask for a timeline. If they do not have a timeline, escalate to the project manager. A missing integration spec is not a minor delay. It blocks software development and site commissioning.
Document every follow-up in writing. Verbal promises are hard to enforce. A written record protects your team when the project goes over budget.
When sending the follow-up, include the original request in the thread. This provides context and ensures the supplier knows exactly which items you are waiting for. If the supplier responds with a partial package, check it against your list again. Do not assume the remaining items are coming. Ask for them explicitly.
If the supplier claims a document is “under review,” ask for the expected completion date. If the date is beyond your project timeline, consider alternative suppliers or negotiate a revised project schedule. Do not let the missing document block your installation planning without a clear resolution plan.
Conclusion
Requesting technical documentation is a controlled process, not a casual email exchange. Structure your requests by phase. Specify the exact model and revision. Verify the files against your project checklist.
When you do this, you reduce the risk of integration errors, utility rejections, and commissioning delays. You get the data you need, in the format you need, before the unit arrives on site.
Frequently asked questions
Can I request documentation in multiple languages?
Yes, but check the revision dates. Translated manuals often lag behind the original language by several months. Request the original language if possible.
What if the supplier does not have a specific compliance certificate?
Ask for the test report from the certification body. A certificate without the underlying test data is less useful for engineering verification.
How often should I check document revision dates?
Check before commissioning and again after any firmware update. A new firmware release may change the communication protocol or error codes.
Do I need CAD files for the installation?
Only if you need to verify physical clearances or mounting points. A standard PDF manual is usually enough for standard installations.
What is the best way to track missing documents?
Use a written checklist with columns for document name, version, and status. Review it with your team before signing off on the installation.
