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

Unique and sequential identification
Variable identifiers, counters and machine-readable codes connected to the production data and line controls that govern each item.
Variable data on the product
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.
Serial printing should define number ownership, acknowledgement and failure handling.Data ownership
Suitable for straightforward counters where the printer can own the sequence and reset rules.
A PLC supplies the variable field in step with machine cycles and product handling.
A controlled application allocates identifiers and records their production status.
Production orders and serial data flow from MES or other business systems through an agreed interface.
Controlled sequence
The final design changes with the risk, but the handshakes should be unambiguous.
Integration interfaces
| Interface layer | Typical purpose | Project question |
|---|---|---|
| Digital I/O | Trigger, ready, fault, print complete or line stop | Which signal owns the product cycle? |
| Serial or Ethernet | Message selection and variable-field transfer | How is successful receipt acknowledged? |
| PLC or HMI | Recipe control and operator workflow | Who may change a job or data field? |
| Database or MES | Order, serial and production-result records | What happens during loss of connection? |
| Vision system | Presence, content, quality or code verification | What decision stops or rejects a product? |
Serial printing FAQs
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.
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.
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.
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
Plan symbol choice, data construction, print quality and inspection.
2D code guideCoordinate records, triggers, printer states, cameras and reject handling.
Integration guideVerify that unique codes remain readable through handling and use.
Substrate guideDescribe the identifier, code type, volume, line control and record requirement. Oxford Traceability can help scope the printing and integration layers.