Why do my merged InDesign product cards contain the wrong QR destination even though every code looks different?

Give the QR field a type and an intended payload

Adobe's workflow uses a CSV or TXT header prefixed with #, such as #QRCode. Web-link data uses URL: followed by the address. In Data Merge, select the source file, select the document's QR placeholder and choose Create Merged Document.

Treat the QR value as product data, not decorative artwork. Begin with the product identifier, the purpose printed beside the code and the approved destination. These three should describe the same merchandise and edition before producing variations.

Do not put a convenient file name or an internal note into the field and assume the merge will turn it into the right destination. The typed value needs to express the intended data. The example header is a documented pattern, not proof that an existing spreadsheet already follows it.

Open Window > Utilities > Data Merge, choose Select Data Source, and select the intended CSV or TXT. After selecting the QR placeholder, use Create Merged Document. Confirm that the loaded source is the approved record set before merging.

The typed-field syntax and merge entry are described in InDesign typed QR field headers and data-merge records.

Illustrative exercise A: each SKU needs its own instructions

A fictional catalog contains two similar kettles with different controls. Each card promises setup instructions for that model. Compare each source record's product identifier and typed address before merging, rather than copying one value down the QR column.

After generation, decode each resulting code and compare the payload with the intended record. Check both similar models deliberately: the code may be valid yet contain the other model's address. A visually different pattern is not a substitute for reading what it encodes.

If the second card points to the first kettle, inspect the source row and placeholder association before changing the printed symbol size. Fixing scan geometry cannot correct a wrong payload. Reassess the affected records after correcting the mapping.

These example addresses are intentionally nonworking and must not be printed. The URL: prefix specifies the input type in the merge field. In a real authorized test, compare the decoded destination with the approved address for that SKU. If KETTLE-B resolves to the kettle-a address, the mapping fails even if both symbols scan; inspect the source values and merge association before touching the artwork geometry.

Unexecuted illustrative CSV: reserved invalid example host, not a working campaign

SKU,#QRCode
KETTLE-A,URL:https://example.invalid/setup/kettle-a
KETTLE-B,URL:https://example.invalid/setup/kettle-b

Intended destinations to compare with an eventual decode; not observed output

KETTLE-A -> https://example.invalid/setup/kettle-a
KETTLE-B -> https://example.invalid/setup/kettle-b

Illustrative exercise B: a shared campaign destination is intentional

Another set of cards intentionally points to one campaign page. Equal addresses across several products may now be correct. Record that shared purpose and ensure the nearby invitation promises the campaign, not model-specific setup information.

Do not invent unique addresses merely to make every QR pattern different. Instead, decode the results and confirm that the repeated destination is the approved one. Then separately assess whether the page presents the right products and whether its use fits the campaign.

If a later brief changes the promise to product-specific care, revisit the record values. A previously accepted shared address does not automatically satisfy the new task, even if the same cards still decode successfully.

Separate payload checking from the physical proof

Use a comparison containing the SKU, source value, merged card and observed decoded payload. This localizes a mismatch without claiming that a successful merge has validated the whole customer journey.

Printed scanning and destination maintenance remain separate checks. A correct payload can still be poorly reproduced, while a readable code can open an unsuitable page. Preserve those distinctions instead of reporting one broad QR pass.

These illustrative exercises involved no InDesign operation, merge, code generation, decoding, export, printing or publication test. No live destination was opened, and no Itemlume integration is claimed.

After record mapping is correct, use the physical QR proof workflow for clear space and actual-size reproduction.

Use the destination lifecycle guide to assign continuing responsibility for a live page; record mapping alone does not maintain it.

Illustrative exercise: SKU-specific instructions versus shared campaign encoding

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)