The two choices on the creation screen
Both cards create the Collection straight away and drop you into its (empty) Item grid.
Under the cards, the same screen offers a short strip of starter templates plus Browse all.
Picking a template replaces this choice — the template carries its own scan behavior, field
schema and page design. See Starter Templates.
Neither choice is permanent. You can flip a Collection between the two later from its settings;
see Scan Behavior for New Items.
The name you get
The new Collection is named sequentially — one past the highest numbered default the team already has, so deleting one in the middle never produces a name collision (Collection 1, 2, 3 → delete 2 → the next one is 4). One wrinkle worth knowing: Collections were renamed from “Tubs”, and the name generator still uses the old word, so the name you actually see isTub4, not Collection4. Rename it inline
from the grid header or from Settings → General — nothing is derived from the name, so
renaming is free at any time.
What a fresh Collection starts with
- Four fields — name, Item ID, description and tags. Everything else you add yourself.
- Random link generation — a fresh
qrtub.com/r/x5fgd-style Link is minted and attached automatically each time you add an Item. Change this in Settings → Link generation. - No page template of its own. A Collection created from one of the two cards has no stored page design. Until you build one in the Page Editor, Items in Page Mode render a built-in default page — the Item’s name, image, status and tags, plus the Collection’s own name, description and image. Collections created from a starter template do get a real page template, generated from that template’s fields.
- No sample Items. Only starter templates seed example data.