DataMatrix vs QR on Vials: Test the Decoded Output

Choose the carrier only after the intended reader and application produce the required output.

A square code is often added to a small vial because it seems to solve the space problem. It may, but two square codes that look similar on a design board can serve very different tasks. Before choosing DataMatrix or QR, I would ask who scans the label, with what device, and what answer that person expects to get.

Suppose a receiving team wants a scanner to capture an internal item identifier and lot field. A consumer-facing QR journey to a web page is not the same requirement. Reversing them can leave a beautifully printed code that the intended device does not parse. The code decision belongs in the data and workflow brief, not at the end of graphic design.

Choose the workflow before choosing the symbol

GS1 distinguishes GS1 DataMatrix, Data Matrix with GS1 Digital Link and QR Code with GS1 Digital Link by data syntax and use. The distinction matters when a buyer expects GS1 identifiers such as GTIN, batch or expiry data. GS1 notes that GS1 DataMatrix is used extensively in supply-chain and healthcare workflows, while QR with GS1 Digital Link is suited to a web-compatible route and common phone-camera engagement. This does not mean every research vial needs a regulated healthcare code or that any QR automatically follows a GS1 standard.

Write the desired scan result in one plain sentence: "The receiving scanner should place our lot number in the inventory field," or "A phone should open the brand-owned instructions page." If there are two destinations, consider whether they really belong in one symbol. Confirm the scanner's symbology support and software configuration with the team that operates it. A printer can reproduce supplied artwork; it cannot infer an organization's data architecture from a tiny square on a PDF.

Make data ownership explicit

Who assigns the identifier? Who produces the variable-data file? Who checks that a repeated code has not slipped into a different vial variant? Who owns and maintains the landing URL if a QR is used? Those are separate responsibilities. Put a sample encoded string, human-readable text requirement and a version-controlled file format in the order brief. Never invent a GTIN, lot or expiration field merely because an example photo shows one.

If a web destination is involved, use a domain and path controlled by the brand, not a printer's temporary short link. Check what happens when a product is discontinued or the page changes. A printed code is persistent; a web destination may not be. For an authentication program, a code alone is not evidence of authenticity: copied artwork can carry the same printed symbol. The brand must design the response and back-end logic separately.

Test the real surface and the real device

On a small vial, neither symbol gets a free pass from curvature, glare or a label seam. Reserve a high-contrast flat-looking panel with the proper quiet area and avoid printing over a fold, shoulder or heavy metallic region. GS1's 2D barcode overview explains the carriers, but the actual print-size and quality target must be selected for the scanning environment. Ask for an applied sample on the actual glass and scan it in normal room lighting and under expected handling conditions.

A valid test uses the approved code content, production-representative material and the real reader. Keep failed scans in the record too; they often reveal whether the issue is code content, symbol size, contrast or application placement.

What to send with the custom-label request

Send the vial dimensions, label space, requested code type or scan purpose, scanner model, expected data fields, destination owner, artwork and quantity per version. Indicate whether the same label also needs a human-readable product name, lot or date. Ask the supplier to show both the flat proof and an applied-vial proof with space reserved for the code. The practical winner is not the symbol that looks smallest in isolation. It is the one that your intended scanner and operator can use without a workaround.

Sources and scope

Reviewed October 2, 2026. The primary references linked below support the identified technical points. Buying scenarios and inspection checklists are editorial guidance, not RP production records, certification, legal approval or universal acceptance standards.

Write the scan result before choosing the smaller square

Suppose the receiving team expects an internal item reference in a stock field. A candidate code scans, the device beeps, and the screen displays a whole string that the operator has to edit. That is a successful decode followed by an unsuccessful workflow. Changing from QR to DataMatrix may not fix it if the application still expects a different data format.

The practical brief is a scan contract: approved encoded input, chosen syntax, reader configuration, raw decoded characters, parser rule and expected destination field. Keep those separate. In the fictional worked record, DEMO-A17 is ordinary demonstration text. It is not a GTIN, a GS1 element string or a production-ready barcode payload. The expected business field can be described before a live test, but the actual decoded output must stay blank until someone observes it.

Ask the system owner to provide a representative payload and the required result. Have the reader owner capture the raw output before the application transforms it. Then let the software owner show what reaches the field or browser. A missing separator, unsupported syntax or unexpected prefix belongs in the record, with its next owner. Do not let the printer “correct” an identifier because it looks unusual.

Keep symbol approval and system approval distinct

The GS1 carrier comparison distinguishes data syntax as well as symbol type. It does not make a generic research vial a regulated healthcare item or guarantee support in the buyer's software.

A phone opening a brand page may favor a web-oriented route. A closed receiving system may favor a carrier and syntax its configured readers already handle. The reasonable winner depends on that task. If both work operationally, compare their physical footprint and applied readability using the actual data, rather than a low-density stock illustration.

Approve the useful output first, then qualify the printed sample on the intended vial. The record deliberately has separate spaces for a planned result and an observed result. It is much cheaper to discover a parsing dependency while the code is still a draft than after it has become a permanent part of the artwork.

Use the record for the actual inquiry

For an RP Labels inquiry, send the actual package and artwork references, quantity per design, the identified owners and the completed record for this decision. Ask which proposed print, sample and finishing scope can be confirmed and which dependencies remain open. Send the project details to RP Labels.