Part of the LIMS software guide
LIMS software · Buyer's guide

Choosing LIMS software: criteria, specification and budget.

Choosing LIMS software starts with one question: do you produce the analyses, or do you receive them? A useful opinion on LIMS software is built on a repeatable evaluation method, not on a vendor ranking.

In brief

  • Start from the scope, not the catalogue. A laboratory LIMS revolves around the sample; a LIMS on the manufacturer's side revolves around the report received, the standard and the compliance status.
  • Eight criteria structure the decision: scope, supplier and product data, report extraction, regulatory standards, traceability, integration with the information system, hosting, support.
  • A specification is written in five blocks, with expected outcomes rather than feature names.
  • A budget is compared by cost model, against market benchmarks to be confirmed in writing, never on an entry price.
  • An evaluation is played out on your own reports, on a costed data migration and on the total cost over three years.

1. Functional scope: the criterion that governs all the others

A laboratory LIMS (Laboratory Information Management System) is organised around one central object: the sample. It tracks a sampling, a method, a result, an instrument, an operator. A LIMS on the manufacturer's side is organised around another object: the test report received. It tracks a parameter, a value, a threshold, a standard, a compliance status.

The distinction determines what your teams will be able to do day to day, and what an auditor will come looking for. In searches, “LIMS software” often refers to both families without distinguishing them, which explains some disappointing demos. The page LIMS: definition and uses details this distinction.

Two questions to settle the scope

  1. Who produces the data?Suppliers or a commissioned laboratory: make use of the reports received. Internal laboratory: perform the analyses and track the samples
  2. What must remain?A compliance status per parameter, product and supplier, or a result per sample linked to a method
  3. Your LIMS familyLIMS on the manufacturer's side centred on the report received, or laboratory LIMS centred on the sample

Two questions are enough to know which family of tools to compare.

What Tracklab covers, and what it does not

Tracklab is LIMS software built for the manufacturer who receives analyses, not for the laboratory that produces them. The platform gathers reports from suppliers, contract laboratories and the internal laboratory, extracts the results, calculates their compliance status against regulations and your own thresholds, and keeps a trace of each calculation. It does not register samples or drive instruments. The approval or acceptance decision stays with your teams: the tool calculates and traces.

List your needs beyond the calculation (analysis planning, batch tracking, deviation handling) and have their coverage checked in a demo, on your own reports.

2. Supplier and product data: master data, not a shared folder

A document management tool stores files. Master data answers a more demanding question: which analysis applies to which product, from which supplier, on what date?

  • Supplier identification. Does it distinguish the legal entity, the production site and the contact?
  • Product linking. Is a report linked to a product, a supplier, a family? What happens when a supplier changes a reference?
  • The origin of the analysis. Does the tool distinguish analyses sent by suppliers from analyses you commission?
  • Duplicates. How does the tool handle two records created for the same supplier by two sites?
  • Updates. Who feeds what: the supplier, purchasing, quality?

The decisive test comes down to one request: show me the analyses of a supplier delivering two sites with two ranges, and what each team sees.

3. Report extraction: measure the output, not the promise

Automatic extraction has become a common selling point. What distinguishes two offers is the quality of the output and the ability to check it again.

  • Six questions to ask in a demo
  • Which types of reports are processed, and which fields are extracted (parameter, value, unit, LOQ, LOD, uncertainty, method)?
  • Is the result measured on your reports, or on a demo data set?
  • How are scanned PDFs, long pesticide tables and multi-language reports handled?
  • Is the same parameter written differently by two laboratories recognised as one?
  • Are “not detected” results kept, or only quantified values?
  • Does each extracted value link back to the source document, and who can correct a value?

Useful extraction is extraction you can check again. If a value does not link back to the report it comes from, it will not stand up at audit.

4. Regulatory standards: which requirements, maintained by whom

Software does not replace your reading of the regulations: it makes it executable. You still need to know which regulations it holds, and who keeps them up to date. Four European regulations set most of the numerical thresholds used in the food industry:

RegulationAreaVersion built into Tracklab
Regulation (EC) No 396/2005Maximum residue levels of pesticides18 October 2026 (EU pesticides database export)
Regulation (EU) 2023/915Contaminants19 August 2026
Regulation (EU) No 10/2011Plastic materials in contact with food14 July 2026
Regulation (EC) No 2073/2005Microbiological criteria1 July 2026

For traceability, three regulations frame the exercise: Regulation (EC) No 178/2002, Article 18 (identify your suppliers and customers), Regulation (EC) No 852/2004, Article 5 (HACCP procedures and records), and Regulation (EU) 2017/625 on official controls. On top of these come the private standards your customers expect (IFS Food, BRCGS, FSSC 22000) and your own requirements: internal policy, customer specifications, material specifications.

Governance questions

  • Are regulations supplied and updated by the vendor, or do you have to enter them?
  • Can you create your own standards, with several threshold levels (warning, blocking)?
  • Is a threshold set once for a product family, or product by product?
  • When a threshold changes, do past calculations keep the threshold of the time?
  • What does the tool do when it cannot conclude: does it display “compliant” by default, or flag it?

5. Traceability and auditability: what the auditor will come looking for

A compliance status without a history is a status that cannot be verified. Traceability is judged on four traces:

  • who uploaded or changed a report or a status, and when;
  • which threshold, from which regulation and in which version, was used for each calculation;
  • what the laboratory's conclusion was, next to the calculated status;
  • which actions followed a deviation: re-analysis, request to the supplier.

Ask for a history that cannot be altered, can be exported and is readable without the vendor's help. Also ask to see a supplier's analyses as they were assessed six months earlier: that is the typical audit situation.

6. Integration with the information system

A stand-alone tool creates one more data entry. Before discussing APIs, clarify the scopes: LIMS, QMS and ERP do not cover the same things, and the page on the difference between LIMS, ERP and QMS details this split.

  • Supplier and item master data: does the ERP remain the source of codes?
  • Direction and frequency of exchanges: one-off import, daily sync, on-demand call?
  • Ownership of the integration: who configures it, who maintains it?
  • Reversibility: can data and reports be exported in a usable format, without paid intervention?

7. Hosting model: cloud, dedicated or on-premises

For a manufacturer, hosting is less a technical question than a contractual one.

  • Location and processing. A provider processing data on your behalf acts as a processor within the meaning of Article 28 of Regulation (EU) 2016/679: the contract governs instructions, confidentiality, the use of other processors and the return of data. Article 32 sets out the expected security measures.
  • External accounts. A portal open to suppliers requires strict access management.
  • Continuity. Backups, recovery plan, exit procedure: get them specified in writing.
  • Retention. Retention period for reports and histories.

8. Support: the hidden cost of configuration

The difference between a tool that is used and a tool that is abandoned rarely comes down to features. It comes down to the initial configuration.

  • Who sets up the first standards and thresholds: you, the vendor, an integrator? With how much of your teams' time?
  • What existing data is migrated: suppliers, products, historical reports, thresholds already kept in a spreadsheet?
  • What training: by role, with reusable material?
  • Which contact: a named lead, a response time?

At Tracklab, setup is done with your real reports and thresholds, starting with the regulatory standards to activate and two or three internal rules. The price of the Tracklab offer is not given on this page: it is built around your volume of analyses.

Building a LIMS specification: the five-block template

A specification is a decision document: it must allow two offers to be compared on the same ground, and allow a vendor to say no.

  • LIMS specification template
  • Block 1 · Context, scope and teams. Business, sites, number of suppliers and products, reports received per month, laboratories, quality, purchasing, laboratory and IT teams, decision-maker and timeline.
  • Block 2 · Priority processes and use cases. Three to five real cases described step by step (pesticide report, check against a customer specification, supplier review, audit response): input, expected processing, output, exception.
  • Block 3 · Data, analyses and requirements. Analysis families, parameters to extract, regulations to apply, internal standards, status rules (what “compliant” means, what to do when the tool cannot conclude), retention.
  • Block 4 · Non-functional requirements. Hosting, security, access, history, exports, availability, reversibility, report languages, access for external suppliers.
  • Block 5 · Comparison and decision criteria. Weighting, knock-out criteria, mandatory response format, documents to provide (demo on your reports, migration plan, timeline).
Three costly mistakes

Writing a list of features with no expected outcome: every offer will answer “yes”. Forgetting data migration: the initial quote almost never covers it. Not setting knock-out criteria: the comparison ends up on price.

LIMS software budget: four cost models

The price of LIMS software does not exist as a single figure: it depends on the billing model, the number of seats, the scope and data migration. Rather than a market average, compare quotes on the same grid.

Cost modelWhat you payWhat to get specified
Perpetual licenceRight of use and annual maintenanceMaintenance rate, upgrades included, cost of test environments
SaaS subscriptionPeriodic fee, hosting and updates includedWhat is included and what is charged separately
Cost per userUnit price per seatDefinition of the billed seat: named account, read-only user, supplier account
Implementation and data migrationConfiguration, migration, training, testingVolume of data migrated, number of days, acceptance testing

What the total cost must include over three years

Add up the licence or subscription, implementation, maintenance and your teams' internal time. On the manufacturer's side, add an often forgotten line: what you currently pay laboratories for compliance assessment against your standards, when they offer it, and the time spent re-keying reports.

Method

Compare two offers in five steps.

A repeatable method to work through before signing: each step narrows the list of relevant offers.

  1. Define use cases and volumes

    Suppliers, products, reports received per month, laboratories, people involved by role. Without volumes, no demo is comparable.

  2. Weight the criteria and set knock-out criteria

    For example: no history of the thresholds applied, no export, regulatory standards you have to enter yourself. Before the demos.

  3. Have it demonstrated on your reports

    Around twenty real anonymised reports: pesticides, microbiology, contaminants, a scan, a foreign language. Note what is extracted, calculated, and what remains “to be determined”.

  4. Check the implementation, not just the interface

    Dated migration plan, contractual commitments: go-live lead time, availability, reversibility.

  5. Decide on total cost and reversibility

    Compare offers over three years, with an identical scope. The LIMS software page describes what the Tracklab module covers.

Free white paper · 10 pagesLaboratory analysis compliance: from reading the report to audit evidence

The situation, the calculation of re-keying time and a four-step demonstration of the Laboratory analyses module.

Frequently asked questions

Choosing a LIMS: your questions.

How does an evaluation of LIMS software work?

It starts with a written framing of use cases and volumes, then a demo on your reports, then a costing of data migration. The demo is only worth something if you know beforehand what you are going to score.

What criteria should be used to compare two LIMS offers?

The scope actually covered, the quality of extraction on your reports, the standards supplied and how they are updated, traceability of the thresholds applied, integration with the information system, hosting, support and the total cost over three years.

How is existing data migrated?

It is prepared before signing: inventory of sources (spreadsheets, shared folders, ERP), thresholds already kept, volumes, duplicates. Ask for a migration plan with a post-import check and a written acceptance criterion.

How do you choose LIMS software when you are not a testing laboratory?

By going back to the nature of the data: if your analyses arrive as reports produced by your suppliers or by commissioned laboratories, what you need is a LIMS on the manufacturer's side, which calculates the compliance of those results with your standards, not a sample-centred LIMS.

How long does it take to deploy a tool of this kind?

It depends on the scope: a start limited to a few analysis families and the built-in regulations is quicker than a project including history migration and ERP integration. Ask for a dated timeline, with each party's responsibilities.

Laboratory analyses module · demo on your data

Try it on your own reports.

Bring a few real reports: together we will look at what is extracted, what is calculated and what remains to be determined.

Our clients

Reliable supplier data, managed with Tracklab.

Their quality and purchasing teams collect, control and leverage their supplier data with Tracklab.

150+

companies supported

40,000+

suppliers referenced

90,000+

products and ingredients

Customer testimonial · Bouvard
“Tracklab has eliminated the blind spots that existed in our document monitoring. Every document is analysed, every change is detected and every decision is traceable. This has enabled us to take a real step forward in terms of professionalism and credibility, particularly with auditors and customers.”
EVEllen V.Quality Director, Bouvard Pro
CyberVadis
CyberVadis Excellence rating

Independent assessment of our cybersecurity framework and of the protection of the data entrusted to Tracklab.

They use Tracklab

  • Somapro
  • Jean Niel
  • La Fournée Dorée
  • Nautilus
  • Cérélia
  • Will&Co
  • Neta
  • Diffusions Aromatiques