QR Code Model 1, Model 2, Micro QR, and rMQR: What Scanners Recognize

Published 2026-08-19 · Updated 2026-08-19

Scanner compatibility differs across QR Code Model 1, Model 2, Micro QR, and rMQR. Model 2 is the practical default for a general public scan, while older Model 1 and specialised Micro QR or rMQR marks require decoder testing against the exact devices and software that will read them.

The decision for QR-family scanner compatibility

QR-family scanner compatibility has one specific operational purpose: a compatibility matrix showing which supported reader decodes the approved printed sample. The controlled input is the symbol family, encoder settings, device model, reader application, and test image. Micro QR versus rMQR chooses a constrained shape; this guide maps all four families and asks whether the reader, rather than the artwork, recognises that family. The relevant current source is ISO/IEC 18004:2024 QR Code specification at https://www.iso.org/standard/83389.html.

The concrete case behind QR-family scanner compatibility

Use the stated case—a plant has 14 handheld readers, 6 kiosk imagers, and visitors' phones, so it tests each family before choosing one label standard—as the acceptance sample. Its figures, 14 handheld readers; 6 kiosks; 1 public-phone group; 4 symbol families; 1 documented acceptance matrix, belong to this record and should be checked against the symbol family, encoder settings, device model, reader application, and test image before release. separate geometry from compatibility.

Compatibility is a matrix, not a family name

List Model 1, Model 2, Micro QR, and rMQR as separate test rows, then list every deployed decoder as columns. A plant with 14 handhelds, six kiosk imagers, and public phones has 21 reader contexts, not one generic ‘QR scanner’. ISO/IEC 18004 covers QR Code, while ISO/IEC 23941 specifies rMQR; a decoder that reads an ordinary Model 2 mark does not thereby implement every related format. Record reader model, software version, symbol family, payload, print material, and result for each acceptance scan. try the output with the site reader.

Separate geometry failure from decoder failure

Use the same short identifier in a well-printed Model 2 control and in the proposed Micro QR or rMQR symbol where their capacity permits. If the control scans but the specialised symbol does not, inspect decoder support and symbol construction before changing the business data. If neither scans, investigate contrast, module size, quiet area, damage, camera focus, and lighting. This paired test avoids the common mistake of declaring rMQR unsupported after testing a cramped or distorted label, or declaring it supported after one clean screen preview. choose a QR payload format.

Choose one release baseline

For a public sign, Model 2 is normally the compatibility baseline because the audience's phone population is uncontrolled. For a closed fleet, approve a specialised family only after every required reader passes the final printed sample; record the fallback if one device is replaced. Do not let a new phone's success override an older scanner that remains in service. The deliverable is a compatibility matrix and a defined allowed symbol family, not a claim that every square or rectangle called QR will work everywhere. diagnose an unreadable proof.

Case ledger for QR-family scanner compatibility

The working case is a plant has 14 handheld readers, 6 kiosk imagers, and visitors' phones, so it tests each family before choosing one label standard. Its measured scope is 14 handheld readers; 6 kiosks; 1 public-phone group; 4 symbol families; 1 documented acceptance matrix. The retained input is the symbol family, encoder settings, device model, reader application, and test image; the observable outcome is a compatibility matrix showing which supported reader decodes the approved printed sample. Micro QR versus rMQR chooses a constrained shape; this guide maps all four families and asks whether the reader, rather than the artwork, recognises that family.

Failure boundary for QR-family scanner compatibility

Calling every square pattern a QR Code, relying on an encoder preview, or approving a family from one new phone while ignoring installed scanners No QR-family symbol can make an obsolete decoder implement a newer specification or make a damaged printed mark acceptable.

Decision record for QR-family scanner compatibility

a deployment owner responsible for readers in the field should retain the case, the figures, the controlled input and the observed outcome together. The next review begins with the symbol family, encoder settings, device model, reader application, and test image and verifies a compatibility matrix showing which supported reader decodes the approved printed sample; it does not infer a new decision from an old image.

Acceptance evidence for QR-family scanner compatibility

Use the case facts exactly as stated: a plant has 14 handheld readers, 6 kiosk imagers, and visitors' phones, so it tests each family before choosing one label standard. Keep 14 handheld readers; 6 kiosks; 1 public-phone group; 4 symbol families; 1 documented acceptance matrix beside the approval, then compare the resulting record with the symbol family, encoder settings, device model, reader application, and test image. The only relevant end state is a compatibility matrix showing which supported reader decodes the approved printed sample. This separates the specific error—Calling every square pattern a QR Code, relying on an encoder preview, or approving a family from one new phone while ignoring installed scanners—from the separate limit that no qr-family symbol can make an obsolete decoder implement a newer specification or make a damaged printed mark acceptable. The evidence is useful only for this comparison: Micro QR versus rMQR chooses a constrained shape; this guide maps all four families and asks whether the reader, rather than the artwork, recognises that family.

Release note for QR-family scanner compatibility

The release concerns a plant has 14 handheld readers, 6 kiosk imagers, and visitors' phones, so it tests each family before choosing one label standard. It is bounded by 14 handheld readers; 6 kiosks; 1 public-phone group; 4 symbol families; 1 documented acceptance matrix; that numerical context belongs with the approved record rather than in an informal message. The approved record is the symbol family, encoder settings, device model, reader application, and test image, and its required destination is a compatibility matrix showing which supported reader decodes the approved printed sample. The receiving role is a deployment owner responsible for readers in the field. Before release, document the exact observed result against those facts and inspect the stated failure condition: Calling every square pattern a QR Code, relying on an encoder preview, or approving a family from one new phone while ignoring installed scanners If that condition appears, use the limitation already established for this route: No QR-family symbol can make an obsolete decoder implement a newer specification or make a damaged printed mark acceptable. The comparison remains material to a later reviewer: Micro QR versus rMQR chooses a constrained shape; this guide maps all four families and asks whether the reader, rather than the artwork, recognises that family. This note preserves the factual chain from the physical item or public route to the decision that follows it.

Follow-through for QR-family scanner compatibility

The resulting work item remains tied to a plant has 14 handheld readers, 6 kiosk imagers, and visitors' phones, so it tests each family before choosing one label standard, not to a generic scan metric. Use the symbol family, encoder settings, device model, reader application, and test image to find the relevant record and compare it with a compatibility matrix showing which supported reader decodes the approved printed sample. Preserve 14 handheld readers; 6 kiosks; 1 public-phone group; 4 symbol families; 1 documented acceptance matrix with the observation. When the exception is Calling every square pattern a QR Code, relying on an encoder preview, or approving a family from one new phone while ignoring installed scanners, apply the stated limit—No QR-family symbol can make an obsolete decoder implement a newer specification or make a damaged printed mark acceptable.—before changing the route or artwork. Micro QR versus rMQR chooses a constrained shape; this guide maps all four families and asks whether the reader, rather than the artwork, recognises that family. ISO/IEC 18004:2024 QR Code specification is the named source for the current external rule or product behaviour.