Basics concepts of Regrows inventory calculations
Overview
Inventory module in Measure API is used to calculate on field emissions factors for a measured crop.
Regrow’s Measure API utilizes the DNDC model, a scientifically validated framework for analyzing soil dynamics. This model evaluates nutrient cycling and variations in soil carbon levels to predict greenhouse gas (GHG) outcomes that arise from changes in agricultural practices. The Measure API is structured into different modules to cater to a variety of client needs.
The Inventory module calculates an absolute value of the emissions for a given time period (and associated with growing a crop) on a field. Inventory is relevant for companies looking to understand their emissions impact. In these cases, customers are not quantifying carbon credits for verification or measuring a practice change, but rather measuring progress towards sustainability or net-0 goals.
The Measure API takes in your field location and field management data (crop info, tilling events, fertilizer data, etc.). The API combines your data with field-level weather, soil info, etc. Field management data includes a recent history of events, we recommend a minimum of 3 years history but more ideally 5 years of history, as well as the reporting period for which your GHG inventory is measured.
Today, outcomes are not calculated according to a specified carbon protocol in order to generate scope-specific assets.
Quick Q&A
|
Question |
Short Answer |
|
What do the Inventory Module Outcomes tell me? |
The absolute net greenhouse‑gas (GHG) emissions and removals that occurred while producing a single crop during your reporting period. |
|
What unit should I report? |
Use the crop‑level emission factor (EF) – tonnes CO₂e per bushel (or per your chosen yield unit). |
|
Is this a credit or offset? |
No. Inventory outcomes provide a footprint, not a credit. Credits come from the Intervention Module, which compares practice changes to a counterfactual. |
|
Where is uncertainty applied? |
v0: Uncertainty is applied at the project level (called crop_level in the API). Regrow uses a Monte Carlo simulation to apply structural model uncertainty across all fields and crops. Then the final crop_level emission factors reflect the 50th percentile of that simulation. field_level values are not uncertainty adjusted. v1: (to be released in Q4, 2025): Both the project (crop_level) and per field values are post uncertainty. |
|
How should I use your calculations? |
crop_level object: For final emissions reporting. field_level object: For field and grower incentives, and tracking. |
What outputs to expect
Measure API Inventory will model SOC, CH4, N20 (direct and indirect).
All outcomes are presented today both as as raw emissions and converted to emission factors in tonnes CO2e/yield unit.
In Measure API the Inventory module returns two nested sections in a single response:
|
Output section |
How is this used? |
Uncertainty |
Outcomes details |
|
crop_level |
This is your overall project emissions. Used for corporate Scope 3, product footprint |
Yes, 50th percentile |
Outcomes are the sum of emissions factors (emissions/yield) for each crop |
|
field_level |
Internal field level benchmarking, grower payment |
v0: No, pre uncertainty v1 (anticipated Q4, 2025 release): Yes. |
Raw emissions and emissions factors (emissions/yield) per field. |