Separate a scanning problem from a destination problem. If a phone reads the code but the website fails, the image may be working correctly while the linked resource is unavailable.
The camera cannot read the code
Try the downloaded original rather than a compressed copy. Use a plain, high-contrast design with a clear border. Remove decorative logos or complex colors temporarily, increase the display or print size, and test in better lighting with another phone.
The code scans but opens the wrong address
Inspect the builder’s Embedded data panel and the selected link or destination. A QR reader uses the encoded data, not the resource’s internal name. Regenerate the correct static code or update the selected dynamic link’s destination as appropriate.
A printed dynamic code stopped working
Check whether the underlying link was disabled, renamed, deleted, scheduled to expire, or limited by clicks. The printed image still points to the original alias. If that alias changed, restore the intended resource where possible or contact support; editing only the QR’s name will not repair the encoded address.
A contact, WiFi, or event action behaves differently on phones
Different scanning apps can interpret the same data differently. Check the recipient, security type, dates, and required fields in the chosen template, then test on the devices your audience uses. Consider a normal URL to a contact or event page if the direct data action is inconsistent.