Processed locally
Your input stays in this browser.
Micro QR and rMQR are QR-family symbols designed for constrained marking areas: Micro QR reduces the symbol for small payloads, while rMQR uses a rectangle for narrow spaces. Use either only when the required readers support it; ordinary Model 2 QR Code remains the safer compatibility choice for a public phone scan.
The specific decision in geometry
Micro-QR and rMQR constrained label belongs to geometry. Evidence means module pitch, ink spread, and the long edge of a cable marker. The controlled value is the required payload, module size, aspect ratio, and decoder support list. a label designer working with a specified scanner fleet needs a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability; a decorative scan is irrelevant. Physical QR size guidance calculates a normal symbol; Micro QR and rMQR change the symbol family when a square Model 2 mark itself is the constraint. The physical mark must therefore answer this one operational question, not a neighbouring question with similar-looking bars or modules.
Facts to establish before using Micro-QR and rMQR constrained label
In geometry, put the required payload, module size, aspect ratio, and decoder support list first. Add module pitch, ink spread, and the long edge of a cable marker next. State a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability in the local procedure. The figures are 9 mm square area; 6 by 24 mm rectangular area; 2 payload shapes; decoder support tested before release. ISO/IEC 23941 rMQR specification at https://www.iso.org/standard/77404.html defines the outside terminology. Use that wording in the data contract before artwork, reader settings, or an import map is touched. calculate a readable module size.
| Constraint | Micro QR | rMQR |
|---|---|---|
| Shape | small square | long rectangle |
| Best check | decoder support plus print sample | decoder support plus print sample |
| Fallback | standard QR if space permits | standard QR if space permits |
Worked case: a 9 mm square service label holds a short identifier, while a 6 by 24 mm cable label has a long narrow printable zone
Here is the case: a 9 mm square service label holds a short identifier, while a 6 by 24 mm cable label has a long narrow printable zone. Its figures are 9 mm square area; 6 by 24 mm rectangular area; 2 payload shapes; decoder support tested before release. Match the source entry to the required payload, module size, aspect ratio, and decoder support list. Create the selected carrier. Observe a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability. A successful decode does not correct a wrong product row, a laboratory mismatch, a shipping mix-up, or an inaccessible response route. check a generated test image.
How the relevant data is read
geometry is read through module pitch, ink spread, and the long edge of a cable marker. That rule sends the required payload, module size, aspect ratio, and decoder support list toward a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability. a label designer working with a specified scanner fleet should explain each character without a guessed prefix or a software preview. Separators, zero fill, guards, direction, and field width can each carry operational meaning. Treat those details as data rather than presentation. make a short identifier code.
Errors particular to geometry
These geometry mistakes matter: Selecting rMQR because it looks efficient without testing readers, forcing a square mark into a rectangular space, or reducing modules until ink spread removes their separation In a 9 mm square service label holds a short identifier, while a 6 by 24 mm cable label has a long narrow printable zone, repair the source record before making another symbol. A fresh export does not repair old data. Compare the repaired value with the required payload, module size, aspect ratio, and decoder support list. Then repeat the step that should produce a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability. keep a constrained-label proof.
Where the method stops
A smaller symbol family cannot overcome insufficient module contrast, a scanner without rMQR support, or a payload that exceeds the selected symbol capacity. This limits geometry. The nearby comparison is different: Physical QR size guidance calculates a normal symbol; Micro QR and rMQR change the symbol family when a square Model 2 mark itself is the constraint. A calculation has one role; an optical read has another; a web answer has another. Allocation, custody, clinical judgement, authenticity, and partner approval require their own accountable process.
Technical case notes for geometry
A 9 mm square service label and a 6 by 24 mm cable marker fail for different geometric reasons. Micro QR suits the short square payload; rMQR offers a rectangular family, but the scanner fleet must support it before a narrow label is released. Measure the smallest printed module after the actual ink, laser, or thermal process has spread it, then scan ten production samples rather than the encoder's clean screen preview. A rectangular symbol does not rescue a payload that is too long, a quiet area that has been trimmed away, or a decoder that recognises only Model 2 QR.
What the result requires next
After the geometry result, use the required payload, module size, aspect ratio, and decoder support list to locate the affected record. Let 9 mm square area; 6 by 24 mm rectangular area; 2 payload shapes; decoder support tested before release define the check. Let module pitch, ink spread, and the long edge of a cable marker define the interpretation. a label designer working with a specified scanner fleet should receive a production-tested symbol whose dimensions fit the available label without shrinking modules below the print process capability. If that result fails, the next action comes from this case — a 9 mm square service label holds a short identifier, while a 6 by 24 mm cable label has a long narrow printable zone — rather than from Physical QR size guidance calculates a normal symbol; Micro QR and rMQR change the symbol family when a square Model 2 mark itself is the constraint.. The correction must be documented against ISO/IEC 23941 rMQR specification, because a later operator needs the same factual basis instead of an informal description of a scan.
Choose a constrained symbol from measured geometry, not from its preview
A 9 mm square maintenance sticker and a 6 by 24 mm cable marker are different engineering problems. The square can carry a short local identifier in Micro QR if the specified reader supports Micro QR; the narrow marker may suit rMQR because ISO/IEC 23941 defines its rectangular formats, encoding and print-quality requirements. Start with the payload, including every character that the receiving record actually needs. Draw the quiet area and the final module pitch at the printer's real resolution, then examine ten production samples rather than a perfect on-screen SVG. Thermal transfer spread can close a light gap; ink can widen a dark module; a laminate edge can remove the quiet area. Keep a normal Model 2 QR control on the 9 mm label where space permits. If Model 2 scans but rMQR does not, the evidence points to decoder support or the rectangular artwork, not to the data record. A smaller family does not compensate for a long URL, poor contrast, or a fleet that only recognises ordinary QR Code. ISO/IEC 23941 rMQR specification is the named source for the current external rule or product behaviour.