Geotrackable.com
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. Public groups also get their own /trackable-group/{publicCode} page when the whole release needs one public-safe landing page.
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.
A journey can include simple location reports and fuller location notes. Both move the route forward, but the route history stays tied to the saved stop while current visible location notes are rediscovered from the same coordinate.
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. The same rule applies if the item ever needs to move to a different group later: remove it first, then associate it to the next group through the supported handoff flow.
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 trackable can belong to only one group at a time, and moving it later is a remove-then-associate workflow instead of a silent one-step switch.
If you leave a batch unactivated for later finders or recipients, Geotrackable can still treat you as a group follower so ownership and watch delivery choices merge cleanly when one of those items later overlaps with you.
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.
Public trackable groups now have their own page so a family release, club batch, or classroom set can be introduced as one collection before a visitor opens the individual items.
That same group page is also where signed-in followers can monitor or stop monitoring the whole batch. Creators who leave the batch unactivated can follow the group there too, and Geotrackable still deduplicates delivery when a later ownership role overlaps with that watch.
A saved route stop and a visible location note are not always the same thing, so clean page families make it easier to share, support, and explain the right page.
Follow the whole group when the batch itself is the thing you care about, such as a club event release, a troop challenge set, or a classroom travel kit that should move as one public story.
Follow individual items instead when you only care about a few specific pieces inside a mixed set. When the same event matches both a later ownership role and the saved group watch, Geotrackable merges those delivery choices into one deduplicated notification pass.
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.
