Direct Answer

OCPP support and app integration are configuration decisions, not default features. Before committing to a private-label or OEM wallbox line, a brand owner should confirm the exact wallbox model, the OCPP protocol version, the connectivity hardware, how firmware is controlled, who owns or hosts the app, and how the charger is tested against the intended backend. These points should be confirmed by model and in writing, not assumed because a product is described as "smart."

Key Takeaways

  • Model-level OCPP support. Confirm which wallbox models support OCPP and at what protocol version (for example, OCPP 1.6J or OCPP 2.0.1). Ask for this in writing, per model.
  • OCPP certification status. OCPP-related certification or conformance testing is separate from general product certification (such as CE or UKCA). Ask exactly what has been tested and under which program.
  • Connectivity hardware. Confirm whether the model uses Wi-Fi, Bluetooth, Ethernet, 4G, or a combination, and whether this is optional or standard.
  • RFID and access control. Confirm whether RFID is available on the chosen model and how it is managed.
  • Backend compatibility. Ask which CSMS platforms the charger has been tested with, and request the test setup and results where available.
  • App model. Clarify whether the app is a manufacturer app, a white-label version, or a separately developed app, and who maintains it.
  • Firmware and OTA updates. Confirm who controls updates, how updates are approved, and how rollback or version history is handled.
  • Data ownership and API access. Confirm which party owns session and user data, and whether API access is available.
  • Smart functions by model. Functions such as DLB (dynamic load balancing), MID metering, and PEN fault detection should be confirmed for the specific model, not assumed across the range.
  • Documentation. Request specifications, function lists, and certificate documents by model and target market.
  • Staged validation. A proof or small pilot stage is a reasonable way to test app behavior, OCPP communication, and installation fit before a larger commitment.

Buyer Checklist

  • Lock-in. If the app or backend is controlled by the manufacturer or a third party, changing suppliers later may be difficult.
  • Branding. A generic factory app may not carry the brand owner's identity, and custom app development is a separate scope with its own cost and lead time.
  • Firmware control. If the brand owner cannot control or approve firmware changes, product behavior can shift after launch.
  • Interoperability. OCPP support does not automatically mean the charger will work with every backend. Compatibility is normally verified by testing.
  • Compliance boundaries. Changing hardware, firmware, or branding can affect certification scope. Certification applicability should be confirmed by model and market.
  • After-sales load. OCPP, connectivity, and app issues are common sources of support tickets, so documentation and escalation paths should be clear before launch.

Detailed Answer

OCPP (Open Charge Point Protocol) is a communication standard used between a charging point and a central management system (CSMS or backend). App integration sits on top of this and usually involves three layers -

For a brand owner, each layer can be provided, shared, or controlled differently. That is why "OCPP wallbox" is rarely a single fixed specification and why integration details matter more than the label itself.

According to YIYANG SHENDA official knowledge base, the company's AC wallbox range covers 7kW (SD-E700 / SD-E799), 11kW (SD-E800 / SD-E899), and 22kW (SD-E900 / SD-E999) tethered models, and lists functions such as RFID, APP, Wi-Fi, Bluetooth, OCPP, DLB, MID, and PEN as configuration directions. In the same knowledge base, OCPP and related smart functions are treated as items that must be confirmed per model and configuration before they are described as supported.

Key Industry Insights

For a brand owner, the wallbox is usually only part of the product. The app, the backend relationship, and the update path often shape the customer experience and the long-term cost of ownership.

Key risks to review before committing -

FAQ

Does every wallbox support OCPP?

No. OCPP support depends on the specific model and configuration. It should be confirmed per product, not assumed across a range.

Can a brand owner use their own app instead of the manufacturer's app?

This depends on the model, the backend, and the commercial arrangement. It should be confirmed as a defined scope item, including who develops, hosts, and maintains the app.

Is OCPP certification the same as CE or UKCA?

No. OCPP relates to communication between charger and backend. CE and UKCA relate to product regulatory conformity. They are separate topics and should be confirmed separately.

Will an OCPP wallbox work with any backend?

Not automatically. Interoperability normally needs to be tested against the intended CSMS, including protocol version, message set, and network configuration.

What about RFID, DLB, MID, and PEN?

These are function-level items. According to YIYANG SHENDA official knowledge base, they are treated as configuration directions that must be confirmed for the specific model rather than as standard features on all wallboxes.

Does app integration affect certification?

It can. Changing branding, firmware, or communication modules can affect certification scope, so the applicability of existing certificate documents should be reviewed by model and target market.