User
Prepare a batch of pre-printed QR campaigns
Create separately identified QR campaigns for a print batch, optionally reusing an existing campaign as a template, and export a CSV register for that batch.
Step-by-step guide
Before you start
- Your plan must allow Pre-Printed QR. Choose whether the batch should copy an existing destination or be prepared without one.
- A generated batch is application data; generating it is not an order placed with a printer.
Open this feature
- Open /portal/qr-codes/pre-printed on your site.
How to use it
Generate a small print batch
- Open /portal/qr-codes/pre-printed. Review the selected existing QR/template before entering the quantity; this screen can preselect an existing campaign.
- Enter Batch name, for example Counter display trial, and set QR quantity to a small practice count such as 3.
- Choose the dynamic QR type, QR style and public-page template. Review the print format/material and logo/short-URL options displayed.
- Select Generate print batch once and note the batch identifier/result count.
- Use Open campaigns or Your campaigns to inspect the new names. Without a copied destination, campaigns are drafts; a template with a destination can create active campaigns.
Export the register and verify print output
- Select Export CSV for the intended generated/recent batch.
- Check the CSV campaign names and public/short URLs against that batch. Keep it as the register for your printed material.
- Complete missing destinations/content in the campaign editor. Export the required QR images through each campaign’s design controls.
- Print a small sample and scan it at the planned physical size before approving a large print run.
Fields and examples
| Field or choice | How to use it |
|---|---|
| Batch name | Required, maximum 120 characters. Names are numbered within the generated batch. |
| QR quantity | Whole number from 1 to 500 in this version. Start small while checking the setup. |
| Template QR | An existing campaign can supply its type, destination, domain and other settings. Inspect the selection instead of assuming a blank starting point. |
| Dynamic type / QR style / Page template | Use offered choices. Generation rejects unsupported dynamic types or style/template keys. |
| Print format / Material | Saved batch preferences; they do not by themselves manufacture or ship printed labels. |
Check your finished result
- Compare generated count and numbered campaign names.
- Check whether each campaign is Draft or Active and whether it copied the intended destination.
- Open the exported CSV and test actual QR images before printing at scale.
Problems and fixes
| What you see | What to do next |
|---|---|
| Choose a dynamic QR type before generating | Select one of the supported dynamic types. |
| Quantity is rejected | Use a whole number between 1 and 500. |
| New codes unexpectedly share a destination | Check the selected template QR; generation copies its existing destination. |
| No print sheet downloads | Export CSV produces a register. Use the campaign design/download/print controls for the QR images. |
Technical reference
Role-scoped source references
Pinned commit: ca125291cce57358ac4842e50928bc31fc6eab07
Source-only route information
| Method | Source-default route |
|---|---|
| GET | /portal/qr-codes/pre-printed |
| GET | /portal/qr-codes/pre-printed/export |
Unmapped fields — not user instructions
These fields belong to this role’s source handler, but their screen labels were not confirmed.
| Source key | Handler |
|---|---|
| selectedType | modules/AppQRPrePrinted/Livewire/PrePrintedIndex.php |
| qrStyleTemplate | modules/AppQRPrePrinted/Livewire/PrePrintedIndex.php |
| publicTemplate | modules/AppQRPrePrinted/Livewire/PrePrintedIndex.php |