Lot-specific recall notices your customers actually see

‖ Quarantined is a hold. Use it while you investigate — a result being re-tested, a supplier query, a complaint you have not got to the bottom of. It is reversible: when you are satisfied, you release the lot back to Verified, or you escalate it to a recall.

⨯ Recalled is final. A recalled lot can only move on to Archived; it never returns to Verified, by anyone, at any permission level.

A lot that was never published on BatchRoute — still Pending — cannot be recalled in one step. If it has reached customers anyway, put it on hold and then recall it: both moves are open to you straight away, and the hold's notice is what anyone looking the lot up sees in between.

For a lot on hold: the Quarantined status with its mark, your notice, a line saying the certificate is temporarily unavailable while the lot is re-checked, and your support address.

For a recalled lot: a filled stop-use line above everything else on the page, the Recalled status, your notice, and your support address. The certificate is replaced by the recall — it is not shown, and the certificate link stops working at once, including on a page a customer already has open.

1. 01 — Open the batch

   In the workspace, find the lot — the batch list searches by lot code — and choose the new status. Only the moves that lot can make, and that you are allowed to make, are offered.

2. 02 — Write the notice

   What the customer holding the bottle should know and do. It is required: a hold or a recall cannot be saved without one, because a warning with no explanation under it helps nobody.

3. 03 — Confirm a recall by typing the lot code

   Case and stray spaces do not matter, but the code does. It is deliberately a little friction: a recall cannot be undone, so it cannot happen by a stray click.

The change is live on the next lookup. Lookups are answered fresh every time rather than from a cached copy, so there is no propagation delay to wait out.

In your team, owners, admins and QA managers can recall a lot. Operations can put a lot on hold but cannot recall it. Viewers can do neither. The rule is enforced on the server, not by hiding a button, so it holds however the request arrives.

BatchRoute support staff hold neither permission. They can read your workspace to answer a question, inside a time-limited access window they open with a reason recorded in your history, and change nothing.

If your BatchRoute account is ever suspended, holding and recalling lots still work, and so does the public page your customers use. A suspended account cannot add products, batches or certificates, or publish a lot — but suspension never removes the controls for warning the people holding your product.

You can edit the notice as things develop — each edit is recorded — but you cannot empty it while the lot is on hold or recalled.

When you archive a recalled lot, the stop-use line stays on its page, now with the date of the recall, and its certificate stays withheld. Archiving tidies your records; it does not bring the bottles back, and a customer finding one in a cupboard next year still needs to be told.

Every step is in the batch's history: the status it moved from and to, the notice written with it, who did it, their role and when. Nothing in the workspace edits or deletes an entry, and neither can our support staff. The only exceptions are the ones our privacy notice sets out: removing or anonymising personal information where privacy law requires it, and the retention period it describes.

BatchRoute does not decide whether a lot should be recalled, notify customers, retailers or regulators, or track who received a product. It gives the person holding a bottle a reliable answer when they look it up, and it gives you a record of what was said and when.

A notice here is a way to reach the person holding the product. It does not replace your statutory recall obligations.

BatchRoute publishes and hosts the batch information you give it. It is verification and documentation infrastructure — not a testing laboratory, a certification body, or a statement that a product meets any regulation. We don't test your product, review your laboratory results, certify anything or determine regulatory compliance. You remain responsible for the accuracy and lawfulness of what you publish.