What you are seeing
This fix makes the email code open a fully addressed message. You will decode the payload, compare the recipient, subject, and body with the intended message, and rebuild it with the email generator. Verify the fix by scanning and reading the drafted email on two phones.
Likely causes
1.
Subject or body field mistyped — Quick test: decode the payload and read every field.
2.
Non-standard email payload format — Quick test: compare the payload with the standard email format.
3.
Special characters breaking the format — Quick test: try a simple subject with plain characters and compare.
4.
Phone email app handles the payload differently — Quick test: try the same code with a second email app.
5.
Body too long for the payload — Quick test: try a short body and compare.
Step-by-step fix
Step 1: Decode the payload and write down the recipient, subject, and body it carries.
Step 2: Compare every field with the intended message, letter by letter.
Step 3: Rebuild the email with the email generator, using the verified recipient, subject, and body.
Step 4: Keep the subject short and use plain characters where possible, then rebuild.
Step 5: Scan the rebuilt code on two phones and read the drafted email field by field.
Step 6: If a field is still missing, test the same code in a second email app to separate a payload fault from an app limit.
Step 7: Retest the final code on two phones and confirm the recipient, subject, and body are all correct.
Putting this into practice
In practice, keep the intended message in one record: recipient, subject, and body. Build the code from that record and check the proof against the same record, so a typo in either place gets caught. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Hand-typing an email payload and losing the subject to a format error nobody noticed.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that scans but the email has no subject will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that scans but the email has no subject.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded recipient, subject, and body match the intended message
- The subject uses short, plain text
- Scanning drafts the full message on two phones
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [email QR code generator](/email-qr-code-generator)
- [QR payload inspector](/qr-payload-inspector)
- [QR offline verifier](/qr-offline-verifier)
- [QR scan log](/qr-scan-log)
- [QR safety checker](/qr-safety-checker)
- [blog](/blog)
