Skip to main content

EDIT ALL FIELDS AVAILABLE

User Feature Request

We seriously need to be able to edit all fields after a scan of a card because often, there are errors from the Ai scan. Set, price, player name, card number, year etc, all fields need to be editable by the user please.

Platform
Status: Future Consideration3 comments

Comments3

  • An Anonymous User

    •

    Aug 13

    •

    Merged request

    •

    2 votes

    Full Card Editing on Desktop (Especially Parallels)

    Summary: Bring complete card editing to the desktop/web experience, with the parallel and variant fields front and center.

    Problem: Identifying and assigning the correct parallel — Refractor vs. X-Fractor vs. Prism Refractor vs. color shimmer — is detail work that's genuinely hard on a phone screen. In my collection, a meaningful share of cards ended up with an empty parallel field, and since price follows the exact parallel, those cards show wrong or missing values. Two examples from my own data: a Refractor rookie carried at the base-card price, and a serial-numbered /25 shimmer with no price at all.


    Proposed behavior:

    • Desktop web app with full edit parity: parallel, serial numbering, condition, custom price, photos, notes

    • Spreadsheet-style grid view with keyboard navigation for fast cleanup sessions

    • A dedicated serial-number field (/25, /99, /250) separate from the parallel name

    • Side-by-side reference images of each parallel option while editing, so I can match the card in hand


    Why it matters: Parallels are where the value lives. A desktop editing pass after mobile scanning is the natural workflow: scan fast on the phone, clean up accurately at a keyboard.

    • Aqua Cat

      •

      Aug 12

      Some of what you're asking is already available. Select the desired card from My Collection and those editable fields are there.

  • April @ Ludex

    Team•

    Aug 10

    Hey there, sorry for the delayed response - we were at the National. :)

    So the rub here currently is that once you customize your card, it would be no longer “found” in our dataset and that would create some issues with how we currently treat cards internally.

    It’s something we’ll need to looking into from a broader perspective of ramifications, but in the meantime our bigger pressing issues are to improve card ID so that ID errors are a rarity rather than an often! :)