u/ToughResolve5504

I’ve been building Stirling QR because I kept seeing the same issue:

teams print QR codes, then later the destination URL changes and the print assets become stale.

What I built:

- Dynamic redirect URLs on our own domain

- Update destination after print

- Expiry dates per code

- Pause/delete controls

- Scan tracking dashboard

Built with Next.js + Supabase.

I’d love feedback on:

1. what analytics are must-have vs nice-to-have

2. whether onboarding is clear enough for non-technical users

3. what would block you from using this in production

Demo:

https://www.stirling-qr.com

https://preview.redd.it/r9cdkj3ih8tg1.png?width=2064&format=png&auto=webp&s=e91a22fc686048f08d65165dcf2f00a11633c40f

I got frustrated with static QR codes breaking marketing journeys whenever destination URLs changed.

The recurring issue was simple:

- campaign launches with printed QR assets

- landing page URL changes later

- old QR points to dead/irrelevant page

- team has to reprint or accept lost traffic

What we changed technically:

1. QR codes now point to a short slug on our own domain

2. that slug resolves through a redirect layer

3. destination URL can be updated without changing the printed code

4. each code has status controls (active/paused/expired)

5. scans are logged so campaign performance is visible

Challenges we hit:

- avoiding stale redirect behavior from caching

- filtering bot/noise scans from real-user scans

- preventing accidental destination edits across team members

What this improved for marketing operations:

- fewer broken campaign journeys

- less reprint waste

- faster response when promos/endpoints change

- clearer scan visibility across active assets

If anyone else is running QR-heavy campaigns, this redirect-first model has been a much more reliable setup than static destination encoding.

https://preview.redd.it/shvguv22j8tg1.png?width=2064&format=png&auto=webp&s=e0e4430479d31f90dc3fae83d095f3f6c640fe38