Working with batches

A batch is the unit of work for processing a group of cards together. When you import a stack of one-touches, a sealed box you've broken, or 200 PSA submissions that just came back, you create a batch — and every card in that batch shares context: source, settings, defaults, and a single audit trail.

Why batches matter

Most dealers move through inventory in waves: photograph a tray of 50, identify them, price them, list them. Batches let you do all four steps at the level of the wave, not the individual card. That's the difference between an evening of work and a week of work.

Creating a batch

From the sidebar, click Batches → New batch. The current creation form is a single screen with required name + optional details. The Wave 2 wizard refactor (in progress) splits this into two steps:

1. General Settings — name, source, sport, set defaults.
2. Optional Details — price floor, default Marketplace Template, 5-dim location prefix, batch description.

For now, fill in the name and skip the rest unless you have specific defaults you want every card in the batch to inherit.

Batch status

A batch moves through open → processing → complete. While open, you can add more cards. Once complete, the batch is read-only — useful for audit trails ("this batch was the May 10 PSA return, 47 cards").

You can re-open a complete batch from its detail page if you need to add a card.

Bulk actions on a batch

The batch detail page exposes bulk actions across every card in the batch:

• Bulk identify — re-run AI identification on every card.
• Bulk price — pull PriceCharting + eBay comps for every card.
• Bulk list — submit every card to eBay using the batch's default Marketplace Template.
• Bulk export — CSV of every card in the batch with all current fields.
• Bulk move — assign all cards to a 5-dim location (e.g. "everything in this batch lives in Container A, Row 3").

Bulk actions queue as background jobs so you can keep working while they process.

Lock Set (Wave 2)

A coming feature called Lock Set lets you restrict the identification scope of a batch to a single set — useful when you're processing a sealed box and want CardSight to never guess outside that set. Currently in development.