A singles storage map that tells staff where the sellable copy is

The inventory screen says the shop owns six Near Mint copies. One is in the display case, three are in a set box, one was pulled for an online order, and one is still in a trade-processing tray. A quantity of six is true, but it is not enough to help the employee find the next copy.

Singles storage needs identity, state, and physical location.

Build a hierarchy employees can walk

Use names that match the room:

Sales Floor > Singles Wall > Cabinet B > Shelf 3 > Box MOD-12 > Row 4

Avoid locations such as Box 7 when several rooms contain a Box 7. A complete location should lead a new employee from the room to the row without tribal knowledge.

Put a stable label on every container

Each shelf, box, and row needs a stable identifier that survives reorganizing.

Example labels:

• SF-CAB-B-S3 for Sales Floor, Cabinet B, Shelf 3;
• MOD-12 for the modern singles box;
• MOD-12-R4 for Row 4;
• QR code that resolves the same storage record.

Do not encode every current rule into the label. A box can change from one set range to another without needing a new physical identity.

Distinguish stored from picked

A card pulled for an order is still owned by the shop but is no longer in its normal row.

Use clear states:

• Incoming: received but not reconciled;
• Received: identity and quantity confirmed;
• Stored: physically placed in the assigned location;
• Picked: removed from storage for an order, event, or other action;
• Sold or removed: no longer on hand.

If the sixth copy is picked, the system should not send another employee to Row 4 looking for it.

Use guided placement rules

A row may hold more than one game or set. Keep the rule understandable.

Example:

Priority	Match	Destination
1	Set A, all finishes	MOD-12-R1
2	Set B, collector 1-180	MOD-12-R2
3	Set B, collector 181+	MOD-12-R3
4	Unmatched modern singles	STAGE-MOD

When a card matches no rule or the row is full, leave it staged for a person. Do not silently place it in a nearby row.

Define capacity in the unit employees use

A row can have:

• item capacity, such as 800 cards;
• container capacity, such as 6 deck boxes;
• unenforced capacity when a reliable number is not practical.

If Row 4 holds 760 cards with an 800-card capacity, an automatic move of 100 should split only if the shop's workflow supports a deliberate second destination. The remaining 60 should stay visible for placement.

Move exact records, not the current screen

Suppose an employee filters for Set B and sees the first 100 of 438 matching records. "Move all results" must not mean move only the visible page.

Use one of:

• exact selected inventory IDs;
• a server-resolved filtered snapshot;
• a durable selection token;
• a background move job that processes the complete scope.

Confirm the count before the physical move begins.

Make the physical and digital move one workflow

For a move from MOD-12-R2 to MOD-18-R1:

1. select or resolve the complete item scope;
2. confirm source, destination, and capacity;
3. create a move record;
4. physically move and count the cards;
5. confirm completed quantity;
6. leave exceptions at the source or staging area;
7. record employee and time.

Do not update the screen Friday and plan to move the box Monday.

Use this storage audit

• Room / shelf / box / row labels are unique.
• Every stored item resolves to a physical location.
• Picked items leave their storage row state.
• Staged items remain visible as work.
• Placement rules are readable by staff.
• Capacity uses a meaningful unit.
• Bulk moves cover the full selected scope.
• Digital and physical moves are confirmed together.
• QR labels resolve the current storage record.

Inventory quantity answers "do we own it?" A storage map answers the question the employee at the case actually has: "where is the copy I can sell?"