Sealway
Food industry · quality alert

Batch withdrawal: prove the alert sent to the distributor.

A batch has to be withdrawn from the market. Six months later, in an audit, a dispute or an investigation, can you produce the exact message sent to the distributor, the documents that came with it and the time it left? With Sealway in BCC of the alert email, the message, its attachments and the recipients shown are received as it is sent and timestamped. Sealway does not prove that the distributor read the alert, nor that the procedure was compliant.

Built for

  • Quality and food safety managers
  • Manufacturers and processors
  • Wholesalers, importers, logistics platforms
  • Distributors and retail chains
  • Legal and insurance departments
  • HACCP consultants

The problem: proving which alert was transmitted to the distributor, and when.

A manufacturer learns, from a laboratory result, that a batch already distributed may be contaminated. It identifies the batch number, the products concerned and the distributors that received it, then emails them asking for an immediate hold, a withdrawal and information on the quantities left.

The withdrawal is done, the recall published if needed, the crisis passes. Then comes the certification audit, the complaint of a distributor who denies having been warned in time, or the investigation after a report. It is no longer a matter of whether you reacted, but of what you wrote, to whom, with which attachments, and at what time. An email found in the “Sent” folder answers it poorly: it can be disputed, and so can the date it shows.

Regulation (EC) No 178/2002 requires operators to initiate withdrawal immediately, to inform the authorities and to pass the necessary information along the chain. It does not say through which channel. When email is that channel, Sealway makes it possible to keep evidence of it: the message received as it is sent, its attachments and the recipients shown, bound to a qualified electronic timestamp.

The alert procedure first; the email evidence second.

Sealway replaces neither the withdrawal or recall procedure, nor the notification of the competent authorities, nor the information of consumers. It documents the email when email is the channel used to warn direct customers. Faced with a non-compliance:

  • apply your alert management procedure and, in France, the official guide to the management of food alerts;
  • inform the competent authorities as provided, and publish the recall (in France on RappelConso) when the product may have reached consumers;
  • warn your direct customers, with Sealway in BCC of each alert email;
  • ask for an explicit confirmation of receipt and implementation: Sealway does not establish it.

The procedure requires, the email alerts, Sealway dates.

The alert procedure defines who warns whom, about what and with which documents; it is what auditors and authorities examine. Email is most often its vehicle towards distributors: fast, written, with the useful attachments. Its weakness is evidential: nothing in a mailbox prevents a message from being re-edited or its date from being disputed.

Sealway adds this layer: a copy of the message received by a third party as it is sent, timestamped by a qualified provider, with each attachment given its own fingerprint. What you transmitted no longer depends on your word alone.

Alert procedure: withdrawal, authorities, recall Alert email to the distributor: content and attachments Sealway: date and integrity of the message received

Sealway complements the procedure; it does not trigger it, does not validate it and warns nobody on your behalf.

What Regulation (EC) No 178/2002 requires, and what the guides organise.

The regulation lays down the obligations of traceability, withdrawal, information and cooperation. The French guide to food alert management and the Commission’s guidance say how the information circulates. None of these texts prescribes email; all of them assume you can show what was transmitted.

Regulation (EC) No 178/2002, art. 19(1), second sentence

Inform the consumers, recall if necessary

The immediate withdrawal and the information of the authorities, the paragraph’s first sentence, are quoted alongside. The second adds that, where the product may have reached the consumer, the operator “shall effectively and accurately inform the consumers of the reason for its withdrawal” and, if necessary, recall the products already supplied.

Regulation (EC) No 178/2002, art. 19(2)

The distributor withdraws and passes information on

An operator responsible for retail or distribution activities shall, within the limits of its activities, initiate procedures to withdraw non-compliant products and “participate in contributing to the safety of the food by passing on relevant information necessary to trace a food, cooperating in the action taken” by producers, manufacturers or the competent authorities.

Regulation (EC) No 178/2002, art. 19(3) and (4)

Risk to health: immediate information and collaboration

An operator “shall immediately inform the competent authorities” if it has reason to believe that a food it has placed on the market may be injurious to human health, shall inform them of the action taken and shall collaborate with them on action taken to avoid or reduce risks.

Regulation (EC) No 178/2002, art. 18

Traceability: identifying suppliers and customers

Operators “shall have in place systems and procedures to identify the other businesses to which their products have been supplied”, information made available to the authorities on demand. The Commission’s guidance (2010) suggests, failing a more precise sectoral rule, five years as a general rule, six months for highly perishable products supplied directly to the consumer, and the shelf life plus six months for other products bearing a best-before date.

French guide to food alert management, DGAL/MUS/2023-11

Each operator informs its direct customers

The guide published by the French DGAL with the DGCCRF organises the flow of information: the operator that finds or suspects the non-compliance notifies its local authority and informs its direct customers (traceability, withdrawal measures, recall), who in turn inform their own direct customers. Recalls aimed at consumers are published on RappelConso after validation by the authorities. Other Member States have their own guidance under the same regulation.

French Code civil, art. 1358 and 1366; Cass. soc., 25 September 2013

The email as evidence of a fact

Under French law, an email produced to prove a fact, here the sending of an alert, is admissible and freely weighed by the court (Cass. soc., 25 September 2013, no. 11-25.884). What counts is what makes it possible to establish its content, its date and its transmission; electronic writing carries the weight of paper when its author can be identified and its integrity guaranteed (art. 1366).

Regulation (EC) No 178/2002 · Article 19(1)

Responsibilities for food: food business operators

Consolidated text of 1 July 2024

The article founds the obligation to withdraw and to inform. It prescribes no channel: the message to the distributor may be an email, a portal, a call followed by a written note. What it requires is immediate action and the passing on of information.

If a food business operator considers or has reason to believe that a food which it has imported, produced, processed, manufactured or distributed is not in compliance with the food safety requirements, it shall immediately initiate procedures to withdraw the food in question from the market where the food has left the immediate control of that initial food business operator and inform the competent authorities thereof.

Regulation (EC) No 178/2002, art. 19(1), first sentence

What Sealway takes from it

“Immediately” has to be proven. When the alert goes by email, the copy received by Sealway as it is sent fixes what was written, with which attachments, and the latest time at which the message was transmitted to Sealway. It proves neither receipt by the distributor nor the compliance of the procedure.

Read the regulation on EUR-Lex →

The alert to the distributor, with Sealway in BCC.

Nothing changes in the way you alert: the same email, the same attachments, the same recipient. One more address in the BCC field, and a proof created as the email is sent.

What an alert email most often contains

  • the identification of the product: name, brand, presentation, references;
  • the batch number(s) and the durability dates concerned;
  • the quantities and deliveries concerned for this recipient;
  • the nature of the non-compliance or hazard, and the laboratory result if there is one;
  • the measures requested: hold, withdrawal from shelves, quarantine, return or destruction;
  • what to do towards the distributor’s own customers and any recall;
  • a reachable contact and a request for written confirmation;
  • as attachments: product sheet, list of references, laboratory results, withdrawal instructions.
  1. 1

    Detect and decide

    Laboratory result, own check, complaint, information from a supplier: the internal procedure qualifies the non-compliance and decides the withdrawal and, if the product may have reached consumers, the recall.

  2. 2

    Identify the batch and the customers supplied

    Downstream traceability (art. 18): which distributors, which quantities, which dates. Each will receive its alert.

  3. 3

    Write the alert and attach the documents

    A clear message, organised by batch and by measure, with the useful attachments. The content of the message and each attachment will be part of the proof.

  4. 4

    Distributor in To, Sealway in BCC, send

    As usual, from your mail client: the distributor in the To field, the address of the “Alert batch L24091” collection in the BCC field. The email leaves as usual; Sealway receives the copy.

  5. 5

    The proof is created

    The message received and each attachment get their fingerprint, bound to a qualified electronic timestamp. The certificate states the sender, the To and Cc recipients, the subject, the declared date and the name of each attachment.

  6. 6

    Carry on with the procedure

    Notification of the authorities as provided, publication of the recall where applicable, follow-up of the distributors’ confirmations. A confirmation received can be kept in turn: you forward it yourself to the collection’s address, and the proof dates that forward and fixes its content.

Quality problem detected Batch identified Alert written Distributor in To, Sealway address in BCC Sent Sealway receives the message and its attachments Timestamped proof

What the proof establishes exactly, and what it leaves to the distributor’s confirmation, is detailed in the email evidence guide.

What email evidence brings to the audit, the dispute, the investigation.

Three situations where you will be asked what was transmitted, and where a re-edited message is not enough.

The certification audit

The auditor wants the chronology of the alert and the documents passed to customers. The proofs give the message, the attachments and the time of transmission, verifiable without Sealway.

The dispute with a distributor

The distributor claims to have been warned late, or without the exact references. The proof shows what the alert addressed to it contained, with its attachments, and when it was transmitted to Sealway.

The administrative investigation

The control services ask for the elements of the alert: the proofs make it possible to produce the original message rather than a reconstruction, without prejudging the assessment of the procedure’s compliance.

Insurance and product liability

The operator’s diligence is argued on dated facts. The proof fixes those that go through email; the rest of the procedure, notifications and recall, is documented by its own records.

Several distributors, several batches: organising the proofs.

One email per distributor

Each recipient gets its alert, and each alert becomes a separate proof. The certificate of each states its recipient as it appeared in the message.

One collection per alert

Create an “Alert batch L24091” collection and use its address in BCC: every email sent with that address in BCC files itself there automatically.

Same attachments, same fingerprint

A batch sheet attached to three alerts has the same fingerprint in the three proofs: you show that the same document was attached to each of the three alerts as sent.

The replies

Nothing lands in the collection by itself: a hold confirmation received from a distributor enters it if you forward it yourself to the collection’s address; it is then dated from the forward and fixed in its content. It does not thereby become proof of the original sending by the distributor.

What the alert email, even proven, does not replace.

Notification of the authorities

It follows its own rules, set out in the applicable guidance. Evidence of an email to the distributor does not stand in for it.

Consumer information

Where the product may have reached consumers, effective and accurate information and, if necessary, the recall go through the official channels: in France RappelConso, in-store notices and the other means provided.

The distributor’s confirmation

Sealway establishes neither receipt nor reading of the alert. Ask for a written confirmation and plan the reminder; when receipt has to be proven, use a sending method that guarantees it.

The food safety management plan

The proof documents a message; it does not amount to implementation of the measures, compliance of the HACCP plan or effectiveness of the withdrawal.

Example: a batch of raw-milk cheese, Listeria detected.

  1. 22 September

    Alert

    A positive own check on batch L24091. Three distributors supplied. Three alert emails leave at 11:08 am, with the batch sheet and the laboratory result, Sealway in BCC. The local authority is notified right after.

  2. 23 September

    Confirmations and recall

    Two distributors confirm the hold by email; the quality manager forwards these confirmations to the collection’s address. As the product was sold, the recall is published.

  3. 4 March

    Audit

    The auditor asks for the chronology. The quality manager produces the three proofs: messages, attachments, timestamps, and the confirmations as he forwarded them.

The proofs establish what was written to each distributor, with which documents, and the time each message was transmitted to Sealway. They establish neither that the distributors read the alert, nor that the withdrawal was effective on the shelves, nor that the procedure was compliant: those questions belong to the confirmations obtained, the controls and the authorities’ assessment.

Plain email, email with Sealway, registered delivery: what each proves.

Three ways of transmitting the same alert, and what is left when you are asked to produce it.

Comparison of the ways of transmitting an alert to a distributor
Approach What it brings Its limits
Plain email Fast, written, with attachments; the usual channel of alerts. The message produced later comes from your mailbox: its content and its date can be disputed.
Email with Sealway in BCC The same email, plus a copy received by a third party as it is sent and timestamped: content, attachments, recipients shown and transmission fixed. €1.99 per proof up to 9 attachments; beyond that, one credit per batch of 10 items, message included. Proves neither receipt nor reading by the distributor; replaces neither the notification of the authorities nor the recall.
Qualified electronic registered delivery Presumption of sending by the identified sender, of receipt by the identified addressee and of accuracy of the dates (eIDAS Regulation, art. 43 and 44). A distinct service, to be planned in the procedure; less immediate than an email in a morning of alert. Can be combined with the email with Sealway.

Email remains the channel of urgency; Sealway fixes its content and its transmission. When receipt by the distributor has to be proven, a sending method that guarantees it is added; it does not replace the speed of the alert.

What Sealway proves, and does not prove, for a withdrawal alert.

Sealway makes it possible to establish

  • the exact content of the alert as received by Sealway;
  • the attachments transmitted with it: batch sheet, laboratory results, instructions;
  • the recipients stated in the message;
  • a bound on the moment of sending: the message, as received by Sealway, existed no later than the time of the qualified timestamp;
  • that the message and its attachments have not been modified since.

Sealway does not, on its own, establish

  • that the distributor received the alert, read it or understood it;
  • that it carried out the hold or the withdrawal;
  • that every regulatory obligation was met;
  • that the withdrawal was compliant or sufficient;
  • that the authorities were properly notified;
  • that the content of the alert, laboratory results included, is accurate.

The authorities, the auditor and, where it comes to that, the court assess compliance and diligence. Email evidence gives them the original message, its attachments and its date, without depending on the person producing them.

What a qualified timestamp changes for a withdrawal alert.

Each alert received in BCC is placed in a Sealway proof as it is sent. Six months later, it is possible to verify that the message and attachments produced are the ones bound to the timestamp created that day.

  • SHA-512 fingerprint of each file: the proof bears on this exact version; modifying the file changes the fingerprint, and the fingerprint cannot be turned back into the file.
  • Qualified electronic timestamp: presumption of accuracy of the date and time and of integrity of the data (eIDAS Regulation, art. 41(2)). The date comes neither from the device nor from Sealway.
  • Evidence file verifiable without Sealway: certificate, manifest, timestamp token and fingerprints, with the references of the anchoring on public blockchains.
The mechanism in detail: prove the content and sending of an email

Frequently asked questions

What quality managers ask before, during and after an alert.

How much does an alert with several attachments cost?
One credit (€1.99) per batch of 10 items, the message itself counting as one item: up to 9 attachments, one credit; 10 to 19 attachments, two credits; and so on, up to 49 attachments per email. An alert with a batch sheet, analyses and instructions usually stays at one credit.
Does Regulation 178/2002 require sending an email to the distributor?
No. Article 19 requires initiating the withdrawal immediately, informing the competent authorities, informing consumers where the product may have reached them and cooperating; article 18 requires being able to identify one’s customers. The channel for informing direct customers is not prescribed: the French guide to food alert management organises that information without imposing email. Sealway is useful when email is the channel chosen.
How do I prove that a withdrawal alert was sent to the distributor?
By having a copy of the alert received, as it is sent, by a third party that dates it: Sealway in BCC. The evidence establishes the content of the message, its attachments, the recipients shown and its transmission to Sealway no later than the time of the qualified timestamp.
Does Sealway prove that the distributor read the alert?
No. Neither receipt, nor opening, nor reading, nor execution of the withdrawal. Ask the distributor for a written confirmation and, when receipt has to be proven, use in addition a sending method that guarantees it.
Are the alert’s attachments part of the evidence?
Yes. Product sheet, batch numbers, laboratory results, withdrawal instructions, list of references: each attachment received with the message is kept and given its own fingerprint, listed on the certificate with its name.
What if I send the same alert to several distributors?
One email per distributor gives one proof per distributor, each stating its recipient. A single email with several recipients in To or Cc gives one proof that lists them all. Either way, an identical attachment carries the same fingerprint everywhere: you show that the same document was attached to each alert as sent.
Does a Sealway proof replace the notification of the authorities?
No. Notification follows its own rules, described in the applicable guidance, and the recall aimed at consumers goes through the official channels. The proof documents the email to the distributor; it notifies nobody.
What is this evidence worth before the authorities or a court?
Under French law, an email produced to prove a fact is admissible and freely weighed by the court (Cass. soc., 25 September 2013, no. 11-25.884); other jurisdictions have their own rules. A qualified electronic timestamp enjoys a presumption of accuracy of the date and of integrity of the data (eIDAS Regulation, art. 41). What the alert proves about the compliance of the procedure remains for the authorities and the court to assess.
Can I create the proof afterwards, from the email sent?
No. A .eml file exported from the mailbox and imported later would only prove its existence on the date of the import, establishing nothing about the sending; the web app refuses it. Email evidence is created as the email is sent, with Sealway in BCC. Forwarding the sent email to the Sealway address creates evidence of the forward, not of the original sending.
How long should these proofs be kept?
The regulation sets no period for traceability records; the Commission’s guidance suggests, failing a sectoral rule, five years as a general rule, six months for highly perishable products supplied directly to the consumer, and the shelf life plus six months for other products bearing a best-before date. The evidence file you keep remains verifiable indefinitely; keep it with your traceability records, and the originals beyond the retention period of your plan.
Can Sealway also serve for an alert received from a supplier?
Yes, the same way: forward the alert received to your collection’s address to fix its content and date the forward, then put Sealway in BCC of the alerts you send to your own customers. The chain of information is documented link by link.

References

Texts, official guidance and decision cited on this page; the French sources are in French.

  • Regulation (EC) No 178/2002 of 28 January 2002 (general food law), art. 14, 18 and 19, consolidated text of 1 July 2024 EUR-Lex →
  • European Commission, guidance on the implementation of articles 11, 12, 14, 17, 18, 19 and 20 of Regulation (EC) No 178/2002 (26 January 2010) food.ec.europa.eu →
  • Technical instruction DGAL/MUS/2023-11 of 10 January 2023, French guide to the management of food alerts Bulletin officiel du ministère de l’Agriculture →
  • French Ministry of Agriculture, “Comment fonctionne le système d’alerte alimentaire ?” (4 June 2025) agriculture.gouv.fr →
  • RappelConso, the French official product recall site rappel.conso.gouv.fr →
  • French Code civil, art. 1358 to 1362 (admissibility of the modes of proof) Légifrance →
  • French Code civil, art. 1366 (evidential weight of electronic writing) Légifrance →
  • Cour de cassation, social chamber, 25 September 2013, no. 11-25.884 Légifrance →
  • Regulation (EU) No 910/2014 of 23 July 2014 (eIDAS), art. 41 EUR-Lex →

Sealway provides neither legal nor regulatory advice. The compliance of a withdrawal or recall procedure is assessed against the regulation, the applicable guidance and the circumstances, by the competent authorities and, where it comes to that, the court. The French guide and decision cited illustrate the French implementation of a regulation that applies across the European Union.

Your next alert, with Sealway in BCC.

The message, its attachments and the recipients shown, received as it is sent and timestamped by a qualified third party. Join the waitlist to be notified at launch.

By signing up, you agree to be contacted by Sealway about the launch. No sharing with third parties.