Corridor Listing Pipeline

Every card needs the same detailed steps: identification down to the exact parallel, pricing from recent sales, an 80-character title, the right category and policies, and a record that ties the listing back to a physical storage slot. Done by hand, it’s slow and easy to get subtly wrong.

My part is the first step and the last. Everything in between is code or AI.

1. 01Me: I photograph a batch of cards and drop the photos in a folder.
2. 02Code or AI: Every night it checks the folder, and does nothing unless a complete batch is waiting.
3. 03Code or AI: It checks the photos: the count, the resolution, duplicates, and that the set has stopped changing.
4. 04Code or AI: It numbers the batch and gives each card a storage slot.
5. 05Code or AI: AI identifies each card, and a separate checking harness has to agree.
6. 06Code or AI: It prices each card from sold comps. If it isn’t sure, it leaves the price blank for me.
7. 07Code or AI: It writes titles, categories and item specifics within eBay’s rules.
8. 08Code or AI: It uploads the drafts in bulk, then checks them field by field.
9. 09Me: I review every draft and publish each listing myself. Nothing posts automatically.

• Never guess. Identity, variant, condition, price and shipping policy stay blank when the evidence is weak.
• Nothing is published automatically. Publish actions are prohibited in the code itself.
• One SKU must travel unchanged from photo, to spreadsheet row, to eBay draft, to physical storage slot.
• Every step has to be auditable after the fact, including the ones an AI agent performed.

1. 01

   Fail closed

   Identification only passes when exactly one legal card variant fits and an independent check agrees. Anything ambiguous goes to a review list instead of into a listing.

2. 02

   Sold comps only

   Prices come from completed sales over a set window, never from asking prices. Low-confidence prices are left blank for me to decide.

3. 03

   The SKU is the address

   Each card’s SKU is also its box-section-slot storage location and its eBay custom label, so nothing gets lost between steps.

4. 04

   Keep the evidence

   Every batch keeps its inputs, file hashes and a QA receipt, so any listing can be traced back to the photos and reasoning behind it.

Me, as the seller for Corridor Cards. It runs on a schedule on my own machine.

My hands are on the two ends of every batch: I take the photos and drop them in a folder, and at the end I review and publish every listing. Everything in between is code or AI. I wrote the operating procedure (versioned, with a dated changelog of my corrections), designed the decision rules, and direct the AI agents that do the identification and build steps.

Read the Corridor Cards story→