[{"data":1,"prerenderedAt":121},["ShallowReactive",2],{"blog-en-shared-collection-tracking":3},{"id":4,"title":5,"body":6,"date":112,"description":113,"extension":114,"meta":115,"navigation":116,"path":117,"seo":118,"stem":119,"__hash__":120},"blog\u002Fen\u002Fblog\u002Fshared-collection-tracking.md","How to Track a Trading Card Collection You Share With Someone Else",{"type":7,"value":8,"toc":102},"minimark",[9,13,17,22,25,29,32,36,39,43,63,67,95,99],[10,11,5],"h1",{"id":12},"how-to-track-a-trading-card-collection-you-share-with-someone-else",[14,15,16],"p",{},"A lot of collections aren't solo projects. Couples build one together. Siblings inherit or\nsplit a childhood collection. Two friends pool budget to chase a set they'd never afford alone.\nNone of these fit a tracking setup built around a single owner — and most tools are built\naround exactly that assumption.",[18,19,21],"h2",{"id":20},"why-a-single-spreadsheet-or-single-account-app-breaks-down","Why a single spreadsheet or single-account app breaks down",[14,23,24],{},"The obvious first move is one person \"owns\" the tracking — one spreadsheet, one login, one\nsource of truth. It works for a while. Then someone adds a card the other person doesn't know\nabout, or updates a quantity from memory instead of checking, and the two people's mental\npicture of the collection quietly drifts apart from the actual one. The underlying problem isn't\ncarelessness — it's that a single-owner tool has no way to represent \"we both look at this and\nwe're both allowed to change it.\"",[18,26,28],{"id":27},"what-real-time-sync-actually-solves","What real-time sync actually solves",[14,30,31],{},"The fix isn't a shared login (which just moves the same single-owner problem to a shared\npassword) — it's a wallet that genuinely belongs to more than one account, where every member\nsees the same cards and quantities updated live. If your partner adds a card from their phone\nat a card show, it should show up on your phone before you're both back in the car, not after\nsomeone remembers to \"sync the spreadsheet\" that evening. In Grail, shared wallets work exactly\nthis way: you invite a collaborator with a link, and everyone in that wallet sees the same state\nin real time, with an editor or viewer role depending on how much control you want to give them.",[18,33,35],{"id":34},"roles-matter-more-than-people-expect","Roles matter more than people expect",[14,37,38],{},"Not every collaborator needs the same permissions. A partner actively adding and pricing cards\nneeds editor access. A parent who just wants to check in on a kid's collection, or a friend\nwho's merely curious what's in a group pool, only needs to view it. Treating \"shared\" as one\nflat permission level either locks out people who should be able to contribute, or gives edit\nrights to people who only wanted to look — both are avoidable with a proper editor\u002Fviewer split.",[18,40,42],{"id":41},"the-wantlist-problem-in-group-collecting","The \"wantlist\" problem in group collecting",[14,44,45,46,50,51,55,56,59,60,62],{},"Solo collectors use a wishlist: cards ",[47,48,49],"em",{},"they"," want. Group collections need something slightly\ndifferent — a shared list of cards the ",[52,53,54],"strong",{},"group"," wants to add next, visible to everyone, so\nnobody buys a duplicate of something a co-collector already has queued up, and everyone can see\nwho requested what. This is a distinct concept from a personal wishlist, and conflating the two\nusually means someone's \"I want this\" gets lost in a private list nobody else can see. Grail\nkeeps these separate: a personal wishlist for what ",[47,57,58],{},"you"," want, and a shared wantlist per wallet\nfor what the ",[47,61,54],{}," is chasing, with each entry showing who added it.",[18,64,66],{"id":65},"practical-tips-for-collecting-with-someone-else","Practical tips for collecting with someone else",[68,69,70,77,83,89],"ul",{},[71,72,73,76],"li",{},[52,74,75],{},"Agree on who prices what, up front."," If one person always sets purchase price and the\nother never does, your ROI numbers will be inconsistent and half-true.",[71,78,79,82],{},[52,80,81],{},"Decide editor vs. viewer per person, not by default."," Don't give blanket edit access just\nbecause it's the path of least resistance when inviting someone.",[71,84,85,88],{},[52,86,87],{},"Use the shared wantlist instead of a side chat."," A \"hey did you want this Charizard?\"\nmessage in a group chat gets lost in twenty minutes; a wantlist entry doesn't.",[71,90,91,94],{},[52,92,93],{},"Check the shared history, not just today's total."," A shared wallet's value history tells\nyou whether the collection has been growing steadily or whether one big pickup did all the\nwork — useful context before deciding how much more to invest together.",[18,96,98],{"id":97},"the-takeaway","The takeaway",[14,100,101],{},"Shared collecting fails quietly, not loudly — nobody notices the tracking has drifted from\nreality until someone finds a card \"missing\" that was actually just never logged, or buys a\nduplicate nobody flagged as wanted. Real-time sync and the right permission model don't make\ngroup collecting more complicated; they remove the manual coordination that was making it feel\ncomplicated in the first place.",{"title":103,"searchDepth":104,"depth":104,"links":105},"",2,[106,107,108,109,110,111],{"id":20,"depth":104,"text":21},{"id":27,"depth":104,"text":28},{"id":34,"depth":104,"text":35},{"id":41,"depth":104,"text":42},{"id":65,"depth":104,"text":66},{"id":97,"depth":104,"text":98},"2026-07-19","Tracking a Pokémon TCG or One Piece collection built with a partner, sibling, or friend has different needs than tracking a solo collection — here's what actually matters.","md",{},true,"\u002Fen\u002Fblog\u002Fshared-collection-tracking",{"title":5,"description":113},"en\u002Fblog\u002Fshared-collection-tracking","5QE-PMpOvfKXUqw-Isob9Ffmoq-3A9zQEerezRtnhlo",1790191573276]