Testing · checklist
NFC launch checklist: test the complete journey
Test the physical product, destination, content, analytics, fallback and team ownership before placing NFC touchpoints in public.
Reviewed for technical accuracy, practical usefulness and product neutrality.
Author: TapFlow Editorial · Reviewed by: TapFlow product teamPhysical check
Inspect print, edges, stability, tap marking and QR quality. Test the product in the same position and on the same surface where customers will use it.
- No cropped important artwork
- Tap area is obvious
- QR scans at normal distance
- Product is stable and reachable
Device check
Use multiple recent iPhone and Android devices where possible. Test with common cases and ask a person who did not configure the product to try without coaching.
Destination check
Test on Wi-Fi and mobile data. Confirm HTTPS, loading, language, business identity, buttons, forms, phone numbers and accessibility at small widths.
Operational check
Confirm who receives submissions, booking notifications and failure alerts. Document how to change the destination and what to do if a service is temporarily unavailable.
Check again after placement
Retest after installation, then schedule periodic checks. Links, business hours and external platforms change even when the physical NFC product does not.
Frequently asked questions
How many phones should be used for testing?
There is no universal number. Use more than one operating system and include devices representative of your real audience.
How often should an NFC destination be checked?
Check after every relevant business or platform change and on a regular schedule appropriate to how critical the touchpoint is.
Primary sources
Sources support technical facts. Practical recommendations are TapFlow editorial analysis.
- NFC TechnologyNFC Forum
- What NFC DoesNFC Forum
- NFC principles of operationNXP