Industrial coding and traceability systems for UK production
Automated production line with conveyors and control equipment

Unique and sequential identification

Serial number printing systems

Variable identifiers, counters and machine-readable codes connected to the production data and line controls that govern each item.

Variable data on the product

Make each identifier accountable.

A serial number can be a simple incrementing code or part of a wider traceability architecture. The printer, controller and data source must agree which number belongs to which product and what happens if a print or communication fails.

The physical mark may be alphanumeric text, a barcode, QR code or Data Matrix. Code selection should follow the amount of data, available area, reader or camera, line speed, substrate and verification requirement.

  • Sequential numbers
  • Randomised identifiers
  • Product counters
  • QR codes
  • Data Matrix codes
  • Line and time data
Modern automated factory line suitable for data-connected codingSerial printing should define number ownership, acknowledgement and failure handling.

Data ownership

Choose where the identifier is created and recorded.

PRN

Printer generated

Suitable for straightforward counters where the printer can own the sequence and reset rules.

PLC

Line controlled

A PLC supplies the variable field in step with machine cycles and product handling.

DB

Database supplied

A controlled application allocates identifiers and records their production status.

MES

Enterprise connected

Production orders and serial data flow from MES or other business systems through an agreed interface.

Controlled sequence

One practical serial-printing flow.

The final design changes with the risk, but the handshakes should be unambiguous.

Production order selected
Identifier allocated
Product detected
Code printed and checked
Result recorded or line stopped

Integration interfaces

Connect only what the production process needs.

Interface layerTypical purposeProject question
Digital I/OTrigger, ready, fault, print complete or line stopWhich signal owns the product cycle?
Serial or EthernetMessage selection and variable-field transferHow is successful receipt acknowledged?
PLC or HMIRecipe control and operator workflowWho may change a job or data field?
Database or MESOrder, serial and production-result recordsWhat happens during loss of connection?
Vision systemPresence, content, quality or code verificationWhat decision stops or rejects a product?
Regulated application? Validation, audit trail, electronic records, aggregation and reporting requirements should be defined before the hardware architecture is approved.

Serial printing FAQs

Questions about unique codes and data.

Where can serial numbers come from?

They may be created by the printer, a PLC, a database, an MES or another authorised system. Ownership of number generation and the response to a communication failure should be explicit.

Can industrial inkjet print a QR or Data Matrix code?

Selected printers can produce 2D codes, but suitability depends on resolution, code size, product movement, substrate and the required verification grade. A trial is essential for a graded requirement.

How do you prevent a duplicate serial number?

The design can include controlled number allocation, acknowledgement, used-number recording and line-stop rules. The required architecture depends on whether the application is simple identification or regulated serialisation.

Is serial-number printing the same as pharmaceutical serialisation?

No. Pharmaceutical serialisation can require validated data, aggregation, audit trails, reporting and market-specific compliance. Those needs must be scoped as a complete traceability system, not assumed from printer capability alone.

Related variable-data guidance

Connect unique data to a readable, verified mark.

QR and Data Matrix printing

Plan symbol choice, data construction, print quality and inspection.

2D code guide

Production-line integration

Coordinate records, triggers, printer states, cameras and reject handling.

Integration guide

Substrate durability

Verify that unique codes remain readable through handling and use.

Substrate guide

Connect the code to the right data source.

Describe the identifier, code type, volume, line control and record requirement. Oxford Traceability can help scope the printing and integration layers.

Discuss your coding project
Call 01865 362785Send enquiry