Agriculture · updated October 2026

Crop science lab software

Crop science lab software is the set of digital tools agricultural research labs use to track samples, record experiments, manage field-trial data, run crop models and analyse results — typically a LIMS or electronic lab notebook plus modelling and statistics packages.

Also known as: agricultural LIMS, plant science laboratory software, agronomy lab software

A crop science lab handles seeds, tissue, soil and DNA samples alongside field-trial plots, weather records and model simulations. No single product covers all of that, so “crop science lab software” describes a stack: a laboratory information management system (LIMS) or electronic lab notebook (ELN) for samples and protocols, trial-management software for plots, crop simulation models for scenario testing, and statistical software for analysis.

This entry explains each layer, names established tools — with figures from their official documentation — and sets out how to connect them so data flows from sample to publication without retyping.

Key figures

45+

Crops modelled in DSSAT

Source: DSSAT official site

$0

Entry price for APSIM, DSSAT, STICS and FAO AquaCrop for research use

Source: Official model sites

4 of 5

Crop simulation tools in our ranking that are open or free for research

Source: Statfield ranking

Annual fee

APSIM commercial Special Use Licence

Source: APSIM licensing

Layer 1: samples and protocols

A LIMS tracks each physical sample — where it came from, which plot and genotype, what tests were run, where it is stored — using barcodes and chain-of-custody records. An ELN replaces paper notebooks for protocols and observations. Labs running high-throughput assays, such as genotyping or soil analysis, gain most from a LIMS; smaller research groups often start with an ELN.

Key requirements in crop science are linking samples to field-plot identifiers, handling plant-specific metadata such as growth stage, and exporting to analysis tools.

Layer 2: field-trial data

Field trials generate plot layouts, treatments and repeated measurements. Open tools include Breedbase, developed at the Boyce Thompson Institute, and the Field Book app for recording phenotypes on Android tablets. Commercial agronomy platforms such as Syngenta Cropwise combine farm-level data with trial and advisory features.

Layer 3: crop simulation models

Crop models translate plant physiology into equations that project growth and yield under given weather, soil and management. DSSAT models more than 45 crops and is distributed as open-source software. APSIM is free for public-good research and education and requires an annual Special Use Licence for commercial use. INRAE's STICS and FAO's AquaCrop, which focuses on water-limited yield, are free.

Labs use models to design experiments, test management scenarios before planting, and extend trial results to other sites and seasons.

Layer 4: statistics and analysis

Trial analysis relies on mixed models that account for blocks, sites and years. R with packages such as lme4, SAS, and the commercial ASReml are common choices; see our entry on statistical software for crop improvement.

Data standards and FAIR principles

Research funders increasingly expect data to be FAIR: findable, accessible, interoperable and reusable. In crop science this means using persistent identifiers for germplasm and trials, standard trait definitions from resources such as Crop Ontology, and metadata standards like MIAPPE — Minimum Information About a Plant Phenotyping Experiment — so others can understand and reuse datasets. Choosing software that supports these standards from the start avoids painful clean-up when data must be deposited in a public repository at the end of a project. It also makes collaboration across institutions simpler, because partners can merge datasets without renaming every trait and plot.

Calibrating and validating crop models

A crop model is only as good as its calibration. Before using DSSAT, APSIM, STICS or AquaCrop to answer a question, collect local data on phenology, biomass and yield for the cultivars of interest, and adjust cultivar parameters until the model reproduces those observations. Then validate against an independent dataset — a different season or site — and report error statistics such as root mean square error. Uncalibrated models can produce precise-looking numbers that are badly wrong. Publishing calibration data and parameter files alongside results lets others check and reuse the work.

Budget and sustainability

Open tools reduce licence costs but not total cost: someone must install, maintain and train users on them. Commercial LIMS and ELN products bring vendor support and validation documentation, which matters for regulated testing labs. Whatever the mix, budget for data management staff time, backups and long-term storage, and avoid systems that only one person in the lab understands.

Weather and soil inputs

Models and trial analyses depend on accurate daily weather and soil profiles. Record weather on site where possible, document gaps and any gridded data used to fill them, and store soil descriptions in the formats each model expects.

Choosing the first tool to adopt

Labs that try to digitise everything at once usually stall. Start where errors currently cost the most. If samples are frequently mislabelled or lost, begin with barcoding and a sample tracking system. If field data is retyped from paper, begin with tablet-based data capture. If analysis takes weeks because data arrives in inconsistent spreadsheets, begin by standardising trait names and templates. Once one layer works reliably, connect the next, using the shared identifiers agreed at the start.

Involve the people who will use the tools daily — technicians, field staff and students — in testing. Their adoption determines whether the data ends up complete.

Document every workflow in a short standard operating procedure, so new team members and visiting researchers record data the same way from their first day.

Key terms

LIMS: laboratory information management system. ELN: electronic lab notebook. Phenotype: an observable trait of a plant. Calibration: adjusting model parameters to match observations. Validation: testing a calibrated model against independent data. MIAPPE: a metadata standard for plant phenotyping experiments.

How this glossary entry was compiled

Every number on this page links to the organisation that published it: an independent research firm, an official product or pricing page, a public filing, or official documentation. We do not publish our own estimates as facts, and where a figure is reported by the company it describes, it is labelled company-reported. Prices are taken from official vendor pages and change often, so open the linked source before relying on one. If a widely repeated figure could not be traced to a primary source, we left it out. Entries are reviewed when the underlying sources publish new editions, and the update date at the top of the page shows the latest review.

Examples

University agronomy group

Uses an ELN for protocols, Field Book for plot data, R for analysis and DSSAT to extrapolate nitrogen-trial results to drier seasons.

Seed company lab

Runs a LIMS for genotyping samples linked to a breeding database, with automated export to the statistics team.

Irrigation research station

Calibrates FAO AquaCrop against measured yields to test deficit-irrigation strategies.

How to build a crop science lab data stack

Design around identifiers first and tools second.

  1. 1
    Define identifiers. Agree unique IDs for trials, plots, genotypes and samples used by every system.
  2. 2
    Choose the sample system. LIMS for high throughput, ELN for smaller groups.
  3. 3
    Standardise field capture. Use tablets with predefined traits and units instead of paper.
  4. 4
    Select a crop model. Match the model to your crop and question; check licence terms for commercial work.
  5. 5
    Calibrate before trusting. Fit model parameters against your own measured data.
  6. 6
    Automate exports. Script transfers into your statistics environment to avoid manual copying.

Frequently asked questions

Is DSSAT free?

Yes. DSSAT is distributed as open-source software and models more than 45 crops.

Can APSIM be used commercially?

Yes, under an annual Special Use Licence; research and education use is free.

Do small labs need a LIMS?

Not always. An ELN plus consistent identifiers can serve a small group well.

Sources

Related on Statfield

All glossary terms