What you are seeing
The code scans, the email app opens, but the subject line is empty, or the body is missing, or the recipient is wrong. The scan worked, so the fault sits in the email payload: the address, the subject, or the body was mistyped, misplaced, or dropped by the phone's handling. Email payloads are sensitive to separators and encoding, and a small format error can lose a field while the rest survives. The fix is to decode the payload and to rebuild it with the email generator.
Likely causes
1.
Subject or body field mistyped — A subject or body field with a wrong name, a missing separator, or a typo can be dropped while the rest of the message survives. Test: decode the payload and read every field.
2.
Non-standard email payload format — A hand-typed email payload can use a separator or field order the phone does not recognise. Test: compare the payload with the standard email format.
3.
Special characters breaking the format — A character such as an ampersand or a line break in the subject or body can break the field structure if it is not encoded. Test: try a simple subject with plain characters and compare.
4.
Phone email app handles the payload differently — Some email apps accept only part of the payload, such as the address without the subject. Test: try the same code with a second email app.
5.
Body too long for the payload — A very long body can be truncated or dropped by the phone. Test: try a short body and compare.
Step-by-step fix
1. Decode the payload and write down the recipient, subject, and body it carries.
2. Compare every field with the intended message.
3. Rebuild the email with the email generator, using plain characters in the subject.
4. Scan the rebuilt code and read the drafted email carefully.
5. Fix any field that is missing or wrong, and retest.
6. Retest the final code on two phones and confirm the full message is correct.
Putting this into practice
In practice, the subject is the field that gets lost first, because it sits in the part of the payload that format errors hit hardest. Build the email with the generator, keep the subject short and plain, and always read the drafted email on a test phone before printing. Keep a short note of what you tested, what failed, and what you changed, so the next person starts from evidence rather than guesswork. A fix that is written down survives staff changes and reprints; a fix that lives only in memory gets repeated.
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)
