Indiquez vos coordonnées pour télécharger le document.
Le fichier s’ouvre dans Google Drive : vous pouvez le télécharger ou l’imprimer.
The LIMS produces and archives a measurement, the QMS holds the rules and deviations, the ERP tracks flows. This page is written for food manufacturers who receive analysis results, not for the laboratory that produces them.
| Laboratory LIMS | QMS | ERP | |
|---|---|---|---|
| Scope | The sample and its result, from sampling to issuing the report | Quality processes: document control, deviations, actions, audits, reviews | Physical and financial flows: orders, goods receipts, stock, prices, invoicing |
| Data covered | Samples, methods, measured values, instruments, reports issued | Procedures and versions, quality records, non-conformities, action plans | Items and suppliers, orders, goods receipts, stock, costs |
| Main teams | Laboratory, laboratory quality | Quality, process owners, management | Purchasing, supply, finance, IT |
| Question answered | What value was measured, by what method, on which sample? | Which rules apply, what deviation, what action? | What quantities, what stock, what costs? |
| What it does not do | Collect reports issued by third parties, hold contractual thresholds per customer | Hold the measurement, compare parameter by parameter | Read a report, compare a value with a threshold |
This table describes what each category of tool is designed for. In practice, scopes shift: an ERP opens quality fields, a LIMS adds specification screens, a QMS absorbs monitoring tables. It is the areas of overlap that determine the quality of your monitoring.
A LIMS is laboratory management software: it records an analysis request, applies the planned method, collects and calculates the result, tracks the instrument, issues the report and keeps the records. Its classic scope ends at the laboratory door. For a full definition, see the page LIMS: definition and uses.
Behind the phrase “LIMS software”, reality varies widely from one vendor to another: some cover only the bench and report issuing, others add metrology, consumables or analysis planning. A comparison is therefore always made function by function.
Two frameworks explain the rigour expected of these tools: the ISO/IEC 17025:2017 standard for the competence of accredited laboratories and, in the pharmaceutical sector, the US 21 CFR Part 11 and Annex 11 of the EU good manufacturing practice guidelines for electronic records. These texts concern the production of the measurement: they say nothing about your customer threshold.
There is, however, LIMS software designed for the manufacturer's side, which starts from the analyses received rather than from samples. This is the approach of Tracklab's LIMS software.
A QMS is first of all an organisational system: the set of rules a company sets itself to maintain the quality of its products. In projects, “QMS” refers to the software that hosts it: document control, non-conformities, corrective actions, internal audits, reviews.
Two standards shape its content: ISO 9001 for quality management and ISO 22000 for food safety. The retailers' private standards (IFS Food, BRCGS) rely on the same documentary building blocks.
What the QMS does not do: it does not hold the measured value, does not keep the analysis method and does not compare a result with a threshold parameter by parameter. The LIMS/QMS difference shows up in a single object: the deviation. The LIMS provides the value and its context; the QMS holds the analysis of the deviation, the decision and the action.
An ERP links a company's functions around a single master data set: items, suppliers, orders, goods receipts, stock, prices, invoicing. This is where the physical arrival of goods is recorded and where a receipt block is decided.
The “LIMS or ERP” question often comes up when an IT manager wants to avoid adding yet another tool. The answer lies in the nature of the data: an ERP does not read a report, does not keep the method and does not hold a threshold per parameter. It tells you a pallet arrived on 4 March; it does not tell you what the attached analysis contained.
Overlaps arise because the same object (a supplier, a result, a deviation) is described by several systems. Each area of overlap creates a risk of double entry and diverging statuses.
A result outside the threshold becomes a non-conformity. The LIMS holds the value, the method and the sampling date; the QMS holds the handling rule, the decision and the action. The working rule that holds up: a single system decides the status of the deviation, the other records it, with an explicit cross-reference between the two.
The ERP knows what came in; the LIMS knows what was measured. The junction point is the supplier/product pair. If the two do not use the same code, a result gets linked to the wrong item.
The ERP holds the administrative supplier record; the QMS holds its quality status. A classic discrepancy: a supplier active in the ERP while its assessment has expired in the QMS.
Whatever the combination of tools, the test report reaches you as a document: a PDF attached to an email, a file uploaded to a portal, often in the laboratory's language. None of the three systems reads this document to extract the parameter, value, unit and limit of quantification. This shared blind spot explains why hand-kept spreadsheets persist. The page on the integrated QMS, LIMS and PIM platform describes how information flows between systems.
The report received has no natural home in conventional tools: the LIMS on the manufacturer's side makes it shared data.
A report contains, in very varied forms: the issuing laboratory and its accreditation, the sample reference, the sampling date, the method, one or more parameters, the measured value with its unit, sometimes the uncertainty, and the laboratory's conclusion against its own references. It is issued by a third party, in a format that changes from one issuer to another.
That same document then has to feed four destinations: the QMS if the value becomes a deviation, the ERP at goods receipt, purchasing for the supplier review, the product file for the audit. Without a structured point of entry, it is handled four times.
No European regulation requires a LIMS, a QMS or an ERP. What the framework requires concerns results, their traceability and records.
| Regulation | What it sets | What you must be able to show |
|---|---|---|
| Regulation (EC) No 178/2002, Art. 17 and 18 | Operators' responsibility, one step back and one step forward traceability | The supplier and product reference behind each result |
| Regulation (EC) No 852/2004, Art. 5 | Procedures based on HACCP principles, records kept | Monitoring records |
| Regulation (EC) No 396/2005 | Maximum residue levels of pesticides | The MRL applicable to the food and the substance |
| Regulation (EC) No 2073/2005 | Microbiological criteria | The criterion applicable to your product family |
| Regulation (EU) 2023/915 | Maximum levels for contaminants, replacing Regulation (EC) No 1881/2006 | Limits per contaminant and per food category |
| Regulation (EU) No 10/2011 | Plastic materials in contact with food | Packaging migration results |
| Regulation (EU) 2017/625, Art. 34 and 37 | Methods for official controls, official laboratories accredited to EN ISO/IEC 17025 | The method used and the laboratory's status |
Two precautions apply throughout. First, the applicable version matters: the annexes are amended regularly. In Tracklab, the four regulations with numerical thresholds are built in and maintained in their latest consolidated version: 396/2005 (EU pesticides database export of 18 October 2026), 2023/915 (19 August 2026), 10/2011 (14 July 2026) and 2073/2005 (1 July 2026). Second, the regulatory limit is not the contractual threshold: a customer can require better than the regulation, never less.
If you perform no analyses on site, you do not need a laboratory LIMS. You do, however, always need to compare what you receive with what you require, and that function does not disappear with the laboratory.
An ERP cannot play the role of a LIMS: it holds no method, no report and no threshold per parameter. A LIMS cannot play the role of an ERP: it manages no stock, valuation or invoicing. The two coexist.
What cannot be missing is a place where the supplier and product reference, the threshold with its source, the measured value and the original document come together. Depending on your organisation, that place is a spreadsheet or LIMS software on the manufacturer's side.
Tracklab is LIMS software built for the manufacturer who receives analyses, not for the laboratory that produces them. The platform:
Tracklab calculates and traces; accepting a material, opening a deviation or reviewing a supplier remain decisions for your quality, purchasing and laboratory teams. The platform replaces neither the ERP nor the QMS: it supplies them with structured data. See the LIMS software page for details of the module.
Before comparing tools, rank your needs. The five criteria are handled in this order: each one narrows the list of relevant solutions. The guide to choosing LIMS software then details the specification template.
Count, over a year, the analyses performed in-house and the reports received from third parties. If most arrive from outside, a laboratory LIMS covers only a minority of your volume: the issue is collection and compliance calculation. Warning sign: a tracking spreadsheet kept by a single person.
List the formats and languages you receive: native PDFs, scans, tables, reports in English or German. The decisive criterion is the ability to extract parameter, value, unit and LOQ while keeping the original document attached. Warning sign: manual re-keying between the PDF and the spreadsheet.
Distinguish three families: regulatory thresholds, contractual thresholds per customer, internal thresholds. To check: who maintains the regulatory thresholds, how to set an internal threshold on a product family, and whether two levels (warning, blocking) are possible. Warning sign: a threshold copied from one file to another, with no reference or date.
What you must show at an IFS Food or BRCGS audit is a history: which parameter, which threshold, which version, which value, on what date, on which document. Warning sign: a status recalculated without keeping the threshold applied at the time.
Look at the existing supplier and product master data, the connection to the ERP, authentication and data migration. Ask a simple question: who administers the thresholds day to day? If the answer is “IT, at every change”, the setup will not last.
| Situation | Usually in place | What is most often missing |
|---|---|---|
| Site with an internal laboratory | Laboratory LIMS, QMS, ERP | Compliance calculation of reports received from third parties against customer thresholds |
| Site without a laboratory | QMS, ERP | A history per supplier and per parameter, across several campaigns |
| Multi-site group | Several ERPs, a group QMS | Consistent thresholds across sites, applied to all reports received |
What changes when the analyses received have a structured point of entry between the laboratory, the QMS and the ERP.
Without a point of entry: Re-keyed into the QMS when the value becomes a deviation
With a LIMS on the manufacturer's side: Extracted once, linked to the supplier and product
Without a point of entry: Searched for at goods receipt in the ERP
With a LIMS on the manufacturer's side: Status calculated with threshold, regulation, version and date
Without a point of entry: Found by hand for the supplier review and the audit
With a LIMS on the manufacturer's side: Structured data supplied to the QMS and the ERP
The situation, the calculation of re-keying time and a four-step demonstration of the Laboratory analyses module.
A laboratory LIMS manages the sample and the result: method, instrument, measured value, report. An ERP manages the company's flows: orders, goods receipts, stock, valuation. The LIMS/ERP difference lies in the nature of the data: a measurement on one side, a movement and a quantity on the other. Neither calculates by default the compliance of a received result with a contractual threshold.
No, and the reverse is also true. A LIMS can flag an exceedance for the analyses it holds, but holds neither procedures, deviation handling nor audits. A QMS does not keep the measurement or the method. The two complement each other, with a clear rule: only one decides the status of the deviation.
Not a laboratory LIMS. A manufacturer receiving all its results from outside has to gather heterogeneous reports, link them to its suppliers and products, calculate their compliance with its thresholds and keep the history. That is the role of a LIMS on the manufacturer's side.
Where the document stays linked to its extracted data, its supplier, its product and the threshold applied. A shared folder keeps files but not that link. The question to ask of every solution: in two years, can we find the value, the threshold, its version and the document for a given parameter?
No. An ERP records the arrival of a material; it does not read the attached report and does not check its values against a threshold. It remains useful for blocking a receipt, but the compliance status must be calculated and traced elsewhere, with the source document.
Show us three reports from your suppliers: together we will look at what your current tools do with them, and what the compliance calculation adds.
0.02 mg/kgCompliant0.09 mg/kgAlert0.015 mg/kgNon-compliantAbsent /25 gTo be determinedIllustration, fictitious data.
Their quality and purchasing teams collect, control and leverage their supplier data with Tracklab.
companies supported
suppliers referenced
products and ingredients
“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.”

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







Platform
Resources