Part of the LIMS software guide
LIMS software · Feature

Test report compliance: a calculated status per parameter, MRLs and internal thresholds.

Tracklab extracts the results from your test reports, compares them with pesticide MRLs, the other built-in European limits and your own thresholds, then calculates a traceable, auditable compliance status per parameter.

In brief: what to remember about this feature

  • What it does: extracts the results from a report, compares them with the built-in European regulations and your internal standards, and calculates a status per parameter and per standard.
  • What it adds: an explicit status, never “compliant” by default, with the reason when it cannot be determined.
  • What it traces: the threshold, regulation, version and date applied to each calculation, with a readable history even when a threshold changes.
  • What it does not do: produce the analysis, give an opinion in place of the laboratory, or decide in place of your quality teams.
  • For whom: quality, laboratory and purchasing teams at food manufacturers who receive reports from their suppliers or from commissioned laboratories.

What does test report compliance calculation actually do?

The feature takes a document received, a report from a supplier or a commissioned laboratory, and turns it into usable quality information. Three operations follow one another: extracting the results, comparing them with the applicable limits, calculating the status.

For each parameter, the platform identifies the result and links it to the product concerned, the applicable regulatory limit and, where relevant, your internal threshold. The status is then calculated and displayed next to the laboratory's conclusion, which is neither hidden nor rewritten.

The feature doesThe feature does not
Extract the results from the report and structure themProduce the analysis or stand in for the laboratory
Match each result with the applicable limit and thresholdDecide in place of the quality teams
Calculate a status per parameter and per standardAssign a default status for lack of information
Keep the threshold, regulation, version and date appliedRewrite or hide the laboratory's conclusion
Feed a searchable, traceable and auditable historyManage stock or production
“From the time products as listed in Annex I are placed on the market as food or feed, or fed to animals, they shall not contain any pesticide residue exceeding: (a) the MRLs for those products set out in Annexes II and III; (b) 0,01 mg/kg for those products for which no specific MRL is set out in Annexes II or III […]”Regulation (EC) No 396/2005, Article 18(1) · EUR-Lex
Key takeaway

Tracklab calculates and traces compliance; validation remains the responsibility of the quality teams. To see where the feature fits in the module as a whole, see the page on LIMS software for the food industry.

How is a test report read and extracted automatically?

Extraction is automatic: results are read and then structured with no re-keying. The process runs in four steps.

From report received to calculated status

  1. ReceiptDedicated email address, supplier portal or direct upload; linked to the supplier and product
  2. ExtractionParameter, value, unit, method, LOQ and LOD, in French, English, German, Turkish or Chinese
  3. RecognitionEach parameter recognised whatever its label; “not detected” is kept
  4. CalculationStatus per parameter and per standard, next to the laboratory's conclusion

The calculated status does not replace the laboratory's conclusion: both readings stay visible side by side.

For quality, the compliance of a report becomes structured data, comparable from one supplier and one laboratory to the next. For purchasing, handling a report no longer depends on the one person who knows a given laboratory's format.

Which European regulations are built in, and how are they kept up to date?

Four European regulations are built in and kept up to date by Tracklab's teams: you have no regulatory limits to enter. Each calculation keeps the version applied.

Built-in regulationSubjectVersion built in
Regulation (EC) No 396/2005Maximum residue levels of pesticides in or on food18/10/2026 (EU pesticides database export, including Regulations 2026/2289 and 2026/2299)
Regulation (EU) 2023/915Maximum levels for contaminants (repeals Regulation (EC) No 1881/2006)19/08/2026
Regulation (EC) No 2073/2005Microbiological criteria for foodstuffs01/07/2026
Regulation (EU) No 10/2011Plastic materials in contact with food14/07/2026

The maximum residue level (MRL) is the highest legally permitted level of a pesticide residue in or on a food. It is the first level of comparison: a result above the pesticide MRL does not call for the same reading as a result above your internal threshold.

Regulatory scope

Updates cover the four regulations listed above. National regulations, non-EU texts and your private specifications fall under your internal standards.

How to set your warning and blocking thresholds by product family

European regulations are not enough to express your quality policy. Your internal standards are added to the calculation: in-house policy, customer specifications. Several standards apply in parallel to the same report, with a separate status for each.

Each threshold has two levels, a warning threshold and a blocking threshold, defined per product family, per rule or per product. The same substance can thus be monitored more strictly on a range intended for a demanding customer.

LevelSet byRole in the calculation
Regulatory limitBuilt-in European regulation, maintained by TracklabLegal reference for comparison
Warning thresholdYou, per family, rule or productTriggers an alert
Blocking thresholdYou, per family, rule or productFlags that your requirement has been exceeded
  1. Start from product risk. Configure the parameters actually present in your reports, not every possible one.
  2. Turn the customer specification into thresholds. A commitment stricter than the regulation must become a threshold, otherwise it is not checked.
  3. Choose the granularity. Product family for broad rules, individual product when the stakes justify it.
  4. Document who sets the threshold and why. The value of the configuration depends on the justification available at audit.

A threshold set too high lets a drift through; set too low, it floods teams with alerts that lead nowhere.

How to read the four calculated compliance statuses

Each parameter, for each applicable standard, receives one of the following four statuses. A report is never declared compliant by default.

StatusMeaningExpected action
CompliantThe result meets the applicable thresholdNone; the calculation and its trace remain available
AlertThe warning threshold is reached, without reaching the blocking thresholdMonitor the supplier trend, inform purchasing
Non-compliantThe blocking threshold or the regulatory limit is exceededDocumented quality handling, decision by the competent teams
To be determinedNo status can be calculated; the reason is displayedCheck the standard, the product link or the report

The “to be determined” status is the most useful one to watch. It appears when no limit is available for the parameter/product pair, when an internal threshold is missing or when the extracted result cannot be used. Once the cause is fixed, the status is recalculated.

The calculated status is displayed next to the laboratory's conclusion. The laboratory describes what it measured against its own references; the platform matches that result with your requirements. The two readings complement each other.

A “compliant” status is the result of a documented comparison, not a decision to accept a batch or a supplier.

Want to see the calculation on one of your reports? Book a meeting with the Tracklab team.

What to do after an “alert” or “non-compliant” status?

Three actions are available today, traced in the same place as the deviation:

  • change the status with a stated reason: the original conclusion and the change are time-stamped;
  • request a re-analysis;
  • send a request to the supplier.

How to find the threshold, regulation and version applied to an older calculation?

Each calculation keeps four elements, available in the history:

  • the threshold applied, with its value and origin (regulatory limit, warning threshold or blocking threshold);
  • the reference regulation, identified by its number;
  • the version of the standard used at the time of calculation;
  • the date of calculation.

An internal threshold changes, a customer tightens its specification, a regulatory limit is revised: earlier calculations remain readable with the configuration that produced them. A report handled in March is read with the March threshold.

This is what makes the status traceable and auditable: in a quality review, a supplier meeting or an audit, the question “on what basis was this status calculated?” has a documented answer.

How to prepare an IFS, BRCGS or FSSC 22000 audit with traceable statuses

IFS Food, BRCGS Food Safety and FSSC 22000 require documented control of suppliers and analyses, with results recorded and assessed by competent staff. The calculated status feeds this file; it does not replace risk assessment or the decision of the quality teams.

  • Before the audit
  • Map the product/standard pairs: does each product concerned have a documented internal standard?
  • Handle “to be determined” statuses first: they flag a missing rule, exactly what an auditor picks up.
  • Document deviations: for each “alert” or “non-compliant” status, keep the decision taken and its reason.
  • Prepare the history extract for the audited period: the threshold, regulation and version applied answer questions on method.
  • Keep the report and the laboratory's conclusion: the calculated status is added to them, it does not replace them.

To go further, the guide how to choose LIMS software details the specification and the comparison criteria, and the quality control plan page explains how to organise your analyses upstream.

Are you a food manufacturer wanting to try it on your own reports? Request free access: access is granted on request, after a conversation with our team.

To go further: our article “Your test reports are not an archive” and the feature launch press release.

Before / after

From report received to traced status.

What changes in the day-to-day handling of a test report, without changing the role of the laboratory or of your quality teams.

Without a tool

The report remains a PDF

With Tracklab

The report becomes data

  1. Without a tool: Results re-keyed by hand into a spreadsheet

    With Tracklab: Automatic extraction, all laboratories and all languages

  2. Without a tool: Threshold copied with no source or version

    With Tracklab: Status calculated with threshold, regulation, version and date

  3. Without a tool: Laboratory conclusion taken as a decision

    With Tracklab: Laboratory conclusion kept, decision left to your teams

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

Compliance calculation: your questions.

Does the feature replace the laboratory information system?

No. It is aimed at the manufacturer who receives a report, not at the laboratory that produces the analysis. The laboratory's conclusion remains visible next to the calculated status.

Can a report be marked compliant without a complete calculation?

No. When no limit is available, an internal threshold is missing or the result cannot be used, the status is “to be determined” and the reason is displayed.

Can I apply a threshold stricter than the pesticide MRL?

Yes. Your internal standards are configured per product family, per rule or per product, with a warning threshold and a blocking threshold.

What happens to a status if I change a threshold six months later?

The history remains readable: each calculation keeps the threshold, regulation, version and date applied, so an older status can be justified with the rule in force at the time.

Which report languages are supported?

French, English, German, Turkish and Chinese, whether the report comes from a supplier or a commissioned laboratory. Each parameter is recognised whatever its label.

Laboratory analyses module · demo on your data

See the calculation on your reports?

Bring three real reports: we run the compliance calculation against your requirements during the call.

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