Trackable groups let you create a batch of related items with shared starter defaults, team scope if needed, and room for item-level overrides later.
Every created item still gets its own public code, secret code, and private QR access even when the visible copy begins with group defaults.
A group defines the batch title, batch description, item count, personal-or-team scope, starting visibility, optional immediate activation, and the shared defaults for item title, item description, status message, and external link.
That is why the group form is best for campaigns, classroom kits, club drops, event giveaways, or any other situation where several items should begin from the same baseline.
A group does not turn several trackables into one record. Each item still has its own codes, its own route history, its own ownership state, and its own future edits after activation.
If an item later needs its own story, images, or different public link, that should happen on the individual trackable instead of trying to force every item in the batch to stay identical forever.
Start on the trackable chooser when you are deciding whether one item or a whole batch is the right fit.
Create TrackablesUse the group form for the batch title, description, count, grouped defaults, images, and first-round visibility or activation choices.
Create a Group of TrackablesUse categories and team scope to keep grouped items discoverable after creation instead of leaving everything in one flat list.
Manage CategoriesDefault title, description, status message, and link are the starter values for items that do not have their own replacements yet.
As soon as one trackable gets its own value, that change overrides the matching group default for that item only.
If a grouped item starts unactivated, activation should be the point where the new owner gives it specific details instead of relying on creator-controlled defaults forever.
A group can start in your personal workspace or under a team, and the grouped items can still be associated with the right category branches later.
The safest group setup starts with broad defaults for the batch and leaves the personal story of each item to later activation or editing.
If a default link or default description later becomes misleading, fix it or report it quickly, because inherited defaults can affect many uncustomized items at once.
