MES traceability links each lot of material to the orders, machines, people and finished units it touched, recorded as the work happens. It answers two questions fast: backward (what went into this unit?) and forward (where did this material go?). Test it with a timed mock recall, not with a demo.
Two directions, one record
A customer complains about pallet P3. Tracing backward finds the film and ink that went into it, while tracing forward from that film lot finds every other pallet at risk.
Genealogy is the common word for this tree. It is one of the classic functions listed in MES modules, and what is an MES shows where it fits.
What gets recorded, and when
The tree is built from a few plain events. If one link goes missing, the chain breaks at that spot.
- Receive: supplier, supplier lot, your own lot code, quantity, date.
- Issue: which lot moved to which line or order, and how much.
- Consume: the moment the lot went into production, with the machine and order.
- Produce: the output lot, pallet or serial, quantity, time, and who ran it.
- Ship: which output went to which customer, and when.
Capture them at the moment they happen, by scan or signal at the line. A record typed from memory at shift end is the weakest link you can have.
How fine should tracing be?
Finer tracing means a smaller recall, and more work on the floor. Compare both sides using your own numbers.
Now the other side. Example: 400 scans a shift at 6 seconds each is 2,400 seconds, or 40 minutes of someone's time.
That is why many plants trace by lot and keep serial numbers for high-value or safety-critical parts. Your customer or regulator may decide it for you.
Where to scan first
You do not need every point on day one. Build from the ends of the chain, and then fill the middle where risk is highest.
- Goods in: give each received lot a scannable label that links to the supplier's lot.
- Line loading: this is the key step, because it ties a lot to an order and a time.
- Finished pallet: the output label holds the order, so the tree connects.
- Shipping: the scan that links pallets to a customer.
The window problem
A lot change has a real time and a recorded time. Example: at 120 units a minute, a scan made 15 minutes late leaves 15 x 120 = 1,800 units that could hold either lot.
Bulk material is worse. In a hopper or a tank, old and new mix for a while, so your rule must treat that overlap as both lots.
Write the rule down, and base it on how the material really behaves. A trial with a colour change or a marked lot can show how long the overlap lasts.
What the rules ask for
Rules differ by sector and country. This is a plain summary to start from, not legal advice, so read the text that applies to you.
- EU food: Regulation 178/2002, Article 18 asks food businesses to identify who supplied them and which businesses they supplied. The Commission's guidance calls this one step back, one step forward, and says the Regulation does not expressly require the internal link between incoming and outgoing products, sector rules aside.
- US food: the FDA Food Traceability Rule covers listed foods, with key data elements for critical tracking events and a traceability lot code. Congress directed FDA not to enforce it before 20 July 2028, and FDA says it intends to follow that.
- US drugs: 21 CFR 211.188 requires batch records to identify each batch of component used, along with major equipment and the people involved. See MES for pharma.
Customer standards can go further than the law. Check your contracts as well.
Run a timed mock recall
Choose one from last month, without warning anyone.
Use the system only, not people's memories.
List each order, pallet and customer the lot reached.
Take one finished unit and list what went into it.
Account for the whole lot, as shown below.
Write down the minutes, and each place you had to fall back on paper or a phone call. Those spots are your repair list.
Mistakes that break the chain
- Backflushing lots. The system assumes which lot was used, rather than recording it.
- Free-text lot numbers. One typo breaks a search, so scan them.
- Losing the supplier's lot. Your own code must still link back to theirs.
- Forgetting rework. Units that loop back need a record, and rework is where trees often snap.
- Shared logins. "Who ran it" is then no answer at all.
- Tracing without quality status. Link holds to lots, so a held lot cannot ship by accident.
A recall can also become your largest cost of poor quality. So the size of the window is a money question, as well as a compliance one.
Genealogy tells you what went into a unit. Fabrico answers a different question, where the line's time went: it is a light MES for OEE, with stops, speed and counts live from machines and causes tagged at the line. See Fabrico as a light MES for OEE.
What people ask next
What is traceability in an MES?
It is the record that links material lots to orders, machines, people and finished units, captured during production. It lets you trace backward from a unit and forward from a lot. MES modules shows where it sits among the other functions.
What is the difference between traceability and genealogy?
People often use them for the same thing. Where they differ, genealogy means the tree of what went into a product, while traceability is the wider ability to follow it through the supply chain, including customers.
Lot or serial traceability, which do I need?
Lot tracing suits most high-volume goods, while serial tracing suits high-value or safety-critical parts. Weigh the size of a possible recall against the scanning time. Your customer's or regulator's rules may settle it.
How fast should a mock recall be?
We found no general legal time limit that fits every sector, though the FDA Food Traceability Rule asks for records within 24 hours of a request, or a time FDA agrees, for covered foods. Set your own target from your customers' demands, then time yourself against it.
Can I do traceability without an MES?
Yes, on paper or in a spreadsheet, if volumes are low and a mock recall still comes out right. Trouble starts with many lots per shift, because the search gets slow and errors creep in. Test it with the steps above, and see MES for small manufacturers.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.