Skip to content
Mock demo · simulated data

A mock demo for food-plant quality teams

Know which lots to pull. And prove the fix worked.

LotGenealogy links every ingredient lot to the batches it entered and the finished lots that left the plant. Scope a recall by lot and date in seconds, then close the loop with CAPA records and effectiveness checks.

Trace a lotOpen CAPA records

All data on this site is invented. 29 synthetic batches, 24 Aug 2026 to 22 Sept 2026.

Flour lotB-01Finished AOil lotB-02Finished BHerb lotB-03Finished CSalt lotB-04Finished D

Scope with records, not guesses

Same simulated plant, same suspect lot, two very different scopes.

One suspect ingredient lot. How much do you pull?

Without lot records, every lot of 3 affected products made in the period is in scope: 20 lots, 130,500 units.

Trace a lotSee CAPA records

What it shows

  • Forward and backward trace

    From a finished lot to every ingredient lot inside it, or from an ingredient lot to every finished lot and depot it reached.

  • Recall scoping by lot and date

    Pick a suspect lot and a production window. See exactly which lots, how many units, and where they went.

  • CAPA records

    Root cause, owned actions, due dates and a documented effectiveness check linked to the lot that triggered it.

  • Effectiveness checks

    Compare before and after data against the criterion written at the start, so a CAPA closes on evidence.

From a suspect lot to a closed CAPA

  1. Step 1

    Trace

    Follow the lot forward to finished lots and depots, or backward to every ingredient lot.

  2. Step 2

    Scope

    Set the lot and the production window. Hold back what the records show is not affected.

  3. Step 3

    Correct

    Open a CAPA, assign owned actions and define the effectiveness check up front.

Shaping this with design partners

This is a sketch built on invented data, at design-partner stage. Algoshred is working out the details with food manufacturers who want to shape it.

Talk to Algoshred