V5 Ultimate
Module · Traceability

Lot traceabilityrecall in minutes, not weeks.

V5 captures the lot link at every point of consumption, so the trace is a query — not a war room.

Start free — no card
The lot tree

Supplier flags Flour lot F-4471. V5 walks the tree up — the dough it built, the SKUs it became, the customers that got it. Pull the lever to see the blast zone.

downstream · 4 customers
Tesco · RDC Magor
10,000 packs · 06 Jun
Sainsbury's · DC-04
5,000 packs · 07 Jun
Ocado · CFC-3
4,000 loaves · 07 Jun
Booker · Wellingborough
2,000 loaves · 08 Jun
2 finished SKUs
SKU 10421 · brioche burger bun 4pk
FG-9912 · 15,000 packs
SKU 10580 · brioche loaf 400g
FG-9913 · 6,000 loaves
1 dough batch
B-78214 · brioche dough
mixed 03 Jun · 1,850 kg · WO-78214 · split into buns + loaves
upstream · 4 ingredient lots
Flour · lot F-4471
ADM · COA on file
Yeast · lot Y-9921
Lesaffre · COA on file
Egg wash · lot E-2210
Noble Foods · COA on file
Packaging film · lot P-77
Berry · COC on file
Affected units
0
Customers
0
Forward depth
2 hops
Backward depth
4 lots
FSMA 204 · ISO 22005 · §820.65

Pull any thread.Walk every direction in time.

Most traceability tools answer "where did this lot come from." V5 answers "where did this lot come from, what else was made with its siblings, what's still on the shelf, which customers received it, and what would happen if we recalled it." One query. One graph.

FSMA 204 · the 24-hour rule

Recall scope, end-to-end, in ~14 seconds.

FSMA gives you 24 hours to produce traceability data on request. V5 produces it before the kettle boils — because the graph is live, not assembled at query time.

0.0s
recall · live trace
  1. 0.0squery: complaint #C-24-0918 → which lot
    L-24-0918-D
  2. 1.4sreverse: dispense events touching this lot
  3. 3.1sreverse: receiving for those raw lots
  4. 5.6sforward: sibling finished lots from same raw
  5. 8.2sforward: shipments for those siblings
  6. 11.4sforward: on-hand inventory still bindable
  7. 14.0sreport.pdf · signed · ready to send to FDA
Genealogy · the live graph

One lot. Every ancestor. Every descendant.

PO-441 · Aurora BioPO-442 · PacificPO-447 · HeartlandPO-451 · MarinerL-24-0918-DFG · VITA-D3in questionSHIP-882 · Acme Health · 1,200uSHIP-884 · GreenStar · 800uSHIP-889 · Vita Direct · 600uSHIP-901 · CVS DC-North · 2,400uSHIP-908 · Wellness Co · 400uOn-hand · BIN-D-12,14,17 · 3,184uL-24-0918-A..G · 6 siblings
4 ancestor receipts (raw lots)
6 sibling finished lots
5 shipments + on-hand
Tamper-evident

Each event is the previous event's witness.

Trace events are linked into a Merkle-style chain. Editing one event invalidates every event that came after it. An auditor doesn't have to trust V5's word — they re-compute the chain.

trace chain · lot L-24-0918-D
RECEIVESep 02 · PO-441a1f9·…·02e7
QC HOLDSep 02 · CoA log9b22·…·71d4
RELEASESep 03 · QA M.Aoki4ef0·…·c891
DISPENSESep 18 · WO-9180c5d·…·a112
BLENDSep 18 · MIX-2047c·a2·91
FILLSep 18 · FILL-08e4d6·…·22ff
PACKSep 19 · PACK-021b88·…·09a3
SHIPSep 20 · SHIP-8825fcc·…·0e4a
Each hash includes the previous hash. Re-sealing the chain takes ~120ms.
Recall · the cascade

One click notifies everyone who needs to know.

23 emails
Affected customers

Templated per region, signed PDF attached, replies routed back to QA inbox.

9 roles
Internal teams

Ops, QA, Sales, Customer Success, Legal — each gets the slice that's actionable to them.

FDA + state
Regulators

Pre-formatted 1-page incident report attached. Submission tracking number returned.

A recall is a query, not a project.

V5

Curious how V5 actually walks a recall in minutes?

Connected

One genealogy graph — every system writes the lot link at source.

No nightly reconciliation across WMS, MES, ERP, lab, and shipping. Every consumption event writes into the same genealogy graph — backward and forward trace become a graph walk in seconds.

WMS · receipt + putaway
Every vendor lot lands with a GS1 scan at the dock. Parent → child LPN splits keep the lot link intact through put-away.
MES · dispense + in-process
Every dispense, charge, in-process sample and yield event records the consumed lot at the kiosk — no after-the-fact entry.
eBMR · sealed batch record
The sealed batch record is the canonical lot link for the WO — every downstream event references it by ID, not by paper.
Genealogy
Graph
one-query trace
Shipping · BOL + SSCC pallet
Every customer ship-event is a graph edge — pallet SSCC, BOL, carrier, customer and ship-date land against the finished lot.
ERP · receipts + ship posts
Two-way posts to your ERP carry the lot link both directions. Finance sees the lot. The lot sees the finance event.
Customer + supplier portals
A supplier recall lands in your portal with the affected lot. A customer notification fires through the portal — no email chain.
No five-system reconciliation. No paper.
The lot link is captured once at the point of consumption. Backward + forward trace, FSMA 204 export and recall scope all read the same graph.
V5

Wondering how traceability plugs into the rest of your stack?

Engineered on
21 CFR Part 11 e-signatures
Immutable audit trail
Multi-tenant RLS isolation
GS1-128 license plates
Two-way ERP adapters
Instead of an FAQ

Just ask V5 — it knows the product cold.

Pick a question or type your own. V5 answers grounded in how lot traceability — vendor → wo → finished lot → customer | v5 ultimate actually behaves on the floor.

Got questions, or want to see it on your shop floor?

Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.