Organize inventory
What you’ll accomplish
By the end of this workflow, your Pegasus inventory mirrors your physical collection well enough that readiness and acquisition recommendations are trustworthy. The single biggest lever in the whole app is the gap between “owned” and “available” — this is where you make that distinction explicit.
Before you start
- A rough mental map of where your cards live physically (which binder, which box, which decks).
- 10–15 minutes of focused time. Inventory work scales linearly with collection size — first pass on a 2000-card collection is one sitting; subsequent passes are minutes.
Steps
-
Create locations you can maintain
Open Inventory → Locations. Pegasus ships empty — you create the locations that match how you actually store cards. Good starting set:
- Active decks — committed to a deck in current rotation
- Staples box — shared singles you draft into multiple builds
- Main binder — display + protected singles
- Trade binder — cards you’d part with
- Unsorted inbox — new arrivals not yet placed
- Bulk storage — sleeved but not catalogued
Resist creating locations you won’t maintain. “Binder page 14, slot 6” sounds organized; in practice nobody updates it after the first reshuffle and the entry rots.
Screenshot pending /img/docs/organize-inventory/inventory-locations.pngFive to seven locations is the sweet spot. Twenty is theatre. -
Assign cards to locations in bulk
Switch to the card grid view. Multi-select with shift-click or the toolbar bulk-select control, then open the assign modal. Pegasus accepts batch reassignment — moving 200 cards from “inbox” to “main binder” is one operation, not 200.
Screenshot pending /img/docs/organize-inventory/inventory-assign-modal.pngIf the modal selection counter doesn't match what you intended, cancel — don't fix it on the way out. -
Watch for cross-deck conflicts
The single most useful inventory signal is the availability column. It shows owned-copies minus committed-copies. When a staple is committed to two active decks, Pegasus flags it on both decks’ readiness pages.
You own three copies of a staple. All three are committed to your control deck. Another target deck calls for three. The second deck reads “buildable: no” even though the card is technically in your collection. That’s the gap between owning and being able to use — Pegasus surfaces it so you make the choice consciously.
Screenshot pending /img/docs/organize-inventory/inventory-conflict.pngThe fix is rarely 'buy more copies' — it's usually 'pick which deck wins.' -
Reconcile after every event
After locals, after testing, after a trade — run a short pass: move cards back to their true location, update deck commitments, clear temporary “lending” locations.
The system stays useful only as long as it’s honest. A two-month-old inventory state with stale commitments produces worse-than-useless recommendations — confidently wrong is worse than admitting uncertainty.
Screenshot pending /img/docs/organize-inventory/inventory-success.pngThe goal isn't perfect — it's accurate enough to trust.
What success looks like
Every active deck shows green availability. The Inventory dashboard tile shows zero “uncategorized” cards. Cross-deck conflict count is zero, or every flagged conflict has a deliberate resolution (you knowingly accept that deck A wins over deck B for the disputed staple).
Going deeper
The owned-vs-available split is core to the scoring model — every readiness check joins the deck list against the inventory respecting commitment flags. The core concepts page explains why Pegasus models locations as first-class entities rather than free-text tags.
If you imported a CSV and want to know what each location field maps to, see Add and maintain cards.
For the field-by-field reference of the inventory surface — every column, every filter, every bulk action — see Inventory (reference).