Source integrated EV chargers from a factory that develops the hardware, firmware and software in-house, and that lets you talk to its engineers before you order. “Integrated” means the charger, its firmware, the app and the back-office connection are designed to work together. “Factory-direct R&D support” means changes to any of them are scoped by the people who built them, not passed through a trading company. For a brand running an ODM project, that is the difference between a request answered in days and one that stalls. This guide shows what to ask for, how to verify it, and what to agree in writing.
Key Takeaways
- Integrated = hardware, firmware, app and OCPP connectivity designed as one system.
- Real R&D support shows up as engineers on calls, written change scopes and samples that match the agreed configuration.
- EVDANCE develops power electronics, embedded firmware, enclosure design and cloud software in-house, according to its Technology & R&D page.
- Agree firmware ownership, update responsibility and app branding before the first sample.
- Verify by video audit or a facility visit to the Shenzhen headquarters.
What “Integrated” Should Cover
| Layer | What it includes | Why a brand cares |
|---|---|---|
| Power electronics and enclosure | PCB and power-stage design, protection, sealed housings | Decides ratings, IP protection and what can be re-certified |
| Embedded firmware | Charging control, current settings, display screens, LED behaviour | Where branded screens and market-specific settings live |
| App and cloud | Remote start/stop, live session data, OTA updates, multi-user access, RFID / QR / app authentication | Your customers see the app every day; it can carry your brand |
| Back-office protocol | OCPP 1.6J or 2.0.1 | Lets operators connect units to their own management platform |
EVDANCE’s Technology & R&D page describes all four layers as developed in-house, with a shared hardware and firmware platform across product families. The same page lists private-label firmware and a private-label mobile app among the OEM/ODM options. For OCPP coverage by model, see OCPP across the EVDANCE range.
Why does it matter who owns each layer? When a charger is assembled from a controller bought from one company, an app licensed from another and a housing from a third, every change request has to travel through all of them. Each party can only answer for its own part. With one engineering team behind every layer, a request such as “lower the maximum current and show our logo on boot” is a single scope from one source, and the factory can tell you straight away whether it touches any test report.
Signs That R&D Support Is Factory-Direct
- You can speak to an engineer. A technical call before the quote, not only a sales contact.
- Change requests come back as a written scope: what will change, what stays, and whether any testing must be repeated.
- Samples match the scope. The first sample is built to the agreed configuration, not a stock unit with a sticker.
- The factory explains the limits. A supplier that says yes to everything without mentioning re-testing is a warning sign.
- Production and R&D share a site. At EVDANCE, OEM and ODM customisation requests are scoped and validated in the R&D lab at the Shenzhen headquarters, alongside the production lines (see the factory tour).
You can verify much of this remotely. Video factory audits explains what a video call can and cannot prove. A facility visit, combined with a technical briefing, settles the rest.
Typical ODM Requests and What They Involve
| Request | Usually involves | Retesting risk |
|---|---|---|
| Branded start-up screen and LED colour | Firmware graphics and settings | Low |
| Different current steps or a lower maximum | Firmware configuration, label change | Low to medium, depending on the rating change |
| Market-specific supply plug or connector | Cable assembly change | Medium: reports must cover the new configuration |
| Private-label app | App branding and account setup on the cloud platform | Low for the charger; agree data and update responsibilities |
| OCPP connection to your platform | Integration testing with your back office | Low for safety; plan time for integration |
| New housing shape | Moulds (full OEM, 500+ units) | Re-check of IP rating and thermal behaviour |
If OCPP matters, read OCPP 1.6J vs 2.0.1 for manufacturers before you write the brief.
What to Agree in Writing Before the Sample
- Configuration sheet: model, rating, plug, connector, cable length, radio modules, screen and LED settings.
- Firmware ownership and updates: who releases updates, how they reach units in the field, and how you are notified. See firmware ownership and updates in a supply contract.
- App branding scope: name, icon, colours and languages.
- Test evidence: which reports cover the configuration and what, if anything, needs new testing.
- Sample approval: how the approved sample is recorded so production matches it.
The charging pile OEM/ODM guide places these steps in the full brief-to-shipment sequence. If the brief is mainly about appearance, what a brand can customise on a wallbox may be all you need.
Have an ODM brief? Share the target market, power level, connector and feature list on the EV charger OEM & ODM page. We propose a configuration, build samples for your testing, then move to production.
Frequently Asked Questions
Is ODM available on small quantities?
Custom orders start from 100 units with logo print and a choice of colourway. Deeper changes such as moulds start at 500 units. Samples of 1–9 units come first.
Can I visit the factory before ordering?
Yes. Distributors evaluating an OEM or wholesale partnership can combine a facility visit with a technical briefing from the engineering team.
Will a private-label app change the charger’s certification?
App branding does not change the charger’s electrical design. Changes to radio modules or hardware may affect test reports, so confirm in the written scope.
