Skip to main content
The Storefront is our energy shopping and enrollment experience, running inside a page on your site. Visitors compare plans, sign up and complete enrollment without leaving you. PowerHQ handles supplier relationships, compliance, enrollment operations and customer service behind it. No developer required. It goes on a page the same way a YouTube video or a Google Map does: one iframe, pasted once by whoever looks after your website. Everything below is optional detail for tuning placements, not work you have to do to launch.
This page is the reference. To actually get set up, work through the Storefront onboarding guide, which collects your branding, customer types and test IPs, and starts your agreement.
Your partner manager sends you a pre-built link. Every Storefront link follows the same shape, and knowing the pieces lets you run different placements on different pages.
The test environment uses the same structure on www.dev.powerhq.co. Production links are identical apart from the domain.
Send the link exactly as your partner manager built it, changing only the optional parameters above. Everything after the # is a URL fragment, which behaves differently from a normal query string, so reordering or reformatting it is the fastest way to break attribution.

​
Embedding it

​
Set the width to 100%

The experience is responsive, so give the iframe width="100%" and let it adapt to desktop, tablet and mobile rather than pinning it to a fixed pixel width.

​
Pre-load a ZIP code

If you already collect a ZIP on your site, pass it in and the customer lands straight on plan results for their area instead of typing it again.

​
One Storefront, different placements

You can run links with different parameters in different parts of your site. Point the link on your commercial pages at service_type=BUSINESS and the one on your consumer pages at service_type=RESIDENTIAL, and each placement shows only the relevant plans.

​
What you get without configuring it

  • Every deregulated market, one embed. The experience recognizes the customer’s market automatically. You do not maintain a version per state.
  • Residential and business by default. Restrict a placement with service_type when you want to.
  • Your brand. We apply your fonts and colors during setup, and customer emails can be sent under your own sender name rather than PowerHQ.

​
Partner codes

You get one partner code. If you want to track activity separately by site, channel, campaign group or sub-brand, we can set up a parent code with child codes underneath it. Every conversion is reported against the code that produced it, parent or child. Combined with utm_campaign, that gives you two independent tracking dimensions.

​
Testing

Onboarding collects the IP addresses your team will be testing from so we can enable your test links. Sending them early keeps your first run-through from waiting on us. Your live Storefront is open to everyone, as you would expect. Put the iframe on a staging page and run the flow as a customer would. Confirm:
1

It renders at every width

Check width="100%" behaves on desktop and mobile.
2

ZIP pre-loading works

Only if you are passing &zip_code= from your site.
3

Branding looks native

Fonts and colors should read as part of your page, not as a visitor.
4

The right customer types appear

Per placement, if you are using service_type.
5

Your codes flow through

Your partner code and utm_campaign values should appear in the daily conversion file.
Once testing passes, your partner manager sends production links with the same structure on the production domain, and you can go live immediately.

​
Reporting and attribution

You receive three reports. Fields in the daily conversion file: Order ID, Conversion DateTime, Estimated Conversion Value, Customer Name, UTM Campaign, Referral Code, Term Length, Start Date, Annual Usage, Customer Type.
Whatever sits in utm_campaign at the moment of conversion is what lands in your reports. Partners use it two ways: some pass campaign details directly, others pass a unique ID and match it back to the source in their own systems. Either works.

​
Compare with the API

The Storefront is the recommended path for most partners. If the energy experience has to live natively inside a product you already maintain, see the Plan Data API instead, or compare the two side by side.