Electricity Prices in Spain: OMIE, REE, and the Wattora App

Spain has one of Europe's most volatile electricity markets. Prices can swing from negative (yes, paid to consume) at sunny noon to 300 EUR/MWh in evening peaks - sometimes both on the same day. Two organisations sit at the centre of this: OMIE, which runs the day-ahead auction, and REE (Red Electrica de Espana), which operates the grid. Understanding both is the first step to taking advantage of the PVPC variable tariff.

This guide explains how the Spanish electricity market works in practice, why volatility is so high compared to neighbouring countries, and how the Wattora app surfaces OMIE prices in a usable form for households on the PVPC tariff.

OMIE: the day-ahead auction that sets your bill

OMIE (Operador del Mercado Iberico de Energia) runs the Iberian electricity market - Spain plus Portugal share the same trading platform, known as MIBEL. Every day at 12:00 Madrid time, OMIE clears the auction for the next 24 hours. Generators submit selling bids, retailers submit buying bids, and the market clears hour by hour at the price where supply meets demand.

The result: 24 hourly prices published around 13:00 local time, applicable from midnight the following day. These are wholesale prices in EUR/MWh. For consumers on the PVPC (Precio Voluntario para el Pequeno Consumidor) tariff, your bill is calculated using these wholesale prices plus grid charges plus VAT - making your retail price effectively a tracking function of OMIE.

Where it gets interesting: PVPC users in Spain see directly the volatility of the wholesale market. A cloudy still day where wind and solar can't cover demand means gas-fired generators set the marginal price, and prices spike. A sunny Sunday with low industrial demand can push midday prices into negative territory - meaning generators pay the grid to take their output rather than curtail.

The Spanish government has periodically intervened with the "Iberian exception" - a cap on gas prices for electricity generation - but the underlying structure remains volatile.

REE and why Spain's volatility is structural

Red Electrica de Espana is the system operator. Its job is to keep frequency at 50 Hz and ensure supply meets demand instant by instant. REE publishes real-time generation mix data, demand forecasts, and CO2 intensity - all openly available via API.

Spain's renewables share is one of the highest in Europe: wind and solar combined regularly cover 50-70% of demand on favourable days. This is good for prices when renewables are running, but creates a structural problem: when renewables drop (cloudy still days), gas plants become marginal and prices spike. Other countries with more nuclear (France) or hydro storage (Norway) absorb these dips at lower cost.

Three structural reasons Spain has more volatility than France or Germany:

1. High renewable penetration without enough storage. Battery storage is growing but still a fraction of what's needed. Pumped hydro exists but is geographically limited.

2. Low nuclear share, declining. Spain has 7 nuclear reactors, all scheduled for phase-out between 2027 and 2035. Less baseload means more price spikes when renewables underperform.

3. PVPC exposure passes wholesale volatility directly to consumers. About 40% of Spanish households are on PVPC. In other countries, retail tariffs absorb wholesale spikes; in Spain, you see them on your bill.

This combination - high renewables, low storage, declining nuclear, direct wholesale exposure - is why a Wattora-style app makes more difference in Spain than almost anywhere else. Knowing which hour to run the dishwasher can shift 20-30% of your monthly bill.

Quick comparison

Common pitfalls and how to avoid them

Across every domain this article touches, the same shape of mistake recurs. Practitioners new to the field overweight the most visible piece of the system — the screenshot, the paywall, the exam question, the headline price — and underweight the underlying constraint that actually determines outcomes.

The five most common failure modes:

1. Optimising for the demo, not the durability. A working demo in a controlled environment proves nothing about reliability under real conditions. In iOS development, an in-app purchase flow that works in the Xcode Simulator says nothing about how it behaves in App Store sandbox with network latency and Ask to Buy approvals. In an exam, a 100% score on an untimed quiz tells you nothing about whether you can do 49/50 in 45 minutes with no second guesses. Build for the hardest realistic case from the start.
2. Skipping the first-principles documentation. Every system has a canonical specification. App Review Guidelines for iOS, the official EU regulations for tax deductibility, the CITB question bank for CSCS, the OMIE market rules for Spanish electricity. Reading them takes a few hours but saves weeks of wrong-direction work. Secondary sources (blogs, tutorials, this article included) are useful as orientation but never authoritative.
3. Ignoring the rate limit. Every external system has rate limits — explicit (APNs silent push throttling, RevenueCat API quotas, exam retake fees) or implicit (App Review patience, customer attention spans, your own working memory). Plan around them. A workflow that requires more rate-limited operations than the system allows will fail in production, not on day one but during the first stress event.
4. Underweighting localisation and regional variation. What is true for Germany is not always true for Italy. What is true for English-speaking users is not always true for Japanese ones. What is true for the UK CSCS test is not always true for the Irish equivalent. Always check the local rule before applying a general one.
5. Treating the documentation as static. Apple updates App Review Guidelines. The Bundeslaender change Schonzeiten. OMIE adjusts market clearing algorithms. Set up a periodic review (quarterly is enough for most things) and re-read the canonical sources. Workflows that worked perfectly a year ago can be silently broken today.

None of these are dramatic. The dramatic mistakes (catastrophic bugs, audit findings, exam failures) are the visible tip of a longer-running iceberg of small misses. Catching the small misses is what separates routine outcomes from problematic ones.

Key takeaways

• OMIE — Day-ahead auction. Publishes 24 hourly prices for next day.
• REE — Grid operator. Generation mix, demand, CO2 intensity API.
• PVPC tariff — Variable retail. Bill tracks OMIE wholesale price.
• Wattora — Consumer app. Hourly prices, charts, notifications.

The pattern that runs through every section above: start with the constraint, not the wishlist. In an exam, the constraint is the question bank and the pass mark. In an electricity market, it is the auction clearing rule. In a tax workflow, it is the receipt-retention requirement. In a code architecture, it is the platform's design decision (StoreKit's transaction lifecycle, App Review's guideline, APNs's authentication model). Get the constraint right and the rest follows.

The opposite failure mode — designing for an aesthetic ideal, then trying to retro-fit the constraint — is the most common cause of wasted work in every domain covered here. A beautiful paywall that hangs in sandbox is rejected at App Review. A polished freelancer expense report that lacks receipts is disallowed by the tax office. A study plan that ignores the actual question distribution leaves the candidate stuck below the pass mark.

The practical recommendation: read the official rules of whatever system you are operating in, extract the binding constraints, and treat them as inputs to the design — not afterthoughts. Every section of this article is the application of that principle to a specific domain.

FAQ

What time of day is electricity cheapest in Spain?
Typically 03:00-05:00 (low demand, base nuclear and wind running) and 13:00-16:00 in sunny months (solar peak). Avoid 19:00-22:00 (evening peak, solar gone, demand high).

Is the PVPC tariff cheaper than a fixed-price tariff?
On average over a year, PVPC has been slightly cheaper than fixed tariffs since 2014 - but with much higher month-to-month variance. If you can shift consumption, PVPC wins. If you can't, a fixed tariff is more predictable.

How does Wattora get OMIE prices?
From the official OMIE API, refreshed daily after 13:00 Madrid time when the next-day prices are published.

Is Wattora available outside Spain?
Yes - Wattora supports Spain, Italy, Germany, France, the Netherlands and Belgium, each with the relevant local wholesale market data.

Further reading and references

The references below cover the official sources for the rules cited in this article. Where applicable, they include the canonical documentation, regulatory text, or vendor-provided guides. For each one, prefer the official source over secondary commentary — secondary sources go stale fast and frequently misquote the binding rule.

• Official documentation of the system in question (linked from each app or service's own help centre).
• Apple Developer Documentation for any iOS/macOS reference — the WWDC session videos and the corresponding Human Interface Guidelines pages are the authoritative source.
• For EU regulatory questions (taxation, data protection, energy market structure), consult the relevant national authority — most publish their guidance in English.
• For Spain and Italy energy market data, OMIE and GME both publish full historical price series in CSV format from their public websites — no API key required.
• For UK CSCS prep, the CITB publishes the official question bank book each year — buy a current copy if you want the authoritative source.

If you find a contradiction between this article and an official source, the official source wins. Article rules of thumb are summaries — they have edge cases, exceptions, and regional variations that the source documents specify exactly.