Purchases

Purchases is the mirror of Sales: a ledger for the singles you buy — the Card Kingdom order, the vendor-hall haul, the deal at Friday night Magic. It records what you actually paid, tracks the order until it arrives, and — when the cards are in hand — loads them into your binders with their real cost attached.

Recording a purchase

Tap +, name the vendor and set the date. Vendors work like buyers do in Sales: created as you type, offered back by autocomplete, so "Card Kingdom" stays one vendor across every order. A store, a person, an event — anything you buy from.

Then Add Card: the same search-and-tap flow as everywhere else. When a card lands on the order, the current price in your price source is filled in as a starting suggestion — but unlike a sale, a purchase line's price is the price you paid, so edit it to the real number. The market price stays visible as a reference (nice for knowing instantly whether you bought well). Tapping the same printing again grows the line's quantity.

Tap a line to refine condition, quantity and price. One rule to know: lines already loaded into a binder freeze everything but the price — revert the load first if you need to change what physically moved.

Statuses

Three independent switches, in lifecycle order: Ordered, Paid, Received — chips on the purchase, dots on every list row, each remembering when it happened. A new purchase starts as Ordered; Paid is the one that matters most, because only paid orders count in the Ledger's numbers. Received flips itself when the whole order is loaded into your binders — in hand is received.

Costs

Beyond the card lines, an order carries three money fields of its own: shipping, fees, and a discount (a bundle deal, store credit). The order total is items + shipping + fees − discount. These are order-level costs — they count in the Ledger's totals, but never in a set's or a card's number.

The load list — from ledger to binders

Recording a purchase doesn't touch your collection — the cards aren't here yet. When they arrive, Purchases closes the loop, mirroring the sales pick list in reverse:

1. Assign destinations

On each line, the binder icon opens the standard destination picker — choose which binder (or list) those copies will land in. The chosen destination shows as a chip under the card.

2. Work the load list

The load list (tray icon on the purchase) groups every assigned card by destination binder, with Unassigned and missing-binder sections — the same screen shape as the sales pick list, pointed the other way.

3. Load

Load adds every assigned card to its binder — all-or-nothing, with the blockers listed if anything can't land. Each landed position also gets its cost stamped: the price you paid becomes the position's purchase price, so your collection starts remembering what it cost you. Loading the whole order flips it to Received.

Changed your mind?

Revert load — per line or for the whole list — takes the copies back out of the binder and returns the line to pending. It can refuse: if the loaded copies have since been moved, sold or unloaded elsewhere, the revert blocks and tells you why, rather than pulling the wrong cards.

Filters, search and sorting

The list searches by vendor, sorts by date, vendor or total, and filters by date — the same presets and custom range as Sales.

Backups

Account backups include the full purchases ledger — vendors, orders, lines, their destination assignments and load history.