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.
Documents, sensory check, test reports, decision, record: the method to organise incoming inspection and make it readable at audit, batch by batch.
Incoming inspection is the check, at the time of delivery, that the raw material received matches the order, the requirements defined by the manufacturer and the documents accompanying the batch - before it enters stock or production. This page describes a method for organising it, documenting it and making it readable at audit: what is checked, in what order, on which documents, and how the acceptance decision is taken and kept. It is aimed at food manufacturers who receive raw materials and must decide on their acceptance based on their own requirements and the supplier's documents, not at the testing laboratory, which carries out the tests.
Incoming inspection checks that a delivery matches the order and the written requirements, in terms of its condition, its documents and, if the plan provides for it, its analyses; it stops at the acceptance decision, which rests with the manufacturer.
The useful scope is described by what the manufacturer must be able to justify to an auditor or a customer:
In many plants, raw material incoming inspection is described in a single procedure but carried out by two different functions: purchasing physically receives, quality decides. This split works on one condition: the decision rule is written down and known to both. Goods-in quality inspection, in the everyday sense, refers to the sensory and physical part of this system. It is a subset of it, not a synonym.
No European regulation requires a form called “incoming inspection”. The obligations it rests on are found elsewhere, and they are enough to frame the method.
References consulted on 12 November 2026: Regulation (EC) No 852/2004 and Regulation (EC) No 178/2002.
The five steps below assume a prerequisite: a standard that defines, for each raw material and each supplier, the expected documents, the checks to carry out and the acceptance thresholds. Without this standard, goods-in comes down to a series of improvised judgements. Building this standard is described on our quality control plan page.
Before unloading, check that the batch comes with what is expected: delivery note, current version of the technical data sheet, batch test report or certificate of analysis, valid certification certificate, declaration of compliance where applicable. Three points are checked systematically: the match between the delivery note and the order, the exact product reference (a technical sheet bearing a similar reference is not the right sheet), and the link between the documents and the batch delivered. An expired document, or one that cannot be linked to the batch, is a documentary non-conformity, not an administrative detail: it is precisely what the auditor will test first.
It is carried out on a sample taken according to a written rule, not on “whatever is visible” when a pallet is opened. Criteria are limited to what can be observed at the dock: appearance, colour, odour, texture, homogeneity, presence of foreign bodies, net weight, condition of labelling, cleanliness of packaging. Two requirements make the check reproducible: written criteria (with a rating scale rather than a simple “compliant / non-compliant”) and numerical tolerances per material, for weight, appearance and temperature. Sampling itself follows the rules on our sampling plan page.
A report is not read like an attachment: it is compared. First check that it covers the batch delivered (product, reference, batch number, sampling date, issue date, laboratory). Then check that the expected parameters are covered, with a method and limit of quantification compatible with the thresholds to compare against. A perfectly readable report that says nothing about a critical parameter does not allow a conclusion - it opens a request for further information, not an acceptance. The next section details this matching.
Four outcomes should be planned in advance, with their standard reason: acceptance, conditional acceptance (for example pending receipt of a missing document, with use blocked in the meantime), hold or quarantine (missing result, doubt over batch identity), rejection. The acceptance decision belongs to the quality teams; purchasing bears the commercial consequence and the laboratory provides the analytical reading. This responsibility must be written down in black and white in the procedure, with the title of the function that decides and the rule applicable in its absence.
The goods receipt record must allow someone who was not there to reconstruct the decision: date and time, supplier, product and reference, batch number, quantity, attached documents, checks carried out and results, decision and reason, name and function of the decision-maker, any concession, physical destination of the batch (stock, quarantine, return). A record that does not link the decision to the batch is unusable at audit.
Each expected document must be associated with a decision, otherwise it piles up with no effect.
| Document | What it establishes | Checkpoints at goods-in | Associated decision |
|---|---|---|---|
| Delivery note and accompanying documents | The identity of the delivery: supplier, product, reference, quantity, batch, date | Match with the order; legibility of the batch number; quantity announced | Acceptance of the physical delivery; in the event of a discrepancy, transport or supplier dispute |
| Product technical data sheet | Declared composition, allergens, characteristics and conditions of use | Current version and date; reference identical to the one purchased; allergens consistent with the product file | Documentary acceptance; outdated version = block or request for update within a written deadline, according to your procedure |
| Batch test report or certificate of analysis | The results obtained on the sample taken from the batch delivered | Batch identity, parameters covered, method, limit of quantification, unit, date, laboratory | Acceptance, hold or rejection depending on comparison with internal requirements |
| Certification certificate (IFS Food, BRCGS, ISO 22000, GlobalG.A.P.) | The level of control of the supplier's system - not the quality of the batch delivered | Validity date at delivery, scope (site, product family), issuing body | Continued approval; expiry passed = rule written in your procedure (example: approval suspended until the certificate is renewed) |
| Declaration of compliance (food contact materials, sector regulations) | The declared regulatory compliance of the material or product | Material reference, regulations covered, date, signatory | Documentary acceptance; missing = block on the packaging concerned |
| Specific attestations (origin, non-GMO, allergen-free, customer requirement) | A particular requirement of a customer or market | Exact scope of the attestation; batch or period covered | Acceptance conditional on the attestation; otherwise written concession or rejection |
| Supplier questionnaire and approval file | The supplier's ability to meet requirements, at the time of approval | Completeness, attachments, date of last review | Supplier approval status: approved, conditionally approved, suspended |
This table settles two common confusions. A certification certificate covers a site and a range, not today's delivery: it governs supplier approval, not batch acceptance. And a declaration of compliance is read with the material number in hand, otherwise it proves nothing about what is delivered.
Matching is a mechanical operation, provided it is written down. It takes five points.
| Checkpoint | Question to settle | Common mistake |
|---|---|---|
| Batch identity | Does the report cover the batch delivered? | Accepting a generic report or one valid for a period |
| Parameters covered | Are all required parameters present? | Treating a missing parameter as a compliant result |
| Method and limit of quantification | Is the limit below the threshold? | Comparing a result with a threshold it technically cannot measure |
| Unit and basis of expression | Are both values on the same basis? | Comparing mg/kg with ppm “by eye”, or dry basis with as-is |
| Version of the regulatory threshold | Is the threshold the one in force on the date of analysis? | Comparing with a residue or contaminant limit that has since changed |
| Measurement uncertainty | Is the result close to the threshold? | Deciding on a borderline result without taking uncertainty into account |
On these last two points, two readers of the same report can reach two different statuses if the comparison rule is not written down. This is what Tracklab's test report compliance calculation does: the platform extracts the results from the report, including “not detected”, compares them with your thresholds and the four European regulations it builds in and keeps up to date, and calculates a status per parameter. Each status keeps a trace of the threshold, regulation, its version and its date; the laboratory's conclusion remains displayed alongside. Tracklab calculates and traces: the acceptance decision remains that of the quality teams.
Tracklab gathers reports from your suppliers and laboratories and calculates, parameter by parameter, their compliance status against your requirements and the regulations. Discover Tracklab's LIMS software, built for the manufacturer who receives analyses.
Only four statuses, and five points to check before concluding. A parameter missing from the report was not analysed: it is not a compliant result.
A non-conformity is a deviation found between what is delivered and what is required. A concession is the decision, taken knowingly, to use the material nonetheless - within a defined scope and under defined conditions. The two must be distinguished, because they do not involve the same people or lead to the same follow-up.
| Situation | Who decides | What must be traced | Follow-up |
|---|---|---|---|
| Non-conformity on a critical requirement | Quality management | Reason, quantity concerned, destination of the batch | Rejection or return; supplier complaint; review of supplier approval |
| Deviation on a non-critical requirement | Quality with purchasing | Internal concession: scope, quantity, duration, conditions of use | Closer monitoring on subsequent deliveries |
| Missing or expired document | Goods-in quality | Documentary block and request to the supplier | Block lifted on receipt of the expected document |
| Result to be determined or parameter not covered | Quality with the laboratory | Request for further information and deadline | Re-analysis or rejection depending on production urgency |
| Deviation affecting a customer's contractual requirement | Quality, with the customer's written agreement | Customer agreement, date, scope | Conditional use; customer informed in the batch file |
Three rules stop concessions becoming a habit: they are named and dated, they specify the quantity and batch concerned, and they are counted. The number of concessions per supplier is one of the clearest signals for revising a supplier approval or increasing a check frequency. An untraced concession amounts, in the event of a customer complaint, to an unjustified acceptance. The medium for recording it is detailed on our non-conformity report page.
The auditor is not looking for a bulky file: they take a delivered batch and follow the thread back. What they must be able to find without help:
Tracklab collects test reports and certificates of analysis, calculates the compliance status of each parameter against your regulatory and internal standards, records the re-analysis and the request to the supplier on the report, and keeps every status change with its reason. Tracklab calculates and traces; it does not decide on the acceptance of a delivery.
For details of the points to check on a supplier certificate, see our article on the certificate of analysis.
Incoming inspection rests on three written decisions: which documents and which checks for which material and which supplier, which comparison rule for test reports, and who decides on acceptance. Without them, goods-in produces records with no weight. Three actions let you move forward without heavy reorganisation: rework the requirements grid material by material, check that each expected document does trigger a decision, and test reconstructing a batch delivered six months ago. It is this test, more than the length of the procedure, that will tell you whether the system is readable.
To see the compliance calculation applied to your own test reports, book a meeting with the Tracklab team.
Each step builds on the previous one: the acceptance decision is only taken once the documents, the dock check and the reports have been checked.
Delivery note, technical sheet, batch report, certificates: present, current, linked to the batch.
Appearance, odour, foreign bodies, net weight, labelling, according to a written sampling rule.
Batch identity, parameters covered, method and limit of quantification.
Acceptance, conditional, hold or rejection, with its reason.
Enough to reconstruct the decision without having been there: batch, checks, decision, decision-maker.
No regulation requires a document with this name. However, Regulation (EC) No 852/2004 (Annex II, Chapter IX) prohibits accepting a raw material that the operator knows or may reasonably expect to be contaminated, and its Article 5 requires permanent procedures based on HACCP principles, with associated records. Regulation (EC) No 178/2002 (Article 17) places responsibility for compliance on the operator. Audit standards and customer specifications, for their part, require documented checks. In practice, incoming inspection is therefore expected everywhere, in varying formats.
The decision belongs to the quality teams, based on the checks carried out and the supplier's documents. Purchasing receives the goods, manages the supplier relationship and bears the commercial consequence of a rejection; the laboratory provides the analytical reading. What must be written down is the rule: who decides, on what criteria, and who decides in case of absence or urgency. A decision taken by default, for lack of a rule, is an untraceable decision.
It depends on what the manufacturer has defined as a requirement for the material and the supplier, and on what its own customers require: there is no universal rule. What is constant is the reading rule: if a test report or certificate of analysis is required, it must cover the batch delivered and the expected parameters, with a limit of quantification compatible with the thresholds. Failing that, there are only two options: a request for further information, or an acceptance decision taken knowingly and traced on another basis.
Yes, provided the concession is a decision, not a workaround. It requires a written reason, a limited scope (batch, quantity, duration), the agreement of the authorised function, and the customer's written agreement when a contractual requirement is involved. The concession must also be followed up: repeated concessions for the same supplier feed into the supplier approval review and justify stepping up checks.
Treat it as “to be determined”, never as compliant. Three outcomes: ask the supplier or the laboratory that produced the report for further information, have a re-analysis carried out on the batch on hold, or reject the delivery if the parameter is critical and the urgency is incompatible with waiting. In all cases, the decision and its reason are recorded with the batch, otherwise the absence of a result becomes, at audit, an absence of control.
Tracklab calculates the compliance status of each parameter in your test reports and certificates of analysis, and keeps a trace of the threshold applied. It does not decide on the acceptance of a delivery.
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