What you are seeing
This fix restores the booking journey behind the code. You will walk the booking manually, check the link and the booking settings, and repair the step that errors. Verify the fix by scanning and completing a test booking on two devices.
Likely causes
1.
Booking link expired or changed — Quick test: open the booking link directly.
2.
Booking settings blocking the request — Quick test: check the booking settings and availability.
3.
Link missing the booking details — Quick test: decode the payload and compare the link with the intended booking link.
4.
Redirect dropping the booking details — Quick test: follow the redirect chain and watch the booking parameters.
5.
Page script or form fault — Quick test: complete a booking manually without the QR code.
Step-by-step fix
Step 1: Decode the payload and write down the exact booking link it carries.
Step 2: Walk the booking journey manually, without the QR code, and note the step that errors.
Step 3: Check the booking settings, availability, and rules for the service.
Step 4: Follow the redirect chain and check that it preserves the booking details.
Step 5: Fix the link, the redirect, the settings, or the page, whichever is at fault.
Step 6: If the payload carries the wrong link, regenerate the code from the correct booking link.
Step 7: Retest by scanning the code and completing a test booking on two devices.
Putting this into practice
In practice, never relaunch a booking code on the strength of a scan test. Only a completed test booking proves the journey works. Keep that test booking in your launch checklist for every booking code. 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
- Relaunching a booking QR code after a scan test, without ever completing a test booking.
- 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 booking page errors 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 booking page errors.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The booking link works directly in a phone browser
- The booking settings allow the requested booking
- A test booking completes from a scan on two devices
- 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
- [survey QR code generator](/survey-qr-code-generator)
- [feedback QR code generator](/feedback-qr-code-generator)
- [QR payload inspector](/qr-payload-inspector)
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR expiry checker](/qr-expiry-checker)
- [UTM builder](/utm-builder)
