Lot genealogy software for medical devices does not solve one problem but three records that frequently sit in separate systems: which material lots went into a finished device, which equipment and operators touched it, and which customers received it. A supplier anomaly or field complaint exposes any break in that chain. The practical test is response speed: reconstructing a lot shipped six months ago should take minutes, not half a day. The sources reviewed here—vendor documentation, a supplier traceability explainer, and a 2026 comparison from GHP News—describe overlapping functions but different boundaries. Some products originate in pharmaceutical or MES contexts, and their claimed compliance with ISO 13485, EU MDR, or 21 CFR Part 11 appears in marketing material rather than independent audit evidence. The decision is less about selecting a category leader than about identifying where incomplete genealogy actually hurts: recalls that cannot be bounded, investigations that require hand reconstruction, and audit defensibility that depends on immutable links.
The three traceability chains are not interchangeable
A common procurement mistake, according to the GHP News roundup, is buying traceability software for one chain while the audit gap sits in another. Medical device companies operate with design traceability, quality record traceability, and product traceability. Design traceability links requirements to design outputs, test cases, risk items, and changes. Quality record traceability links complaints, CAPAs, change control, training, and document versions. Product traceability—lot and serial genealogy—runs through assembly into the device history record and out to unique device identification. A failure that GHP News describes as "a recall nobody can bound because the genealogy has holes in it" belongs to the product chain, and a tool strong in design linkage will not repair it.
This distinction matters for lot genealogy software specifically. Cerebellis, a supplier of traceability tools for regulated industries, describes backward traceability as starting from a delivered finished product and working toward material lots, components, equipment, and operators. Forward traceability begins at an incoming lot and moves toward the products and customers that received it. Both directions must be navigable without manual reconstruction or intermediate export, according to Cerebellis. Under ISO 13485, the organization defines how far it traces and keeps lot-level records; the stricter requirements for implantables remain a separate consideration. MDR supply chain identification and internal production genealogy are distinct requirements, not one feature set.
What the records must link, before evaluating software
Cerebellis lists the operational requirements a traceability tool must meet regardless of vendor: every consumption must be linked to an identified incoming lot, including partial consumptions. The whole chain must be navigable in both directions without intermediate export. Every action must be time-stamped with the identity of its author so values cannot be silently overwritten. Equipment and its metrology status must be linked to the production runs it served, so a drifting instrument can be traced to affected lots. Deviations must be recorded when they occur, with justification, rather than reconstructed from memory afterward. Finally, the destination of shipped lots must remain connected to manufacturing data, so a recall does not force cross-checking two systems by hand.
These requirements are testable, and Cerebellis suggests a concrete exercise: take a lot shipped more than six months ago and time the answers to six prompted questions. A few minutes means the traceability is navigable; half a day or more means it is documented but not usable. The same logic applies across products. Critical Manufacturing, whose Genealogic application is built on MES data, names the operational scenarios directly: backward traceability for root cause detection and forward traceability to see affected products downstream when a supplier recall or bad material lot is identified. A genealogy tool that cannot answer both directions on one screen leaves the investigator assembling the story from LIMS, QMS, and ERP records separately.
Evidence-grade checks for shortlisting
For product chain genealogy in a medical device manufacturing context, prioritize evidence of backward and forward navigation on one screen, not screenshots of compliance icons. Ask the vendor to trace a six-month-old shipped lot in both directions during a demo, with partial consumption and at least one split lot included [4][2]. Check whether the audit trail records who changed each relationship and when; Cerebellis requires timestamping every action with author identity, and Mareana claims durable, immutable nodes and edges, but the proof is in what can be retrieved during an audit [4][1].
Do not accept standard names alone. Confirm whether the system's claimed EU MDR or ISO 13485 support covers the records your inspectors actually ask for: economic operator identification and technical documentation for MDR, versus lot-level consumption records under ISO 13485 [4]. If the tool sits inside an MES, clarify whether complaint, CAPA, and change control links live in the same system or require a second platform; the boundary will determine whether a quality record audit can be completed without hand reconciliation [7].
Architectural differences: MES-native, graph-based, and module-linked
The products differ in where genealogy data originates and how rigid the model is. Critical Manufacturing's Genealogic claims to provide traceability and production history from MES data, with a Graphical Genealogy Explorer for expanding or narrowing searches across related lots, components, and processes. Its stated focus industries include semiconductor, electronics, medical devices, and industrial equipment. Mareana, by contrast, markets Batch Genealogy as a knowledge graph that ingests ERP, MES, LIMS, and historian systems into a unified layer, with immutable nodes and edges that link raw material, process, and finished good entities. Mareana specifically claims support for paper and siloed OT data, a distinction that matters in device manufacturing where legacy paper batch records persist.
Zometric takes a third approach: Thread is a separately licensed traceability layer that weaves data from Inventory, Production, and Quality modules and can connect to SAP, Oracle, and third-party MES through APIs. It advertises sub-lot and split-lot genealogy with exportable reports for audits. Zometric names IATF 16949, 21 CFR Part 11, FDA, EU MDR, and ISO 13485 as supported standards. However, Zometric's marketing positions Thread as a decision support layer for questions like "Which supplier lot caused this customer return?" The important comparison is not which product lists the most standards, but whether the tool's audit trail is immutable and whether the material events are captured automatically or entered manually after the fact.
Where the product boundaries actually sit
The GHP News comparison organizes tools by which traceability chain each holds, and the boundaries are unusually candid. Critical Manufacturing is placed in the product chain, with non-conformance, CAPA, and change control inside the manufacturing system but no requirements, risk, or verification traceability. Orcanos is described as holding design and quality-record chains in a single data model, with device history records and lot tracking also present, meaning production records sit alongside design and quality chains rather than in a separate system. Tulip, by its own statement in the GHP News account, stops at product traceability; its platform produces electronic device history records tied to serialized devices or lots, while documents and CAPA sit beyond the product boundary.
These boundaries should shape procurement, not simplify it. A manufacturer whose primary pain is bounding a recall within production may find Critical Manufacturing or Tulip proportionate. A manufacturer whose audit findings point to broken links between complaint, CAPA, change control, and retraining may find that a better MES-native genealogy tool does not address the actual finding. The vendor pages themselves support this difference. Slingshot Pharma, aimed at pharmaceutical clients, describes lot genealogy and GS1 event capture alongside DSCSA and 21 CFR Part 11 support, which is adjacent to device needs but not equivalent. Reading one vendor's compliance list against another's without checking which records are linked within the same data model is a category error.
A concrete evaluation: one complaint, two directions
A useful evaluation might be built around a single imaginary event, clearly labeled as a suggestion rather than a tested workflow. Suppose a finished electrophysiology catheter, serialized and shipped eleven months ago, returns with a complaint about a distal tip bond. A backward traceability query should identify every incoming lot of adhesive and catheter shaft material, the bonding equipment, its calibration records, the operator shift, and any logged deviation, all from the serial number without exporting from one system to another. A forward query from a suspect adhesive lot should list every finished catheter lot and dispatch destination that consumed material from that lot. If partial consumptions are recorded, the forward list should include lots that received a split portion, not only full-container issuances.
The same exercise exposes the difference between a tool that records genealogy and one that enables response. Cerebellis's six-minute test and Zometric's prompt examples both describe the finished answer, but the evidence for speed is vendor-sourced and unverified. A manufacturer evaluating Critical Manufacturing could run the complaint scenario against MES history and ask whether the graphical explorer can display a rework loop, split lot, or by-product without flattening the path into a lossy table. A manufacturer evaluating Mareana could ask whether paper batch records are actually ingested and linked automatically, or whether manual entry remains the practical path. The test should be scored on how quickly an investigator can produce the complete chain with supporting evidence, not on how many rows the system stores.
Sources & references
- Batch Genealogy - Mareana · mareana.com
- Genealogic - Critical Manufacturing · www.criticalmanufacturing.com
- Thread: Traceability Software with Full Material Genealogy · Zometric · www.zometric.com
- Medical device traceability: lot tracking software | Cerebellis · cerebellis.com
- Product Genealogy & Traceability Software | Tulip · tulip.co
- Lot Genealogy and GS1 Traceability | Slingshot Pharma · www.slingshotpharma.com
- 6 Best Traceability Software for Medical Device Compliance - GHP News · ghpnews.digital