How EV Installers Can Evaluate a Charging Software Reseller Offer

A practical guide for EV installers selecting charging software to resell: customer ownership, support, compatibility, commercial scope and pilot acceptance.
Adding software to an installation proposal changes the relationship after commissioning. Someone must onboard the site owner, answer driver questions, maintain the configuration and reconcile problems that cross hardware and software. Before putting your brand on an offer, decide which of those responsibilities your business intends to own. This guide is a selection framework, not a promise of recurring revenue.
Choose the role before choosing the platform
ReferralYou introduce the customer and agree how the software provider takes over. Establish who contracts, invoices and supports the customer.
ResellerYou include software in your commercial offer. Define renewal, pricing control, billing and the boundary between your support and the supplier.
Managed serviceYou operate some or all of the ongoing service. Budget for people, monitoring, escalation and customer communication as well as a licence.
These are possible business arrangements, not standard Sock8 partner entitlements. A supplier may offer only some models, with different eligibility and terms. Ask for the proposed agreement and confirm the responsibilities with your own team before describing the service to a customer.
Check the service with one representative installation
Start from the charger model and firmware, connector count, payment requirement and site use case of a real project. Decide which customer journeys must pass before rollout. A workplace access workflow, a public pay-to-charge journey and a fleet reporting requirement can need different configurations. Do not use an unrelated showcase as evidence that your project is ready.
Write the customer and data boundaries down
Clarify who is the contracting supplier, which brand appears in customer communication and who answers operational questions. Determine who can see each site, export session information and update tariffs. Name the parties responsible for notices, data processing and retention. Legal and payment arrangements depend on the actual market and contracts; a white-label interface does not settle them.
Price the service you can actually deliver
Separate one-time onboarding from the recurring software charge and your own work. For each proposed customer, include implementation, training, first-line support, escalation and any payment or integration costs. Check minimum commitments, dormant connectors, renewal conditions and currency exposure. Any margin calculation should use your costs and signed supplier terms, not a claimed industry margin.
Avoid a support gap between hardware and software
Agree who collects logs, who can access the device, who communicates with the site owner and who decides that a field visit is necessary. Document where electrical or hardware work must be handled by the appropriate qualified provider. Give staff an escalation checklist and a clear way to distinguish a software issue from a site, network or charger problem.
Use a pilot with a decision at the end
ScopeName the site, hardware, operating flows, people and exclusions. Confirm who pays and what the price includes.
EvidenceRecord expected results, logs, support responses and outstanding gaps. Use test data where possible.
Commercial decisionState what happens at completion: rollout terms, further validation, a revised scope or stopping. Any pilot credit must be agreed, not assumed.
A supplier conversation is useful when you have an upcoming project, an identifiable decision-maker and an unresolved software requirement. Sock8 can be evaluated for that scope; reseller conditions, support commitments and integration needs should be confirmed during discovery. Bring the project details rather than asking for a generic partnership promise.

