Rebuild a batch history and manage a product recall

How to trace every step of a batch and what to do in the first minutes of a product recall or withdrawal.

Quality managers and ownershaccp:manageReading: 3 minUpdated on: 2026-09-19

In critical moments, such as a product recall flagged by a supplier or a surprise inspection, how fast you can rebuild a batch history makes the difference. KlyraOS links receiving, production, consumption and sale in a single, searchable timeline.

Active batches with use-by dates and expiring products — Desktop view (browser)

Tracing upstream: where the batch comes from

From any batch you can trace back to the original receiving document, the supplier and, if the product comes from a production run, the raw material batches that generated it.

Tracing downstream: where the batch ended up

You can equally see which recipes, production runs or transfers between sites used that batch, along with any losses recorded against it.

First steps in a product recall

As soon as you receive a recall notice from a supplier, identify the affected batch immediately and check its history in KlyraOS: quantity received, quantity consumed, quantity still in stock and sites involved.

Identify the batch and supplier involved
Check the quantity still in stock
Physically withdraw and quarantine the batch at every site involved: KlyraOS does not provide an in-app block button
Check whether the batch went into recipes or production
Inform staff and, if needed, customers

Documenting for inspection

The full, exportable batch history is the concrete proof needed during an inspection: it demonstrates the supply chain is traced from receiving through to service.

What this guide covers

product recall
product withdrawal
batch history
traceability
inspection
food safety crisis

Steps

Open the sheet of the flagged batch
Check the origin section to trace back to the supplier
Check the usage section to see where it ended up
Verify the quantity still available at each site
Physically withdraw and quarantine the affected product
Export the history for the required documentation

Common issues

The batch flagged by the supplier cannot be found straight away → the code they gave does not match your internal one → also check the supplier codes linked to the batch
The remaining quantity does not match the physical count → some consumption was not recorded in real time → update consumption before calculating the quantity to withdraw
A batch shows as used in a recipe but the dish cannot be found → the recipe does not update traceability → check that the production declaration was completed correctly
The recall arrives after the product has already been consumed → the supplier notice was not checked promptly → review pending supplier notices daily

Frequently asked questions

How long does it take to rebuild a batch history?

With traceability enabled, the origin and usage timeline is available in minutes directly from the batch sheet.

What should I do first in a product recall?

Identify the affected batch, check the quantity still available and physically withdraw and quarantine it at every site involved before anything else; KlyraOS does not provide an in-app block button.

Can I export a batch history for an inspection?

Yes, the batch history can be exported as supporting documentation for checks and inspections.

Related guides

Open this screen in the appSign-in required

Was this guide helpful?

Still need help?

Describe the issue: page, location, organisation and role are attached automatically.

Contact support