Scan-to-confirm for label printing

The most expensive shipping mistake is sending the wrong card. Two PSA 9 Charizards look identical at arm's length; one's a $400 sale and the other is a $40 sale. CardDealer's scan-to-confirm interlock turns the slab label you already print at intake into a hardware-level safety net.

Two flows, same protection

CardDealer's /orders queue accepts two distinct scan inputs, and the input field auto-focuses on every page load. Plug in any USB barcode scanner and start scanning — no setup, no driver tweaks.

Picklist-first (paper-driven)

Best for dealers shipping more than ~5 orders a day, or anyone who likes batching by physical location.

1. Open Tools ▾ → Pull sheet from the queue. Each row has a printed Code128 barcode beside the order #.
2. Walk your storage with the printed sheet. Pull every card into one tote.
3. Back at your desk, scan a row's barcode. CardDealer opens that order with the scan-to-confirm gate already engaged.
4. Scan the actual card's slab label. If the SKUs match, Buy + print unlocks. If they don't, you see a red callout — "Wrong card. Looking for PSA-87654321, scanned PSA-99887766." Find the right slab, scan again.
5. Click Buy. The label prints to your default printer.

Card-first (no paper)

Best for dealers running 1–5 orders a day or shipping ad-hoc throughout the week.

1. Open /orders. The scan input is auto-focused.
2. Pick up any card from your pile. Scan it.
3. CardDealer finds the matching awaiting order, routes you to its detail page, and counts the scan as the confirmation. Buy + print is unlocked immediately.
4. Click Buy. Label prints. Pick up next card. Repeat.

Both flows audit every scan + override into the easypost_shipment.rawResponse.scanAudit field — if disputes ever come up, you have the receipt trail.

Strict mode

By default the scan-to-confirm gate only engages when the dealer arrives via a picklist scan. Manual navigation (clicking an order from the queue) treats Buy + print as ready immediately — you're already in front of the right card.

To require a scan on every label buy regardless of how you arrived, flip the "Strict mode" toggle in /settings/shipping → Scan-to-confirm card. Higher-volume operations sometimes want this.

What you'll need

• A USB barcode scanner, plus any scanner shorts under $50 on Amazon will read Code128. Most are plug-and-play — no software install on your computer.
• Printed slab labels with SKUs on every card you sell. CardDealer auto-prints these at intake when you connect PrintNode.
• PrintNode for the actual label printing (/settings/printer walks the setup).
• EasyPost for the shipping rates + label purchase (/settings/shipping walks the setup).

Override path

When a slab label faded, peeled, or never got printed, you don't want the scan gate to block you forever. Click "I'll verify manually" inside the scan panel and type a one-line reason (e.g. "label peeled — verified by photo cross-check"). The override gets stamped onto the order's audit trail so you can spot patterns later.

Why the audit trail matters

Every successful scan, every mismatch attempt, and every manual override writes a row capturing what was scanned, what was expected, and (for overrides) the reason. If you ever ship the wrong card and dispute the buyer's claim, you can pull the audit trail to show what happened.

We don't surface the trail in a UI yet — it's stored on each easypost_shipment row's rawResponse.scanAudit field. Email us if you need a report; that's the kind of feature we'll build when there's a real reason to.