Skip to main content

Device Manufacturing Traceability and Product Recalls

Production data (lot codes, work orders, firmware versions, hardware revisions) is typically captured at the factory and stored in ERPs or production management systems. The challenge emerges when a field issue requires correlating that data with devices deployed in the field: which specific units came from an affected batch, where they are, and who owns them.

Controlled recall vs brand-damaging crisis

When something goes wrong, the ability to identify the exact set of affected devices within hours is the difference between a targeted, controlled recall and a brand-damaging crisis.

Most critical for

Manufacturers with high-volume production runs (where manual cross-referencing becomes impractical), regulated industries where product safety incidents carry legal obligations (HVAC, medical-adjacent devices, industrial equipment), and any product line where a firmware bug or hardware defect requires a targeted OTA campaign or recall notice to a specific batch.

The challenge with manufacturing traceability​

Once a device leaves the factory, its production data (serial number, hardware revision, firmware version, lot code, work order) typically lives in a system that has no connection to the IoT platform managing the same device in the field. When a field issue emerges, reconstructing which units were affected requires manually cross-referencing production records with operational data across systems that were never designed to work together.

This creates specific operational and compliance problems:

  • Targeted recall is impossible without traceability: without knowing which lot a defective device came from, you cannot identify other devices in the same batch, meaning either a recall that's too broad (costly) or too narrow (leaving affected units in the field).
  • Support escalations are slow: when a customer reports an issue, the support team cannot immediately know whether the device is affected by a known production problem, because manufacturing data isn't accessible from the operational system.
  • Regulatory exposure: product safety regulations in the EU and elsewhere require manufacturers to be able to identify and contact owners of recalled products. A manufacturer who cannot reliably link a device's field identity to its production history cannot satisfy this obligation.
  • No bridge from manufacturing to cloud identity: the serial number on the box and the device ID in the cloud are often managed in separate systems with no reliable link between them.

What it takes to get it right​

Manufacturing traceability for connected products requires:

  1. A dedicated manufacturing data store, separate from the IoT operational data (telemetry, connectivity) but linked to it. Manufacturing attributes are recorded once, at production time, and should not be overwritten by operational updates.
  2. Complete historicization, every change to a device's manufacturing record is preserved, enabling reconstruction of the full production history at any point.
  3. Lot and batch linkage, each device record must carry identifiers (lot code, work order, pallet ID) that group it with others produced at the same time, from the same materials.
  4. Production line integration, the data must be captured at the factory, not entered retrospectively. This requires an API or CLI that fits into the existing production flow.
  5. Accessible from the operational system, the link between manufacturing data (Connhex Manufacturing) and cloud identity (Connhex Core) must be explicit and queryable, so support and operations teams can retrieve manufacturing data from a device ID without leaving the platform.

How Connhex solves it​

Connhex Manufacturing is a dedicated service for storing device manufacturing data throughout the production lifecycle: manufacturing, final assembly, testing, and packaging.

It ships with a default schema that covers the most common fields out of the box:

Identity informationTraceability information
FieldDescriptionFieldDescription
serialNumberDevice serial numberworkOrderProduction work order
partNumberProduct part numberproductionOrderProduction order identifier
pcbPartNumberHardware part numberpalletIdPallet identifier
fwVersionFirmware version at manufacturing timepackageIdPackage/box identifier
deviceTypeDevice type
connhexIdConnhex cloud identity

The schema is fully customizable: any additional fields relevant to your production process can be added without modifying the platform.

Product recall in practice​

The key capability is batch recall. Given a single defective device's serial number, Connhex Manufacturing can return the complete list of devices that share the same lot, work order, or production batch, in a single API call.

This means a recall operation that might otherwise take days of cross-referencing spreadsheets becomes a query. The result is the precise set of affected units: no more, no fewer.

Full historicization​

Every change to a device's manufacturing record is stored, not overwritten. This means the complete manufacturing history of any device, every state it passed through from production to packaging, is retrievable at any time. This is the audit trail that regulators and enterprise customers ask for.

Integration with the rest of the platform​

Connhex Manufacturing is not a standalone record system. It integrates directly with:

Production line integration is handled through the Connhex Manufacturing API or the open-source CLI, a command-line wrapper around the same API designed for use in factory automation scripts.

Relevant verticals​

Manufacturing traceability is most critical in industries with regulatory exposure or large deployed fleets:

Connhex for HVAC · Connhex for Industrial Washing Machines · Connhex for Vending Machines

Read the technical docs​

Know exactly which devices are affected, before the recall becomes a crisis.Serial numbers, lot codes, firmware versions, all linked, all searchable, from production to field.
Talk to us