Real data. Real decisions. Real results.

Klappir is built for organisations whose operational footprint spans multiple sites, subsidiaries and source systems. The platform is in active use across shipping, retail, building materials, brewing and construction — from a global fleet of 16 vessels to 100-plus retail locations to 14 store networks to a 100-year-old brewery to an 8-subsidiary construction group. The common thread is data complexity, not a specific industry.

Each subsidiary, site, vessel or business unit feeds data into a single shared structure. Records are attributed to the right entity, period and scope so group-level figures are built from the same foundation as local ones. Hagar runs all GHG accounting for 10 businesses and 100-plus locations through the platform. Eimskip consolidates across 21 subsidiaries in 20 countries. ÞG Verk does the same across 8 group companies.

Yes. Every record carries its full lineage — source system, site or asset, period, methodology, emission factor — so audit trails are produced continuously rather than assembled at year-end. Hagar received limited assurance on its 2024 GHG figures, energy data and workforce metrics on the basis of data held in Klappir. Husasmiðjan, Ölgerðin and Eimskip rely on the same foundation for their externally verified ESG statements.

The structured data foundation supports the frameworks customers actually have to file under — GHG Protocol Scope 1, 2 and 3, CSRD, EU ETS, FuelEU Maritime, CII for shipping, EPDs for building materials, and country-specific reporting in Iceland, the Faroe Islands and the Netherlands. The same governed records feed multiple regulatory outputs, so adding a new framework doesn’t mean rebuilding the data.

The value compounds. Once the foundation is in place, scope expands and precision improves year over year without rebuilding. Hagar moved 75% of procurement emissions to weight-based methodology in 2024, up from 53% in 2023. Eimskip recalculated marine fuel emissions from CO₂ to CO₂e back to 2015 and added Scope 3 Category 3 for the first time — both on the same data layer. Methodology improvements don’t require rebuilding the data; they require a foundation built to evolve.