WebAR Qr-code Campaign Pre-launch Checklist For UK Brands

WHY QR + WEBAR IS THE LOWEST-FRICTION AR THERE IS

The traditional AR problem was distribution: build a beautiful experience, then beg people to download an app to see it. Download friction kills most consumer AR before it starts. WebAR removes that step entirely. The customer points their normal phone camera at a QR code, the browser opens, the camera feed starts, and the AR experience loads. On iOS that means Safari; on Android, Chrome. No install, no account, no permissions beyond camera access.

For brands, that changes the maths: a QR code costs almost nothing to add to print you are already producing, and every unit becomes a measurable media channel. Where campaigns fall apart is the gap between the demo and the real world — built on office Wi-Fi with the latest iPhone, experienced in a supermarket aisle on patchy 4G with a three-year-old Samsung. The checklist below exists to close that gap.

If you are still deciding between WebAR and a native app for the campaign, read our comparison of AR filters vs WebAR first — for QR-driven campaigns, WebAR wins on friction almost every time.

THE PRE-LAUNCH CHECKLIST

Fourteen checks, grouped by where things go wrong. Do them in order — each group depends on the one before it.

GROUP A — THE LINK AND THE LANDING

1. Point the QR at a short URL you control, never directly at the experience. Use a branded short link that 301-redirects to the WebAR build. When (not if) the experience URL changes, you update one redirect instead of reprinting ten thousand boxes. Keep the redirect chain to a single hop — every extra hop is scan-to-load time.
2. Build a lightweight loader page in front of the experience. Before the camera opens, show the brand, one line explaining what happens next ("Point your camera at a flat surface to place the sofa"), and a clear consent/continue button. This page is also where your privacy notice lives and where unsupported devices get their fallback — not a dead end.
3. HTTPS everywhere, no exceptions. Mobile browsers will not grant camera access on an insecure connection. If any asset in the chain loads over HTTP, expect silent failures on some devices.

GROUP B — THE AR EXPERIENCE ITSELF

1. Set a payload budget and enforce it. Aim for the first AR frame in under five seconds on 4G: compressed models (GLB with Draco), mobile-sized textures, and lazy-loading anything not needed in the first ten seconds. Ask your developer for the total transfer size — if they cannot tell you, that is your answer.
2. Design for the worst phone in your audience, not the best. Test on a mid-range Android from two or three years ago, because that is what a large share of your scanners will hold. If it only runs smoothly on a flagship iPhone, you have built a demo, not a campaign.
3. Give the experience one job. "Try the shade on your wall, then tap to find your nearest stockist." AR without a next step is a novelty people close after eleven seconds. Decide the single action the experience exists to drive, and design backwards from it.
4. Do not rely on audio. Most scans happen in public with the phone on silent. Captions, on-screen instructions and visual cues carry the experience; audio is decoration.

GROUP C — THE PHYSICAL QR CODE

1. Size it for the scanning distance. Rough rule: the code should be at least 10% of the distance people will scan from. Packaging scanned at arm's length needs roughly 2 × 2 cm minimum; a poster scanned from two metres needs 20 cm. When in doubt, go bigger — nobody ever complained a QR code was too easy to scan.
2. Protect contrast and the quiet zone. Black on white, always. Decorative coloured codes on patterned backgrounds are the number one cause of "it doesn't scan" complaints. Keep the blank margin (quiet zone) around the code clear of text and design elements.
3. Place it where people have time and signal. A QR code on the side of a bus is a joke; a QR code next to the product on a shelf, at eye level, with a reason to scan is a channel. Pair every code with a plain-English incentive: "See this sofa in your room" beats "Scan me" every time.
4. Print a short URL alongside the code as backup. Some users cannot or will not scan. A memorable short link catches them.
5. Use dynamic QR codes for anything printed at volume. The printed pattern stays the same while the destination stays editable. Static codes on ten thousand units are a liability the first time a URL changes.

GROUP D — TESTING

1. Run a real device matrix, not a desk check. iOS Safari and Android Chrome, old and new; in the actual lighting where the code will live (supermarket fluorescents are unkind); with the phone's data saver on. Test the full journey from a cold scan to the conversion action, not just "does the AR load".

GROUP E — MEASUREMENT

1. Define the one metric before print, and instrument for it. Pick one: scans, experience starts, completions, or the downstream action (signup, voucher claim, stockist click). UTM-tag every destination and use unique QR variants per placement — packaging vs poster vs in-store — so you know which placement earned its keep.

GROUP F — LEGAL (UK)

1. Sort GDPR before launch, not after. If the experience collects emails, runs analytics, or drops cookies, you need a lawful basis and a privacy notice — the loader page from step 2 is the natural home for it. And under ASA rules, anything the AR shows must not mislead: a virtual try-on that misrepresents the product's size, colour or effect is an ad like any other.

THREE WAYS THESE CAMPAIGNS ACTUALLY FAIL

The same failures repeat across campaigns. All three are checklist items above — which is the point.

1. The QR points at a dead URL. The microsite was taken down, the platform trial expired, or marketing changed the link and nobody told print. Dynamic codes and owned short URLs exist precisely for this.
2. It was only tested on the agency's iPhones. Half your audience is on Android. If QA never touched a mid-range Samsung on 4G, launch day is the first real test — conducted by your customers.
3. Success was never defined. "We got 40,000 scans" means nothing without the next number — how many started the experience and did the thing it was built for. Decide the metric before print, or the report afterwards will be vibes.

WHAT A SENSIBLE BUDGET LOOKS LIKE

Honest numbers from the UK market: a straightforward WebAR experience — product viewer, simple game or filter delivered through a QR code — typically lands between £3,000 and £8,000 to design and build. 3D models are often a separate line at £300–£1,500 per SKU (less with existing CAD files); dynamic QR generation and scan analytics cost tens of pounds a month. What moves the budget is scope creep: multiple products, languages, or a competition mechanic with prize fulfilment. Our WebAR development cost guide for 2026 has the full bands — and if you want a fixed quote for your campaign rather than a range, ask us.

WEBAR QR CAMPAIGNS — FAQs