Start anywhere
A Collection, an Item, a Link and a Page do not require each other to exist. You can create Links and send them to a supplier before you know what they will point at, build a Page before any code opens it, or import real equipment data and print a box of spares in the same afternoon. Most systems make you finish the database before you can print; QRtub doesn’t, and that changes how you sequence a rollout. The tutorial below is one workable path through that, not the required one.Start here
- Key Concepts — Collection, Item, Link, Page and Tag in a sentence each
- Creating Your First Link — create a Collection, get a Link, connect it to an Item
- The Print-First Workflow — printing codes before the Items exist
Your data
- What Is a Collection? and Creating a Collection
- Core Fields vs. Custom Fields — what data each Item carries
- What Is an Item?
- Importing Items from CSV
Links and QR codes
- What a Link Is
- Choosing a Link Type — random, numbered, or custom
- Unallocated Links — a real, printable Link with nothing attached yet
- Downloading QR Codes
What a scan does
- Pages Overview — one code, several destinations
- What Is a Destination?
- Field Bindings & URL Templates — pre-fill another system with this Item’s data
Printing and rollout
- What Is a Tag? — stickers, plaques, signs, NFC tags
- Print Batches — tracking a production run
- Preparing Your Print Job
Use cases and integrations
- Works with — Mitti (formerly SafetyCulture), Google Forms and anything else with a URL; every recipe is a URL, not an API sync