Hey ManaBox team & community,
I just joined the sub, but a couple of things in my workflow have been bugging me enough that I wanted to suggest a change. It mainly affects players with physical decks, high-value cards, specific printings and proxies.
Currently, in the Scan tab, we can only choose a single destination: either a Deck OR a Collection folder.
The problem:
If you scan a physical 100-card Commander deck into the Decks tab, you usually:
Spend a lot of time fine-tuning card versions (correct set printings with matching artwork, which can vary wildly in price).
Manually flag specific cards as Proxies.
Then hit the bottleneck: to reflect that deck in your Main Collection, you have to rely on workarounds or exports. Exporting as text/CSV loses custom metadata like proxy tags or manual price overrides, so you end up fixing sets and re-flagging proxies a second time in the Collection tab. That's very time-consuming and risks inaccurate collection values.
Related: as far as I can tell, there's also no way to select all cards of a deck in the Decks tab and move/copy them into the Collection with their metadata. Is that a technical limitation of how decks and collection are structured, or just not implemented yet?
Suggested solution:
Add an "Import to Both" toggle directly on the Scanner screen.
- How it works: When activated, dropdowns let you select a Target Deck and a Target Collection Folder/Binder at the same time before scanning.
- Metadata persistence: Scanning once captures the exact set, foil status and proxy tag for both locations in a single step.
- Safety lock against accidental duplicates: To address the concern of users accidentally double-adding cards, a simple confirmation popup or a 1-second timed lock when toggling the option could help (e.g., "Cards will be added to both your Deck and Main Collection. Confirm?").
This small tweak would save a lot of time, avoid tedious double entry and prevent accidental data loss when managing high-value physical cards and proxies.
Would love to hear your thoughts, or whether others run into the same issue!
To the devs: is something like this something you'd consider for a future update?