Loading your page…
Product guide
SoccQR gives a soccer ball its own return page. The finder scans the tag, sees only the contact options the owner chose, and can return the ball without an app or account. The same SoccQR account can also keep a player journal and connect to team tools.
The scan opens the return page the owner already set up.
The return flow is the first job SoccQR does, and it stays deliberately simple.
The page answers the finder's three questions: what is this ball, who owns it, and how do I get it back?
Claim the tag once, then update the information behind it without replacing the QR tag on the ball.
Owners can edit the title, message, image, tag status, and public contact choices. They can also open the live return page to check exactly what a stranger will see before the ball goes back into use.
Contact details remain behind the actions the owner enables. The public page is for returning the ball; management stays with the signed-in owner.
The journal is optional. When a player uses it, practices and matches build a season record instead of disappearing into a generic activity log.
Saved sessions feed recent activity, weekly totals, streaks, progress views, and an eight-attribute player profile. Players can review or edit that history from the sessions manager.
The player journal stays personal by default. A coach invite adds the shared roster and assignment layer.
Players see assigned work in their team workspace. Coaches see roster activity, assignment completion, and the recent logs players already save—so follow-up is based on real work rather than a separate check-in system.
Players join through an invite code, email, or team link and must accept before they become active roster members. Coach Mode is enabled for the right account after review. If a player is removed, a fresh invite is required to rejoin.
Set up the recovery flow first. Add the journal or team layer only when it helps.
Ball return first. Player progress second. Team tools when the group needs them.