01
Identify
Record the exact model, firmware, OCPP version, security profile, connector layout, and network configuration.
Hardware independence with evidence
OCPP charger compatibility verified by model and firmware
Sock8 evaluates charger compatibility at the level operators actually deploy: manufacturer, model, firmware, OCPP version, security settings, connector layout, and required transaction flows.
A charger is treated as production-ready only after the relevant boot, status, authorization, session, metering, remote-command, recovery, and error behaviours have been exercised. A compatibility catalogue is available during technical discovery.
Who it is for
Built for teams accountable for live charging.
- CPOs selecting or onboarding hardware
- Charger manufacturers validating integrations
- Networks operating mixed-brand estates
- Procurement and technical due-diligence teams
Problems it solves
Replace operational blind spots with one system.
- Compatibility assumed from an OCPP logo
- Firmware changes altering message behaviour
- Incomplete connector and meter-value mapping
- Hardware purchases made before backend validation
How it works
A clear path from connection to daily operation.
02
Connect
Verify endpoint connectivity, identity, boot acceptance, heartbeat, and status transitions.
03
Exercise
Run the required authorization, transaction, metering, command, offline, reset, and fault scenarios.
04
Approve
Document the supported profile, constraints, configuration, evidence, and conditions for production rollout.
Product view
See the operating detail behind the promise.
The compatibility catalogue records charger profiles used by network teams during onboarding and operations.
Representative Sock8 product interface
Features
Capabilities included in the product scope.
- Model and firmware records
- OCPP message validation
- Connector and meter mapping
- Remote-command verification
- Offline and recovery checks
- Documented limitations and rollout conditions
Protocols and interfaces
Designed to connect the charging stack.
OCPP 1.6JOCPP 2.0.1WebSocketTLSVendor extensions by scope
Implementation or migration
Move from technical discovery to a controlled launch.
- 1
Compatibility request
Submit exact hardware and firmware information plus the operating flows the network requires.
- 2
Evidence review
Check existing validation records and identify gaps introduced by firmware, configuration, or use case.
- 3
Bench validation
Connect a representative charger and execute the agreed positive and negative test plan.
- 4
Field approval
Confirm production configuration, pilot at a real site, and approve the rollout profile.
Customer evidence
Multiple charger brands operated centrally
6 wks to migrate · 400+ connectors
Echarge Moldova · Moldova
The migrated network demonstrates why compatibility must be managed across a mixed hardware estate rather than assumed once.
Evidence shown is limited to the named deployment facts currently approved for this site.
Deployment
Choose the operating boundary.
Compatibility validation is available for networks adopting Sock8 managed cloud or customer-hosted software.
Pricing information
Scope the commercial model.
Existing approved profiles are reviewed during discovery. New model, firmware, vendor-extension, or specialised test work may be quoted separately.
View platform pricingBuyer FAQs
Questions technical and commercial teams ask.
Is every OCPP charger compatible?+
No. OCPP support alone does not establish production compatibility; the exact model, firmware, settings, and required flows must be checked.
Why does firmware version matter?+
Firmware can change message fields, timing, security, meter reporting, command support, and recovery behaviour.
Can Sock8 test a charger before we buy it?+
Yes, when a representative unit or accessible test environment is available for the agreed validation plan.
What does approval cover?+
Approval records the tested model, firmware, configuration, protocol profile, scenarios, known limitations, and rollout conditions.
Can vendor-specific extensions be supported?+
Required extensions can be evaluated and scoped when they are documented and testable.
Next step