Book a consultation

Cognex Machine Vision Applications: What Vision Does on a Plant Line

Cognex Serialization on Pharmaceutical Lines: What Vision Supplies

Cognex serialization on pharma lines: DSCSA and EU FMD, code reading, grading, aggregation, validation, and what Cognex and the integrator each supply.

Vladimir Romanov


Cognex serialization is not a Cognex product. It is the vision layer of a pharmaceutical serialization line: cameras and readers that check that each printed code exists, reads and matches, and verifiers that grade the print. The serial numbers, the parent-child records for cases and pallets, and the reporting to regulators’ systems come from other software. This page explains where Cognex’s devices sit, what the rules ask of the line, what validation adds, and who supplies what. It belongs to Cognex machine vision applications in the Cognex hub.

This is an engineering overview, not regulatory advice, and Cognex statements are attributed. Dates and rules are as of November 2026.

What the rules ask of the line

RegimeWhat it requires of packs, as we read the sourcesStatus as of November 2026
DSCSA (US)Product tracing with unique identifiers at pack level and electronic exchange of dataEnhanced distribution requirements took effect 27 November 2023. FDA has since granted exemptions, and on 6 August 2026 announced an extension of the small-dispenser exemption to 27 November 2027
EU FMDA unique identifier encoded in a 2D Data Matrix (product code, serial number, batch number and expiry date, plus a national reimbursement number where a Member State requires one), and an anti-tampering device. The identifier data is uploaded to a European data repositoryThe safety feature provisions entered into force on 9 February 2019 for almost all prescription-only medicines, under Delegated Regulation (EU) 2016/161
UDI (US devices)Unique device identifiers, a public database, direct part marks on some reusable devicesNot covered in depth here. Cognex names UDI as an application standard in its verifier manual

Sources: FDA exemption letter of 6 August 2026 and FDA exemptions page for the small-dispenser dates, FDA’s 2024 exemption letter for the 27 November 2023 effective date, MHRA on FMD and Delegated Regulation (EU) 2016/161 for the EU rules. We did not confirm manufacturer-specific DSCSA dates, which have applied for longer than the dispenser exemptions above, so check FDA directly. The UK position after Brexit is outside this page.

Blister packs of yellow tablets beside loose orange capsules on a pale surface
Each blister pack, carton and case carries a code that must print, read and match a record.

Where vision sits on a serialization line

Four jobs use vision, each named in the research as a standard pharmaceutical application:

  1. Print and check the 2D code on each unit. A printer applies a Data Matrix with a unique serial. A camera or reader decodes it straight away and compares the data to what the system sent to the printer. Mismatches and no-reads are rejected.
  2. OCV of lot and expiry. The human-readable text is read and verified against the batch record.
  3. Aggregation. Readers scan unit codes as they enter a case, then the case code, and the software builds the parent-child record. A missed read here corrupts the record upwards.
  4. Presence checks. Leaflet present, label present, tamper-evident seal intact.

An illustrative aggregation sequence. Units pass a reader that records each code. A case is closed. The case label is printed and read, and the software links the unit codes to the case code. If a unit code was missed, the case is rejected before it is labelled, because a label on a wrong record is worse than a reject. The PLC owns the timing of that decision, which is why the handshake design from the PLC integration page matters on these lines.

Reading versus grading

A grade is a measurement, not a read result. A verifier grades print quality under defined lighting. Cognex’s DM475 verifier manual names ISO/IEC 15416 for linear codes, ISO/IEC 15415 for 2D codes on labels and ISO/IEC TR 29158 (AIM DPM) for direct part marks, with ISO/IEC 15426-2 for the verifier’s own requirements. Grades run from A to F. The manual also lists GS1, UDI and HIBCC as application standards, and states that ISO-compliant grading needs the label, DPM or HD lighting accessory. Other lighting gives “Standards-Based Grading” only (DM475 manual). Cognex states it grades up to 20 codes per second.

What to take from that. If the contract asks for a grade, the grade must be measured with a verifier set up as the standard requires. An in-line reader that reports “read OK” has not graded anything. Whether a given reader or camera qualifies as an ISO-compliant verifier is a per-product question, so ask for it in writing. The barcode verification page has the detail.

Who supplies what

Who supplies what in a serialization stack Four layers from the line up. At the bottom, devices: printers, cameras, readers and verifiers, where Cognex supplies the vision devices. Above, the line controller and line integration, supplied by the integrator or machine builder. Above, line-level serialization software that generates serials, builds aggregation records and manages rejects. At the top, enterprise serialization software that connects to trading partners and regulators' systems. Enterprise serialization (often called Level 4) repository, trading partners, regulators' systems Line and site serialization software (often called Level 3) serial numbers, aggregation records, reject handling Line controller and integration PLC, handshakes, reject timing, job selection Devices: printers, cameras, readers, verifiers the vision devices are the Cognex layer Integrator or machine builder joins the device layer to the software and validates the line The level numbers are the common industry shorthand, our reading, not a Cognex statement.
Cognex sits at the bottom of the stack. Everything that makes the serial numbers legally meaningful sits above it.
LayerWho supplies itNotes
Cameras, readers, verifiersCognex (or a competitor)Models differ in protocols and grading features
Printers and applicatorsPrinter vendorInkjet, laser, thermal transfer
PLC logic and handshakesIntegrator or machine builderTrigger, result, reject, job change
Line and site serialization softwareA serialization software vendorGenerates serials, builds aggregation records
Enterprise software and exchangeSame or a separate vendorTrading partner and regulator connections

One public example, from an older trade article: Seidenader’s Process Manager, line-level serialization software, is described as designed to configure and manage Cognex In-Sight technology and as reducing administration and validation expense (Pharmaceutical Online). That is a vendor and integrator claim, not an independent result.

Validation considerations

GAMP 5 and risk. The ISPE GAMP 5 Second Edition (July 2022) is industry guidance on a risk-based approach to computerised systems in regulated settings. It is guidance, not regulation (CASRAI summary).

21 CFR Part 11 covers electronic records and signatures, and applies where a vision system creates or holds regulated records such as inspection results, recipe changes and audit trails. We describe it here without a link to the regulation text because we did not open the primary page for this review. FDA’s February 2026 Computer Software Assurance guidance covers computers and automated data processing systems used in medical device production or the quality management system, in the context of 21 CFR Part 820. Its FDA page does not mention Part 11, so do not treat it as Part 11 guidance (FDA).

Considerations for a vision station. This is our synthesis, not a Cognex or FDA statement:

  1. User roles and password control on the camera or reader
  2. An audit trail for configuration and job changes
  3. Locked, versioned job files and a backup of each
  4. Result and image retention that matches the record rules
  5. Time synchronisation across devices
  6. A challenge test with known-good and known-bad samples at qualification, repeated periodically
  7. Change control when a lens, light or camera is replaced

For smart cameras, the vendor’s tools may not provide all Part 11 features by default. Whether specific Cognex products do is unverified here, and must be checked with Cognex.

Where it gets hard

  • Aggregation errors travel upward. One bad read corrupts the case and pallet record above it.
  • Grading needs the right lighting. Reading successfully is not grading, and the wrong lighting gives only an approximation.
  • 2D support is per model. Which Cognex models read and parse GS1 2D codes was not verified.
  • Validation is a project. The documentation, qualification and change control often cost more than the devices.
  • Rules change. Exemptions and dates move. Check FDA and the EU sources before relying on this page.

See systems integration, commissioning support, and the sibling pages on packaging inspection and food and beverage inspection.

Frequently asked questions

What does Cognex supply on a serialization line?

Cognex supplies the vision hardware and its tools: cameras and code readers that check printed codes, and verifiers that grade them. It does not supply the serialization data. Serial number generation, aggregation records and reporting to repositories come from line-level and enterprise serialization software, joined to the line by an integrator.

Does DSCSA require a vision system?

DSCSA sets traceability requirements, not specific equipment. A manufacturer meets them with whatever combination of printers, readers and software it validates. In practice, reading and checking each printed code is how a line proves that what was printed is what the system recorded. FDA, not the vendor, defines the requirements.

What is the difference between reading and verifying a 2D code?

A reader decodes the code. A verifier grades its print quality against a named standard, such as ISO/IEC 15415 for 2D labels, under specified lighting. A code can read successfully and still grade poorly. Cognex states its DM475 verifier needs the standard's lighting accessory for ISO-compliant grading.

Do Cognex cameras meet 21 CFR Part 11?

We could not confirm this for specific Cognex products, so do not assume it. Part 11 applies to the electronic records a system creates and keeps, such as inspection results, recipe changes and audit trails. Ask Cognex which user-access, audit-trail and record-retention features each product provides, and plan to cover gaps in the surrounding system.

References and further reading

  1. FDA: Exemptions under the Drug Supply Chain Security Act (DSCSA) · U.S. Food and Drug AdministrationThe current exemptions and dates for dispensers.
  2. FDA: Computer Software Assurance for Production and Quality Management System Software · U.S. Food and Drug AdministrationFebruary 2026 guidance for device makers in the context of Part 820. Its page does not mention Part 11.
  3. FDA: DSCSA exemptions for small business dispensers until 27 November 2027 (letter of 6 August 2026) · U.S. Food and Drug AdministrationThe date of the extension and the 25-employee definition.
  4. Commission Delegated Regulation (EU) 2016/161 · EUR-LexArticles 4 and 5 on the unique identifier and the 2D Data Matrix.
  5. Falsified Medicines Directive safety features · MHRA InspectorateThe EU FMD 2D code and anti-tampering requirements.
  6. DataMan 475 Verifier Reference Manual · Cognex documentationThe standards named, the lighting rule and Standards-Based Grading.
  7. Smart cameras reduce implementation and validation costs in pharmaceutical serialization · Pharmaceutical OnlineA vendor and integrator account of Cognex cameras in serialization software.
  8. GAMP 5 Second Edition changes · CASRAIA secondary summary of the ISPE guide.

← Applications

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.