Octopus Energy Data Integration Specialists

Most sites benefit from daily extracts at off-peak times (e.g. 02:00 UTC) to avoid throttling during business hours. Billing events should be captured as they occur via webhook, with a nightly fallback poll to catch any missed notifications. The right cadence depends on your portfolio size and API quota; we work with you to find the balance between freshness and rate-limit risk.

Yes, if your customer records in the ecommerce or ERP system include site codes or account references that match the Octopus Energy supply numbers. iWeb designs the join keys and enriches the energy fact tables with customer and order dimensions so you can analyse energy spend per customer segment, product line or geography alongside revenue metrics.

We implement slowly-changing dimension (SCD Type 2) logic for tariff and rate tables, capturing the effective date of each change. This allows cost calculations to use the correct rates for each consumption period. When Octopus publishes a new tariff, it flows through the API and is automatically versioned in the warehouse.

The extract pipeline includes a nightly reconciliation check that polls the Octopus API for any billing events that were not captured via webhook. If gaps are found, they are flagged for investigation and backfilled. iWeb configures these fallback polls and maintains an audit log of all missed and recovered events.

We build a reconciliation fact table that joins invoiced amounts (from Octopus billing data) against calculated consumption cost (from metered usage and tariff rates). Any variance greater than a configurable threshold is flagged for manual review. This catches backdated adjustments, estimated reads and billing corrections before month-end close.

Yes. With historical consumption data warehoused, you can build trend models using consumption volume, seasonal patterns and tariff forecasts. iWeb populates the base data and helps you set up the forecast columns; your data science or finance team owns the model logic and refresh frequency.

Key checks include: meter readings are non-negative and monotonic (consumption cannot decrease unless there is a meter replacement), daily consumption totals stay within expected ranges for each site, billing records match the number of meters and supply accounts, and extract timing (freshness of the most recent consumption read) stays within your SLA. iWeb configures these checks as part of the pipeline.

Each meter is extracted separately with its own supply number, consumption readings and costs. For sites with multiple meters, you must define allocation rules in the warehouse (e.g. by square footage, headcount or production volume). iWeb builds the dimension table that tracks meter-to-site mappings; your operations or finance team defines the allocation logic.

iWeb extracts the data into the warehouse where it can be modelled and validated, then exports cost summaries or detailed files to your ERP system or finance tool (SAP, NetSuite, Sage, etc.) for reconciliation. The warehouse acts as the trusted intermediate, so both systems have a common reconciliation baseline.

iWeb instruments the pipeline with timestamps, record counts, and comparison checks (e.g. consumption volume vs. prior week). Alerts notify your data team if an extract fails, if consumption data is older than expected, or if reconciliation variance exceeds thresholds. A status dashboard shows the run history and latest metrics.

Octopus Energy requires API key (Bearer token) authentication. iWeb manages the secure storage of keys in your orchestration platform, rotates them regularly and ensures they are never logged or exposed in error messages. Multi-account setups require separate API keys per account.

A basic pipeline (daily consumption extract, cost fact table, simple reconciliation checks) typically takes 4-6 weeks to design, test and deploy. More complex estates with many meters, multiple tariffs or deep ERP integration may take 8-12 weeks. iWeb provides a detailed timeline and scope document after discovery.

The Octopus Energy API typically exposes only 24-36 months of data. For older history, you must request a manual export from the Octopus portal or contact their support team. iWeb helps you acquire and load these extracts into the warehouse as a one-time historical load.