What you are seeing
The code scans, the map opens, but the pin lands in the wrong place: the wrong building, the wrong end of the street, or an empty field. The scan worked, so the fault sits in the location the code carries: the coordinates, the address, or the map link. A wrong pin is worse than no pin, because visitors follow it confidently in the wrong direction. The fix is to decode the location, compare it with the real place, and correct the coordinates or the address.
Likely causes
1.
Coordinates mistyped in the payload — A coordinate with a mistyped digit, a swapped latitude and longitude, or a missing minus sign can land the pin far from the intended place. Test: decode the payload and read the coordinates.
2.
Address ambiguous or misread — An address that matches several places, or that the map service reads differently, can pin the wrong one. Test: search the address in the map service and compare the pin.
3.
Map link points at the wrong place — A map link copied from the wrong pin, or from a search result, can carry the wrong location. Test: open the link and compare the pin with the intended place.
4.
Pin placed on the building, not the entrance — A pin on the centre of a large site can send visitors to the wrong side of the building. Test: compare the pin with the entrance visitors should use.
5.
Outdated map data — A new road, a renamed place, or a moved entrance can make the map data disagree with reality. Test: compare the map with the real location on the ground.
Step-by-step fix
1. Decode the payload and write down the exact location it carries.
2. Open the location in the map service and compare the pin with the real place.
3. Find the correct coordinates for the entrance visitors should use.
4. Rebuild the code with the verified coordinates or the corrected address.
5. Scan the rebuilt code and compare the pin with the real location.
6. Retest on two phones and confirm the pin lands on the right place.
Putting this into practice
In practice, the pin is the product. A map code that points at the building instead of the entrance sends visitors to the wrong door, which is a failure even when the coordinates are technically close. Choose the pin for the entrance, test it on the ground, and check it again whenever the site changes. 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
- Copying a map link from the wrong pin and sending visitors to the wrong end of the site.
- 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 map shows the wrong place 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 map shows the wrong place.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded coordinates match the intended entrance
- The pin lands on the right place on two phones
- The coordinates are recorded in the job file
- 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
- [QR payload inspector](/qr-payload-inspector)
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR expiry checker](/qr-expiry-checker)
- [QR placement guide](/qr-placement-guide)
- [QR safety checker](/qr-safety-checker)
- [blog](/blog)
