Food & Beverage /Document Generation live field guide · 8 min

Recall War Room

Traces an affected lot forward through production and shipments to scope a recall, drafts the customer and retail notification list, and builds the action log — with a recall coordinator approving each stage before any notification is sent.

Open the live demo

theater/demos/food-bev_recall-war-room.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Takes the affected supplier lot, traces it forward through every production batch, finished SKU, customer and shipment, and lays out the scope and draft notifications for a recall coordinator to approve before anything is sent.

Input 01

The contaminated lot

A supplier contamination notice or food-safety alert: the affected ingredient, its supplier lot number, and the notification date — keyed against your traceability and ERP records.

Agent 02

Traces forward, scopes, drafts

Walks the lot genealogy forward — which production batches used the lot, which finished SKUs those batches became, which customers and shipments received them — then drafts the customer, regulator and internal notices.

Output 03

A scope map, with its working shown

The affected batches, SKUs, customers and units-in-market, plus draft notifications, laid out for the recall coordinator to review, correct and approve before any notice is sent or the FSANZ recall coordinator is contacted.

Where it works well

It does the forward trace in full, every time, and shows the chain it followed.

Done by hand under "one step back, one step forward" records, scoping a multi-batch lot can take hours to days — the demo's 4,200 units across 7 customers is the kind of fan-out that is easy to under-count manually.
Best for a quality or food-safety manager who owns recalls and withdrawals, and for running mock-recall drills auditors expect under Standard 3.2.2.
The recaptured hours go back into containment and the customer calls, not into reconstructing the genealogy from spreadsheets.

The slow, dangerous cost of a recall is the forward trace — following one contaminated supplier lot through every production batch, every finished SKU, and every customer shipment, under time pressure, while the clock on product still on shelf is running.

Where it works badly

It is confidently wrong when the traceability records are incomplete — and a clean-looking scope map hides the batches it never saw.

Weak where lot links are recorded on paper, in operator memory, or as free text — the batches it can't see are exactly the ones that bite you.
If rework, repacking or co-mingled bulk means one finished SKU draws from several supplier lots, a one-lot trace will understate the scope. It should flag the ambiguity, not guess past it.

The honest test

If you cannot, right now, trace one finished SKU back to every supplier lot that went into it from your own records, this tool makes that gap faster to hit, not safer to cross.

Point it at receipt and production records that don't link supplier lot to production batch to finished SKU, and it will draw a tidy genealogy that simply stops at the gaps. The map looks complete. It isn't. That is the trap.

What it doesn't do — and shouldn't

It scopes and drafts. The coordinator approves. That boundary is deliberate.

WHAT IT DOES

Shows the lot-to-batch-to-SKU-to-customer chain it traced

Surfaces affected batches, SKUs, customers and units in market

Flags links it could not resolve from the records

WHAT IT WON’T

Send any customer, retailer or regulator notice

Notify the FSANZ recall coordinator or lodge the recall report

Decide the recall is complete or that stock recovery is sufficient

A food recall carries obligations under Standard 3.2.2 of the Australia New Zealand Food Standards Code and the FSANZ Food Industry Food Recall Protocol. A missed batch or a wrong scope can leave unsafe product on shelf; the accountable person stays on the decision because the consequence — and the report to FSANZ — lands on them, not the tool.

What your data has to look like

Lot links recorded as structured fields, end to end, current to the day the lot was received.

Typical readiness

across orgs we see, before the first job

Supplier-lot to production-batch links

Needs shaping

Production-batch to finished-SKU genealogy

Needs shaping

Customer and shipment records per SKU/batch

Usual weak point

Lot identification on-pack

Usually ready

Current allergen and product data per SKU

Usual weak point

The real first job

The forward links are usually the weak point — supplier lot to batch to SKU held on paper, in an operator's head, or as free text nobody can query. Fixing how lot genealogy is captured and kept queryable is usually the real first job — larger and far more valuable than the tracing layer on top. Once the links are clean, every trace after that is fast and complete by default.

Right fit if…

You own recalls and withdrawals and run mock-recall drills under Standard 3.2.2

Your supplier lots, production batches and finished SKUs link as structured, queryable fields

Complex supply chains where one lot fans out across many batches, SKUs and customers

You can trace a finished SKU back to every supplier lot today, from records

Walk away if…

Lot-to-batch links live on paper, in operator memory, or as unstructured free text

Rework and co-mingled bulk mean SKUs draw from several lots you can't reconcile

You ship a single SKU from one lot with no batching complexity — manual tracing already suffices

You want a tool that lodges the FSANZ report or signs off recall completion for you

Open questions

The worried-buyer questions, answered straight

It can under-scope — which is exactly why nothing is sent on its say-so. It traces the supplier lot forward through the production-batch, finished-SKU and customer links in your records, shows the chain it followed, and flags any link it could not resolve. A recall coordinator checks that scope before a single notice goes out. The tool surfaces the genealogy; the person stands behind the recall.

It works from structured, queryable links: supplier lot to production batch to finished SKU to customer shipment. Where those links live on paper batch sheets or in an operator’s memory, the trace stops at the gap and the scope map quietly understates the recall. Getting that genealogy captured as fields under “one step back, one step forward” is usually the first piece of work — and the piece that pays off in every trace after.

No. It removes the manual genealogy reconstruction — the hours of tracing one lot through batches, SKUs and shipments — so the coordinator spends that time on containment, the customer and retailer calls, and the FSANZ recall report. The recall is still theirs to run and to certify under the Food Standards Code. The capacity it frees goes back into managing the incident, not the spreadsheet.

Current to the day the lot was received and used. A recall is triggered on a specific supplier lot and notification date — point the trace at stale or half-entered batch records and it draws a genealogy that no longer matches what was actually produced and shipped. The honest test: can you query, today, which production batches used a given supplier lot and where those batches went?

Recall data — supplier lots, batch genealogy, customer shipment lists — is commercially sensitive and, for the regulator notice, regulated under the Food Standards Code. Any deployment runs against your own traceability and ERP systems and your own data handling, not a shared pool; we scope where the data sits and who can see it as part of the build. The demo here runs entirely on fabricated data — Murray Valley Farms, lot MV-2847 and every customer are invented.

No. It drafts the customer, regulator and internal notices and lays out the scope, but a person reviews and approves them, and a person contacts the FSANZ recall coordinator and lodges the recall report. The FSANZ Food Industry Food Recall Protocol sets out the reports and timeframes a recalling business must meet; the tool gets the drafts and the scope most of the way, and the accountable person closes the last step.

What it takes to build

4–6 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · traceability/ERP connectors · impact dashboard · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your recall readiness?

The honest place to start is a bite-sized first piece — usually proving your lot genealogy can be traced end to end. Tell us where it hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work