Dynamic URL System with NFC/QR Code

Overview:

I need a system for managing dynamic URLs used with NFC and QR code products.

Each item will have a unique short URL that can be updated after creation and must track usage (scans/taps).

Core Requirements:

Dynamic URL System
Generate unique short URLs (e.g. subdomain.com/r/{code})
Each URL redirects to a destination URL
Destination must be editable at any time
Must log each scan/tap event (timestamp minimum)
Must support 1,000+ URLs initially and scale to 100,000+
Admin Tools
Bulk generate URLs (1,000+ at a time)
Export CSV of URLs (for external use)
Assign URLs/items to users
Customer Dashboard (Simple MVP)
User login (email/password or magic link)
Each user sees only their assigned items

Dashboard must include:

List of items
Per item:
total scans/taps
last activity
current destination URL
Ability to edit destination URL

Optional (nice to have):

basic overview of total scans across items
Architecture Requirements
Use subdomains:
go.domain.com → redirect system
app.domain.com → dashboard
Must be clean, simple, and scalable

Technical Direction (flexible):

Preferred:

Supabase (database + auth)
Next.js (frontend)
Vercel or Cloudflare (hosting)

Open to simpler or better alternatives if:

faster to build
easier to maintain
scalable

Important Constraints:

Keep it SIMPLE (no overengineering)
No unnecessary complexity
Must be easy to maintain after delivery
Must NOT require ongoing developer involvement for basic usage

Scalability Requirement:

System must be structured to handle:

tens of thousands of URLs
multiple users with many items
increasing scan volume

Future Considerations (do not build now):

AI-generated responses (e.g. review replies)
additional analytics features
multi-account / multi-location support

Deliverables:

Working deployed system
Code in my GitHub
Backend in my account
Subdomains configured
Basic documentation for:
generating URLs
exporting data
managing items

To Apply:

Share relevant past work (dashboards, link systems, analytics tools)
Briefly explain how you would approach this
Confirm you understand this is a lean MVP (not a full SaaS build)

Note:

I am specifically looking for someone who can build a clean, simple, scalable system without overengineering.