One QR code is easy to manage. Ten is fine. A hundred is where things start to go wrong โ€” and they go wrong in a very specific way. You end up with a flat list of codes with names like "QR Code 14 - copy" and no idea which ones are live, which are archived, or which belong to which campaign.

Project folders solve this. Here's a simple, scalable system that works whether you're running three codes or three hundred.

Why folders matter at scale

The primary function of a folder system is filtering. When something breaks โ€” a destination returns a 404, a campaign ends, a team member asks where a specific code is โ€” you need to find it fast. A flat list does not scale. Folders do.

Folders also make analytics meaningful. Instead of looking at a single graph of all scans across all codes, you can isolate a campaign or product line and see exactly how that group is performing. That's where QR analytics become genuinely actionable.

A folder structure that actually works

The most effective folder systems organise by context of use, not by code type. Here's a structure used by teams managing 50โ€“200 codes:

๐Ÿ“ Marketing Campaigns Spring Sale 2025 Summer Launch Black Friday ๐Ÿ“ Menus Main Menu โ€” London Drinks Menu โ€” London Seasonal Specials ๐Ÿ“ Product Packaging Widget Pro โ€” Manual Widget Lite โ€” Warranty ๐Ÿ“ Business Cards Alex โ€” vCard Sam โ€” Review Request ๐Ÿ“ Archive 2024 Christmas Campaign Old WiFi Code
๐Ÿ’ก
Always have an Archive folder

Keep completed campaigns in Archive rather than deleting them. Archived codes remain accessible for analytics and can be restored in one click. Deletion is permanent.

Naming conventions that save time

Good folder names are obvious to anyone on the team, not just the person who created them. Use the format: [Location or Client] โ€” [Purpose] when relevant, and avoid abbreviations your team doesn't share.

  • Good: "Bristol Branch โ€” WiFi", "Product Launch Sept 25 โ€” QR on Box"
  • Bad: "WiFi3", "QR Code (new)", "Campaign v2 FINAL"

Use the Notes field on each code to add context that doesn't fit in the title: where the code was printed, what material it appears on, who requested it, what the expected lifespan is.

Organising for teams

On the Growth plan and above, multiple team members can access the same dashboard. The folder structure becomes the shared filing system for the whole team. A few ground rules help:

  • One person owns each folder. They're responsible for keeping it tidy and reviewing archived codes quarterly.
  • New codes go into a folder immediately. Not the root list. Never the root list.
  • The Archive is reviewed every quarter. Delete permanently only after checking that no physical materials with that QR code are still in circulation.

Using folder analytics

Once your codes are organised into folders, you can filter your analytics dashboard by folder to see aggregate performance. This tells you things like: "All my Menus folder codes combined received 4,200 scans last month" or "My Business Cards folder has been growing 12% week on week since the team started using the new card design."

Folder-level analytics are particularly useful for comparing campaigns, tracking seasonal patterns, and deciding when to retire codes that haven't been scanned in 90 days.

Start now, tidy as you go

If you already have a flat list of codes, don't try to reorganise everything in one session. Create your folder structure first, then move codes as you touch them โ€” when you're updating a destination, when you're checking analytics, when a team member asks about a specific code. Within a few weeks, the most active codes will be organised. The rest can wait.

The goal is not a perfect system from day one. It's a system that makes the next search take seconds instead of minutes.

Project folders are available on Starter and above

Starter includes 5 folders. Growth includes 20. Pro / Scale includes unlimited. Compare plans โ†’

Start 7-day trial โ†’