You’ve done your research, had the conversations, and you’re ready to move forward. But before you sign – or right after you do – you probably have some very practical questions: How does the technology actually connect? How do we integrate with your existing systems? How long before your first customers can go live? We hear these questions a lot. And we think you deserve clear, honest answers. In this post, we’ll explain how Podero integration and onboarding work in practice.

Below, we’ve compiled the most common questions we get from new partners at this stage, covering everything from device connectivity and data security to savings calculations and go-live timelines.

1. How do we connect to the devices?

Podero connects to your customers’ devices entirely via cloud-to-cloud integration, no hardware, no installer visits required. We connect via the device manufacturer’s cloud API (we maintain direct partnership agreements with major OEMs, including Bosch, and others), which means Podero communicates with the device through the manufacturer’s existing cloud infrastructure.

Your end-customers connect their own device through your branded onboarding UI (white-label Connect UI). The exact flow depends on the device manufacturer: in most cases, customers simply log in with their existing device account and Podero receives access automatically.

Once connected, Podero can monitor, steer, and optimize the device in real time. For a full list of supported device types (heat pumps, EVs, EV chargers, solar inverters), see our compatibility list or the Partner API documentation.

2. Why cloud, not hardware?

Podero is built on a cloud-cloud interoperability model, and intentionally so. Here’s why this matters for you:

• No physical rollout. Hardware-based approaches require logistics, installation, and field support at scale. Cloud integrations have none of that friction.
• Faster go-live. With no hardware to ship or install, onboarding a new customer takes minutes, not weeks.
• Easier maintenance. API-based integrations are updated centrally. When a manufacturer updates their system, we handle it: not you, not your field team.
• Mass adoption. Hardware dependencies are the single biggest barrier to scaling device flexibility programmes. Cloud removes that barrier entirely.

The trade-off (slightly more latency versus a direct local connection) is well within acceptable margins for the energy optimisation use cases we support.

3. Where do we store the login data?

Podero takes data security and GDPR compliance seriously. Here’s where and how data is stored:

• Infrastructure: The Podero platform is hosted on Google Cloud EMEA (primary data centre in St. Ghislain, Belgium), with backups in the EU region.
• Login credentials: End-user device credentials (e.g. manufacturer login data) are handled securely via OAuth or encrypted token flows. Podero does not store plain-text passwords.
• Security standards: Podero has implemented CIS IG1 and is actively working towards ISO 27001 certification. Annual penetration tests by independent third parties are conducted; results are available on request.
• Sub-processors: The main sub-processors are Google Cloud EMEA (hosting), Smartcar (vehicle data), and Sentry (error tracking). A full Data Processing Agreement (DPA) is available.
• Trust Center: You can review Podero’s compliance status in real time at trust.podero.com.

4. Do we have access to all device functionalities?

Podero’s access to device functionality depends on what the device manufacturer exposes via their API. In general:

• What Podero can do: Monitor device state (e.g. charge level, temperature, power consumption), send steering signals (e.g. start/stop charging, adjust heat pump setpoints), and retrieve historical usage data.
• What Podero cannot do: Access functionality the OEM has not made available in their API (e.g. certain advanced settings or diagnostics that remain locked to the manufacturer’s own app).
• User preferences: End-users retain control over their comfort settings (e.g. minimum charge levels, comfort temperatures). Podero optimises within those boundaries, never overriding them.

For the specific capabilities available per device type, the API Reference lists all attributes and states accessible for heat pumps, EVs, EV chargers, and solar inverters.

5. How do we integrate with the customer? What systems do we need to connect to, initially and for full rollout?

The integration is modular, you can start light and deepen over time.

Phase 1. Minimum to go live:

• Partner API: A server-to-server OAuth2 connection to the Podero Partner API. This enables user creation, building/device management, and data retrieval. You can start with this alone using the Podero web app (no deeper integration needed on your side).
• Onboarding UI: Embed or link to the white-label Connect UI so your customers can onboard their devices.

Phase 2. For a full, scaled rollout:

• CRM / User management system: Pass user data (customer IDs, energy contract details) into Podero via the API to enable personalised optimisation.
• Billing system / ERP: Integrate with Podero’s savings data endpoints to retrieve per-customer savings for billing (especially relevant for fixed-price tariff customers).
• Trading system: Connect your trading desk to Podero’s load forecasts to execute Day-Ahead and Intraday trades on behalf of the optimised fleet.
• App / Customer portal: Expose Podero data (savings, device status, steering history) directly in your own customer-facing app via our API.

Podero provides an implementation roadmap and runs a kick-off workshop with your team to scope these integrations in detail. Typical go-live for Phase 1 is 8 weeks.

6. How do we calculate savings?

Savings are calculated by comparing what a device would have consumed (unoptimized baseline) with what it actually consumed under Podero’s optimization:

Savings (€) = (Unoptimized consumption × spot prices) − (Optimized consumption × spot prices)

Savings (%) = Savings (€) ÷ Unoptimized consumption cost

For heat pumps, the unoptimised baseline is estimated using a standard residential load profile (with morning/evening peaks), scaled to the device’s actual total consumption. For batteries, savings come from Day-Ahead and Intraday market arbitrage. For EVs, savings are calculated per full charge cycle.

Savings data is accessible:

• Per customer: via the Podero Console / dashboard, filtered by device and time period
• Per fleet: aggregated daily view for utilities
• Via API: GET endpoints to pull savings per user/device for billing or reporting purposes
• Via CSV export: available as a workaround for fixed-price billing workflows

Podero guarantees a minimum saving per device per year — so your customers always walk away better off. The guaranteed minimums are €120/year for batteries, ~€50/year for EVs (€1 per full charge, excluding hybrid vehicles), and €50/year for heat pumps. In practice, observed savings are typically higher. Here you can read more about the €200 guaranteed in savings.

7. How long does it take to go live?

The implementation typically takes 8 weeks, running two parallel workstreams: a business track and a technical track.

In week 1, you and Podero run a kick-off workshop to map the customer journey and define the implementation roadmap. Weeks 2 and 3 are spent developing your messaging and legal framework (T&Cs and privacy policy), while on the technical side the API integration and onboarding UI are built. Weeks 4 and 5 focus on designing and developing the checkout process, with optional billing and savings API integration running in parallel. Weeks 6 and 7 are dedicated to planning the marketing campaign and final testing. By week 8, you’re ready to go live.

Podero runs a weekly business check-in and ad-hoc technical syncs throughout. You don’t need to have all optional integrations (trading, ERP, billing) complete before go-live: you can start with the minimum and build from there.

8. What Podero data can we show in our app?

Via the Partner API, you can pull the following data into your own customer app or portal:

• Device status: current state, connectivity, last steering action
• Energy data: real-time and historical consumption/production curves per device
• Savings: optimised vs. unoptimised cost, savings in € and %, over any specified period
• Steering history: when and how Podero steered each device
• User preferences: current comfort settings (e.g. minimum charge, temperature setpoints)
• Buildings: device groupings per metering point

For a full data model, see the API Reference covering heat pumps, EVs, solar inverters, buildings, and energy contracts. And here you can find more information regarding myPodero app.

9. How should we communicate savings to our customers?

Scaling a device flex proposition is as much a communications challenge as a technical one: customers need to understand and trust what’s happening with their device.

Best practices:

• Lead with the annual number, not the monthly equivalent. “Save €120/year” lands much better than “save €10/month”.
• Use the guaranteed minimum as your anchor. It builds trust. Example: “Minimum guaranteed €120/year for your battery, or we make up the difference.”
• Keep it simple for end-users. Avoid market jargon (Day-Ahead, intraday, balancing). Focus on: “Your device saves you money automatically. Here’s how much you saved this month.”
• Show the number in your app. Savings visibility in the customer portal is one of the strongest drivers of continued engagement and retention.
• Segment your communication. Early adopters want detail; mainstream customers want the headline number and reassurance. Use your CRM to tailor.

Podero provides messaging best practices and communication playbooks as part of the onboarding process.

10. How do we explain the proposition to our customers?

The simplest frame that works across device types:

“Your [heat pump / EV / battery] is connected to the energy market. It charges or runs when electricity is cheapest, automatically, within your comfort settings. You save money. We handle everything.”

Key proof points to include:

• Up to €200/year savings (varies by device; always cite with the guaranteed minimum)
• No changes to your comfort, the device stays within your preferred settings at all times
• No extra hardware, connects via your existing device app
• Powered by your energy provider, reinforces trust and brand ownership

For your sales team and marketing materials, Podero provides a full proposition toolkit including key messages, objection handling, and segment-specific copy.

11. What T&Cs should users sign when onboarding their device?

When onboarding end-users, two sets of legal documents typically need to be in place:

1. Your own B2C terms (drafted by you, reviewed with Podero input):

• Terms of Service for the smart steering / flexibility product
• Privacy policy covering Podero’s data access and processing
• Any specific consent language required for device control

2. Podero’s standard documents (provided by Podero):

• Data Processing Agreement (DPA): Governs how Podero processes personal data on your behalf, required under GDPR.
• Terms of Service / Nutzungsrichtlinien: Available from Podero upon request.
• SLA (Service Level Agreement): Defines uptime, support response times, and escalation paths.

Podero supports the legal setup as part of the implementation (Business Work Package 3: B2C Legal Framework). Typically 2 weeks to complete with your legal team.

All documents are available via the Podero API, or by contacting your Podero account manager.