Docs / LinkQR

Bulk Generation

Create many QR campaigns from CSV rows.

Estimated reading: 2 minutes

Bulk Generation

Bulk Generation creates multiple QR campaigns from CSV-like rows.

Format

Name,type_key,https://destination.example.com

Example:

Landing Page,dynamic_url,https://example.com
Menu QR,restaurant_menu,https://example.com/menu

Rules

  • The name is required.
  • The type key must match a supported QR type.
  • The URL must be valid.
  • Plan limits can restrict row count and total QR count.

Bulk Generation - Detailed Feature Guide

Feature Purpose

Create many QR campaigns from CSV rows. This feature is part of the LinkQR workflow and should be documented as an operational tool, not just a menu item.

Main Capabilities

  • CSV-style creation for multiple QR campaigns or short links at once.
  • Validates campaign name, destination URL, alias, password, and related import fields where supported.
  • Respects plan limits for maximum QR codes, short links, and maximum bulk rows.
  • Best for agencies, events, franchise locations, product catalogs, and multi-location campaigns.

Typical Workflow

  1. Open the Bulk Generation page from the sidebar.
  2. Review the existing records, settings, or campaign state.
  3. Create or update the required item.
  4. Validate important fields before saving.
  5. Preview or test the public/user-facing result when applicable.
  6. Use analytics, logs, or reports to confirm the feature is working as expected.

Admin Configuration Notes

  • Confirm the feature is enabled in the correct plan.
  • Check workspace ownership when users work inside a team.
  • Review related limits such as credits, storage, QR count, scan count, or team members.
  • Clear cache and test again after changing global settings.

Customer-Facing Benefits

  • Reduces manual work and makes campaign setup faster.
  • Keeps campaign assets organized and easier to maintain.
  • Improves reliability by keeping important setup steps inside one workflow.
  • Supports better reporting and troubleshooting after launch.

Troubleshooting Checklist

  • If the feature is not visible, check plan permission and user role first.
  • If saved data does not appear publicly, verify publish/status settings.
  • If a public URL is involved, test the URL in a private browser session.
  • If team workspaces are involved, confirm the item belongs to the correct owner workspace.
  • If tracking or analytics is involved, confirm the visitor action uses the tracked dynamic URL.