Track and trace is one phrase covering two different problems. Tracking answers where is it now. Tracing answers where has it been and what is inside it. A plant can be excellent at one and helpless at the other, and most are, which is why the phrase is worth unpacking before anyone buys software for it.
Tracking: where is it right now?
Tracking is a present-tense question. Where is order 4471? Which rack holds the customer's components? Where did the part pulled for rework end up? Answering requires location events captured as things move: a scan at a station, an RFID read at a gate, a completion event at an operation. Plants without tracking answer by walking the floor, and the walk costs twice, once in the time spent looking and once in the parts remade because nobody found the original.
The classic tracking failure is the part that goes dark. A cabinet door pulled to a repair bench, a receiver pulled to refinish, a hull moved across the yard: the system still shows it in its last known state, so a replacement gets ordered at full cost in material, labor, paint, handling, and freight. Scan-in and scan-out at exactly those bleed points, with RFID where scanning is impractical, is the standard fix and usually the fastest payback in the whole program.
Tracing: where has it been, and what is in it?
Tracing is past-tense and relational. Which supplier lots went into this batch? Which finished lots did that suspect ingredient reach? Which customers received them, and in what quantities? Answering requires links rather than locations: an edge recorded every time an input is consumed into an output. Those edges form the genealogy graph a recall walks in either direction. The mechanics are covered in our lot genealogy guide, and the short version is that the links have to be captured while production runs, because reconstructing them later from binders is exactly what turns a two-minute question into a two-day project.
Why plants end up with half of each
Partial track and trace is the norm because both grew up as side effects of other systems. The ERP knows what was ordered and shipped but not where anything physically sits. The historian knows what the machines did but not which lot was running. Paper batch sheets hold the consumption links, but only a human can read them, one page at a time. Each system is right about its own slice, and the slices never join, so the plant can tell you a great deal and still not answer the two questions that matter under pressure.
What a working system captures
- Receiving: inbound lot identity and quantity, with the paperwork read automatically instead of filed.
- Movement: location events at the points where things get lost, staging areas, rework benches, yards, and cross-plant transfers.
- Consumption: the load-bearing capture, which input lots fed which batch or unit, recorded at the station or the scale.
- Process context: machine, hour, operator, and settings, so a trace can answer why as well as where.
- Pack and ship: lot to case to pallet to customer, closing the loop outward.
Regulation keeps raising the bar
For food companies, FSMA 204 turns tracing from a capability into a deadline: standardized data at defined events, produced within 24 hours, which our FSMA 204 preparation guide covers in plant terms. Firearms manufacturers carry per-unit recordkeeping obligations. Automotive and powersports suppliers get scoped by fastener lot when a supplier flags a problem. The pattern is the same everywhere: the acceptable answer time keeps shrinking, and reconstruction cannot keep pace with it.
Building both halves without a rip-and-replace
The version that ships in weeks is additive. Digitize the capture points that create tracking and tracing data, connect the machines that already know what they made, and let document processing read the existing paper archive into the same layer. Where no MES exists, that layer can become the system of record; where one exists, it sits on top. In Harmony deployments this runs inside a published pilot: $15-20K one time, 4-6 weeks, forward-deployed engineers on-site, with a sub-minute mock recall as a standard acceptance test. Molding plants use the same layer to tie resin lots to presses and finished cartons, as described on our plastics and rubber page, while the tracking half answers the question the floor asks hourly.
Two tests that show which half you are missing
Ask someone to locate a specific work order or part without walking the floor or calling anyone. If they cannot, tracking is missing. Then pick a lot from three weeks ago and ask for every customer it reached with quantities reconciled. If that takes more than a few minutes, tracing is missing. Most plants fail both tests the first time they run them, and the failures point straight at which capture points to digitize first.