Are there QR code registration requirements for vision systems?

You plan to print a QR code carrying station, recipe or routing data on your own parts and have a camera decode it to drive the machine. The question that stalls the project: does someone have to approve or register that code, the way a JAN number on a retail pack is registered? The answer is no, and the distinction is worth getting exactly right, because one code in your plant still does need registration — the trade item number on a shipping carton. The sections below give the rule, the standard behind it, the numbers to size the symbol, and a sign-off test for your own line.

Do QR codes need registration before a camera can read them?

No. A QR code carries no registration requirements of any kind: the symbology is published as the open international standard ISO/IEC 18004, and no authority approves, licenses or keeps a registry of the codes you print for your own line.

The confusion comes from the JAN code on a retail pack. A JAN or EAN-13 number is a globally unique trade item identifier issued under license from GS1, and that registration attaches to the number, not to the bars. The EAN/UPC barcode format itself is an equally open standard (ISO/IEC 15420) that anyone may print or decode. Your control payload — OP=2;LINE=B;REV=03 — identifies nothing outside your plant, so there is nothing to register and no fee to pay. Generate the symbol, print it, and any conforming fixed code reader decodes it.

Who owns the QR Code, and can it charge you for using it?

No one can charge you for printing or reading QR codes. The company that invented the symbology in 1994 holds patents on it and a trademark on the name, but it has published a declaration that it will not exercise those patent rights against implementations of the published specification.

The symbology was standardized soon after its invention: ISO/IEC 18004 first appeared in 2000 and was revised in 2006, 2015 and 2024 (ISO catalogue entry, ANSI announcement of the 2024 edition). Encoders and decoders exist for every language and platform, and every industrial reader and phone camera decodes the same symbol. Licensed proprietary 2D formats do exist; QR is not one of them. The trademark covers the term, not the technology: describing your mark as a QR code on a drawing or in a manual needs no permission from anyone.

When does a code on your part actually require registration?

Registration enters only through the data, never through the QR symbol: if your payload is a GS1 trade number such as a JAN, EAN-13 or GTIN — or a GS1 Digital Link URI aimed at consumer scanner apps — the number inside must be licensed from GS1, while the code format itself stays free.

Sort your payloads into two bins. Internal data — station number, recipe index, routing flag, your own serial scheme for traceability — needs nothing from anyone: you define the field layout, document it in your own records, and change it whenever the line changes. Commerce data needs GS1: a JAN/EAN-13 on a shipping carton, a GTIN inside a QR code consumers will scan, or the regulated serialization schemes used in industries such as pharma. Even there the symbology stays free; the obligation is to license the company prefix and allocate numbers to GS1's rules. The code on your workpiece carrier sits in the first bin.

What does ISO/IEC 18004 actually specify?

It specifies the symbol, not your rights: version 1 measures 21 × 21 modules and the grid grows to 177 × 177 modules at version 40, error correction levels L, M, Q and H recover roughly 7, 15, 25 and 30 percent, and four encoding modes cover numeric, alphanumeric, byte and Kanji data.

Everything a reader needs to find and decode the mark is fixed by the standard: the three 1:1:3:1:1 finder patterns, the timing pattern, the masking rules and the encoding modes. Nothing in it constrains what your payload must mean, so your field layout stays entirely yours. Your obligations are to print a conforming symbol and to keep the quiet zone — 4 clear modules on every side — because that margin is what lets the finder pattern detection work at an angle or slightly out of focus.

How much control data fits, and which error correction level should you set?

A short control payload fits with room to spare: byte mode holds 26 characters at error correction M in a version 2 symbol of 25 × 25 modules, and 42 at version 3 (29 × 29), so a 10-to-25-character recipe or routing string needs no larger code.

Byte-mode capacity per ISO/IEC 18004, in characters per symbol:

Set level M as the default on a clean printed label, and step to Q where codes scuff, collect dust or face washdown — the fixes for damaged, low-contrast codes apply unchanged to self-defined payloads. Resist inflating version or correction level to be safe: at a fixed print size, more modules mean smaller modules, and smaller modules mean fewer pixels per module. For a control string of up to 26 characters, version 2 at level M is the committed choice.

How small can you print the code for your camera to read it?

Size the print from pixels, not from habit: give each module at least 3 pixels at the sensor, which for a 60 mm wide field of view on a 1600-pixel reader means modules no smaller than 0.11 mm, and makes a 0.40 mm module comfortable at 10.7 pixels.

Size your own camera against the print with the camera resolution calculator:

When the smallest module is fixed and the field of view cannot shrink, buy sensor pixels instead of print size. The LS-CRD-0028 pairs a 2560 × 2048 sensor with an 8 mm lens and reads up to 60 codes per second. At the same 60 mm field of view that sensor delivers (0.40 / 60) × 2560 = 17.1 pixels per module, nearly six times the floor.

How do you verify the read before you commit to the format?

Run a sign-off test before the format reaches the drawing: print the worst-case payload, read it 100 times at line speed, then repeat with the exposure doubled, the code tilted 30 degrees and the window misted — if every pass decodes cleanly, lock the format.

Verification is a print-quality problem before it is a software problem. ISO/IEC 15415 grades printed 2D symbol quality on contrast, modulation and similar parameters, and industrial readers report their own decode confidence, so record both during the test (judging whether a decode is trustworthy, the verification workflow for label inspection). On glossy carriers or shrink wrap, glare replaces damage as the dominant failure mode; polarized lighting and lens covers from the code reader accessories range address exactly that, and the playbook for reflective and curved surfaces transfers directly. The MV-IDB005EXI-05NRP is a polarized 1.3 MP reader with a 4.63 mm lens focused at 70 mm.

When is a QR code the wrong choice for control data?

Keep QR for printed labels: Data Matrix packs the same data into a smaller mark and is the standard choice for direct part marks, while any payload that identifies a trade item globally belongs in a GS1 number, not in a private string.

Four cases decide it. A paper or polymer label with modules of 0.3 mm and up: QR, sized as above. A mark etched or laser-dotted straight onto metal with modules below 0.2 mm: Data Matrix (ISO/IEC 16022, equally open and free) — and read up on mirrored Data Matrix codes, because direct part marks produce them. A payload consumed by anyone outside your plant, such as retailers, service networks or regulators: a GS1-registered number in the appropriate carrier. A decode that must trigger machine logic with no PC in the loop: a smart camera runs the decode and its outputs on the device.

Which reader should you start with for a control-code station?

Start from field of view and mounting distance, not from feature lists: pick a reader whose fixed lens focuses at your stand-off, confirm 3 pixels per module with the calculator above, and choose Fast Ethernet or GigE output when the decode string travels to a PLC.

Three matches settle most stations. Optics: compact readers come with a spread of fixed focal lengths, so match the lens to the stand-off instead of moving the mount. Interface: Ethernet keeps the payload off discrete I/O wiring; plan the link before you drill the first hole (PLC communication planning for barcode readers). Cycle time: keep the ROI tight so the reader only processes the pixels it needs (ROI setup for inline code reading). The MV-ID3013PM-12M-WBN is a compact 1.3 MP code reader with a fixed 12 mm lens on an M12 mount and a Fast Ethernet interface — the class of part that bolts beside a station and hands the string to the PLC.

Browse the code reader finder, send your payload, print size and mounting sketch through the build-a-system configurator, or reach the team through the contact page if the format has to coexist with a customer's labeling standard.