Production Genealogy: Trace Every Lot and Serial Forward and Backward

It is 4pm on a Thursday when the email lands. Your bearing supplier has found a defect in one batch and is asking every customer the same question: did you use lot number BRG-6205-0417, and if so, where did it go?

Now the clock is running. Somewhere in your finished-goods area sit units you shipped last month with that exact lot pressed inside them. Which ones? You are not sure. So the plant does what plants have always done: someone opens a spreadsheet, someone else digs through paper travelers, and a third person starts calling customers to buy time.

By the time you have an answer, it is the next morning and you have either over-recalled (pulling good product and burning trust) or under-recalled (leaving suspect units in the field). Neither is a good look.

This is the problem production genealogy solves. And in Qualis, the answer to that supplier's question is already recorded, the moment each finished unit was built. You are not reconstructing history. You are just reading it.

What production genealogy actually is

Think of it as the family tree of every unit you make.

For any finished lot or serial number, production genealogy answers two questions:

• Backward (the ancestors): which component lots and serials went into this finished unit? Which raw materials, which sub-assemblies, from which manufacturing order?
• Forward (the descendants): this component lot I am worried about, which finished units did it end up in? This is the where-used, or recall, trace.

Read the tree one way and you have a defect investigation ("this unit failed in the field, what was inside it?"). Read it the other way and you have a recall scope ("this batch is bad, what did we build with it?").

The honest villain here is not a rival ERP. It is the manual reconciliation, the paper traveler, and the spreadsheet that only one person knows how to read. Genealogy replaces all three with a record that writes itself.

The important word is as-built. A bill of material tells you what a product is supposed to contain. Genealogy records what a specific unit actually consumed, on the actual day it was made, down to the specific lot. Those two are not always the same, and the gap between them is exactly where recalls go wrong.

How genealogy works in Qualis

Here is the part that matters for a busy plant: nobody has to maintain the genealogy. It is a by-product of doing the work you already do.

It starts on the shop floor, not in a spreadsheet

When you run a manufacturing order, your operators issue components against it and receive the finished goods when the order is done. That is normal shop-floor activity.

On the order's shop-floor screen, an Issue Materials section gives each component line its own Issue button, and a Receive Output section gives each output a Receive button. When a component is lot or serial tracked, issuing it records which lot was consumed. This is not extra paperwork; it is the material issue you were already doing.

Then comes the quiet magic. The moment you receive the finished goods, Qualis mints a genealogy edge automatically. It reads the order's material-issue ledger, takes a snapshot of every component lot that was consumed, and pins it to the finished lot you just received. That edge records:

• The finished product, its lot or serial, and the quantity received.
• Every component lot or serial consumed, with the quantity and the operation that consumed it.
• The manufacturing order, the receipt move, and the exact timestamp it was produced.

Each record gets its own reference (like GEN-00001) and is written once, then locked. It is an immutable audit edge, not something anyone edits later. Byproducts are received without a genealogy edge, because genealogy follows the finished good you actually care about tracing.

Because the edge is built from the issue ledger, not from the recipe, it captures what really happened. If an operator substituted a different lot at the last minute, the genealogy reflects that lot, not the one the BOM assumed.

The Trace tab: pull the thread from either end

Open a manufacturing order and you will see a row of tabs: Materials, Material Plan, Work Orders, Cost, and Trace. The Trace tab is where a finished order shows the lots it produced and lets you walk the tree from there. (Until the order has received finished goods, it simply tells you genealogy appears after finished-goods receipt.)

From a finished lot, trace backward and Qualis shows you the component lots consumed into it, and keeps going down through any sub-assembly orders that fed it. From a component lot, trace forward and it shows every finished lot that lot ended up in, climbing up through the parent orders. The walk is multi-level, so a raw material three assemblies deep is still reachable in one query.

One click to the family tree

You do not have to open an order to start a trace. On the Manufacturing Orders list, the top bar has a dedicated Genealogy Trace button.

Open it, pick a lot or serial number, and Qualis builds the tree in both directions. It is designed for the exact moment in our story: the supplier names a lot, you paste it in, and you see every finished unit it touched. Need it for the quality file or the customer? Export the trace to CSV and attach it.

A couple of engineering details worth trusting: the trace is cycle-safe (it will never loop forever on a circular reference) and bounded (it stops cleanly at a sensible node limit and tells you so, with an option to export the full set). A deep or messy genealogy will not hang your screen.

Why an automatic genealogy matters

Let's go back to that 4pm email, but this time you are running Qualis.

You open Genealogy Trace, paste in the bearing lot, and trace forward. In under a minute you have the exact list of finished serials that consumed it, which orders produced them, and which are still sitting in your warehouse. You recall precisely those units. Not one more, not one less.

Here is what that automatic record quietly prevents:

• Over-recalls. Without lot-level trace, "we think it was around March" becomes "pull everything from March." Genealogy lets you pull only what is actually affected.
• Under-recalls. The scariest outcome is a suspect unit you miss. A complete as-built tree closes that gap.
• The spreadsheet that lies. Manual traceability logs drift the moment someone forgets a row. A record generated at receipt cannot forget.
• Audit panic. When a customer or auditor asks you to prove a specific unit's content, you show them the genealogy record and the audit trail behind it, instead of promising to "get back to them."

To be fair about the market: serious ERPs can do lot traceability. The real difference is how much manual effort it costs you day to day, and whether it is switched on by default or buried behind a pricier tier and a consultant's configuration. Many mid-market setups still lean on spreadsheets or bolt-on traceability logs that someone has to keep alive by hand. In Qualis, the genealogy is a native part of the manufacturing order lifecycle, minted by the same receipt step your team already performs.

The end-to-end picture

Zoom out and the whole thing is one simple flow. Components (each with their own lot) are issued to an order. The order is finished and received, which mints a genealogy edge. That finished lot may itself become a component in a higher-level order, and the tree grows.

Trace down that tree and you have the ancestry of any unit. Trace up it and you have the where-used trace for any component lot. Same data, read in two directions, always current because it is captured at the source.

Frequently Asked Questions

What is the difference between a bill of material and production genealogy?

A bill of material is the recipe: what a product should contain. Production genealogy is the as-built record: what a specific finished lot actually consumed, including the exact component lots, captured on the day it was made. The BOM is a plan; the genealogy is history.

Do I have to create genealogy records manually?

No. Qualis mints the genealogy edge automatically when you receive the finished goods against a manufacturing order. It snapshots the component lots from the order's material-issue ledger, so the record is a by-product of normal shop-floor work, not an extra data-entry task.

Can I trace both forward and backward?

Yes. Backward trace shows the component lots and serials that went into a finished unit, walking down through any sub-assembly orders. Forward trace (the where-used or recall trace) shows every finished lot a given component lot ended up in, climbing up through parent orders.

Does it work for serial numbers as well as lots?

Yes. Genealogy traces both lot-tracked and serial-tracked items. Serial-tracked finished goods are received one unit per serial, so each serial gets its own precise as-built record.

How does this help with a recall?

When a supplier or your own QA flags a suspect component lot, you trace it forward to get the exact list of finished lots and serials that consumed it. That lets you scope the recall to only the affected units, and export the trace to CSV for the quality file or the customer.

Can I get the genealogy out of the system for an audit?

Yes. Every genealogy record carries its own reference and is an immutable, audit-logged edge, and the trace viewer lets you export the full tree to CSV. You can hand an auditor or customer a complete, source-of-truth record rather than a hand-kept log.

The bottom line

Recalls and defect investigations are stressful because they are usually a scramble to reconstruct history you never properly recorded. Production genealogy flips that. It records the family tree of every unit as you build it, so when the hard question comes, the answer is already sitting there, one trace away.

Trace forward for recalls, trace backward for root cause, and stop keeping the spreadsheet that only one person understands.

Want to see it on your own products? Explore production genealogy inside the Manufacturing Orders module in Qualis, or start a trial and build one order end to end to watch the genealogy write itself.