Commerce Solutions for Utilities

Built for Utility Commerce, Not Utility Billing

Broadleaf is the source-available commerce platform for utilities selling equipment on payment plans, running commercial accounts with usage-based pricing, and quoting contract work. It runs alongside the CIS and billing systems you already have, licensing is fixed, and you can deploy it wherever your infrastructure lives.

Technician explaining a heat pump to a homeowner couple outside their home
  • Payment Options for Equipment Your Customers Buy or Lease

    Sell heat pumps, EV chargers, batteries, and efficiency equipment outright, on installments, or on a lease, with in-home installation and service priced into the same payment schedule.

  • Commercial and Industrial Account Portals

    Multi-site account hierarchies, contract pricing by commercial customer, and quote-to-contract workflows for large energy buyers.

  • Quoting and Contract Pricing

    Sales teams negotiate and issue quotes inside the platform, with contract pricing that applies by account, segment, or service territory.

Heat pump with purchase, installment and lease payment options on a phone checkout

Payment Options for Equipment Your Customers Buy or Lease

  • Purchase, Installment, and Lease Terms on the Same Equipment

    One piece of equipment can be offered three ways: bought outright, paid down over a set number of months, or leased with a buyout at the end of the term. Configurable products and the Subscription Operation Service model the term length, the recurring charge, and what happens at renewal, so the same catalog item carries every option a program allows.

  • Installation, Electrical Work, and Service Priced Into One Schedule

    A heat pump on the wall costs more than the heat pump itself. Bundle the equipment with in-home installation, the electrical work that install requires, and an ongoing service or monitoring plan, then present it as one price and one payment schedule. Line-level configuration keeps the scope and cost of each contributor visible on the order for the teams who have to settle it.

  • Credit Terms and Eligibility by Program or Rate Plan

    The Credit Account Service carries account credit and net terms for customers who qualify for them. Customer Segments and Pricing Terms decide which payment options a given customer sees, based on rate plan, service territory, or program enrollment, and usage-based pricing defines the rate logic your billing system consumes downstream.

Engineer at an industrial plant, with a multi-site commercial utility account

Commercial and Industrial Account Portals

  • Account Hierarchies for Multi-Site Customers

    Model a corporate parent with multiple facility sub-accounts, each with its own service addresses and pricing context. Admin tools roll up the hierarchy.

  • Pricing Terms and Multi-Territory Rates

    Customer Segments and Pricing Terms apply tiered pricing by commercial customer size, contract structure, or load profile. Application-specific price lists model multi-territory rate variations. The pricing engine runs in the platform, not as hardcoded rules.

  • Self-Service Account Members with Roles

    Energy managers, procurement leads, and facility teams each get role-scoped permissions, approval thresholds, and visibility into their account’s history.

Approved quote with contract pricing sent to ERP as a purchase order

Quoting, Contract Pricing, and Procurement Workflow

  • Quote Negotiation for Multi-Site Deals

    Sales reps and commercial buyers initiate, negotiate, and approve quotes inside the platform. Quoted prices bind to the account and expire on a configurable schedule.

  • Contract Pricing by Account, Segment, or Service Territory

    Contract pricing applies at the account, segment, or service-territory level. Application-specific price lists model multi-state rate variations. Customer Segments handle commercial tiers and regulated rate categories.

  • ERP, Billing, and Back-Office Integration

    Integrate with CIS, billing, ERP, and procurement systems through the platform’s REST API surface and the Data Exchange Service. When an integration does not fit a standard pattern, the source-available code lets your team handle it at the service level.

Broadleaf Commerce logo surrounded by React, Kubernetes, Spring, Java and Docker icons, representing custom extensions

Architecture Closed Platforms Cannot Match

  • Source-Available with Four Extensibility Layers

    Java and Spring Boot, source-available with four extensibility layers (Data, Microservice, API, Admin). TM Forum certified (TMF620, TMF687) for standards-based integration. When configuration is not enough, your team modifies the platform at the source.

  • No Vendor-Roadmap Bottleneck

    When a usage-based rate needs a custom calculation, a subscription needs a non-standard renewal flow, or a payment plan needs an approval step nobody anticipated, closed platforms make you wait for their roadmap. With Broadleaf, your team can build it.

  • Compliance Posture You Own

    Deploy on AWS, Azure, GCP, on-prem, or your existing compliance-controlled infrastructure. Source-available code and deploy-anywhere flexibility keep your compliance team in control of infrastructure, data residency, and audit posture.

Fixed annual commerce license with 0% revenue share and 0% transaction fee

Commercial Terms Built for Regulated Buyers

  • Fixed Licensing, No GMV Tax

    Fixed annual licensing covers worldwide use across brands, geographies, users, and API volume. There are no usage-based fees that climb when a new program launches or when seasonal demand spikes, so the number you budget is the number you pay.

  • Perpetual Licensing Option

    Utilities that prefer to carry the platform as a balance-sheet asset have a perpetual licensing path alongside subscription.

  • Vendor Stability

    Employee-owned and privately held, Broadleaf has never faced a forced pivot from investor pressure or an acquisition. Utility contracts run for years, and procurement teams weigh whether a vendor will still be independent at the end of one.