Configurator
Assemble the right ChargeControl package for each customer context.
The configurator will guide resellers through domains, modules, and enablement options. It is not interactive on this page yet.
In development
What is available on this page today
The interactive configurator is not built yet. This page explains the packaging decisions it is meant to structure so partners can prepare customer context before a working session.
What the configurator is meant to help with
Choosing a domain starting point
Decide whether a customer begins with home, workplace, public, or a combined multi-domain package.
Selecting the module stack
Combine reimbursement, energy management, integrations, and reporting without overselling unused capability.
Setting an enablement path
Match onboarding, sales tools, and support intensity to partner maturity and customer complexity.
Clarifying delivery handoffs
Make install, go-live, and support boundaries explicit before a quote leaves the partner desk.
Where to go for package scoping now
Until the configurator ships, package design happens through the reseller program materials or a specialist who knows enablement, integrations, and rollout options.
Prefer to configure with a partner specialist
A ChargeControl specialist can walk a live customer scenario and map it to a package that your team can sell and deliver with confidence.
Schedule a demoWhy configuration needs more than a price list
Resellers rarely sell a single SKU. Customers mix domains, reimbursement rules, hardware ecosystems, and reporting needs. The configurator is being built to turn that mix into a guided package path partners can reuse across deals.
This page does not configure products and does not emit quotes or simulated carts. There are no form controls here. When the interactive configurator ships in Phase 2, it will replace this landing page at the same URL.
Until then, use the reseller program page for partner positioning and bring a concrete customer scenario to a demo: domains in scope, must-have workflows, and who owns installation versus operations. That conversation produces a clearer package than a static brochure.