Skip to project details
eBay Listing Tool
Menu

Listing automation

eBay Listing Tool

A private listing pipeline and workbench intended to reduce repeated work between local photos, garment processing, and listing review. The processing, media, deployment, and sandbox publish-and-verify paths are built. Nifty remains in the workflow while ordinary-item acceptance and production approval are pending. The planned product name is Buy List Sell.

Private working systemPrivate local-first listing workflow. Sandbox publishing and retrieval verification are complete; ordinary real-item acceptance and separate owner approval for production publishing remain required. Production publishing remains disabled.

Local listing workbench

Private local system · production publishing disabled
Review GridPrivacy-safe representative state
AllReviewDraftApprovedVerifiedFlagged
PHOTOWITHHELDLocal source
LOCAL DRAFT · ITEM WITHHELDListing details stay private until review.
SIZE UNCONFIRMEDHUMAN REVIEW
Required evidenceSize not confirmedHuman confirmation is mandatory
ConditionReview requiredPricing withheld
PUBLISH LOCKEDResolve required fields
01

The problem

Preparing consistent clothing listings requires repeated photo review, tag reading, standardized fields, title construction, pricing checks, condition judgment, and post-publish verification. Those steps need to be dependable without allowing uncertain data or an approval shortcut to publish a listing.

02

The current approach

The system uses a locked local vision model, standardized clothing attributes, deterministic title and description assembly, sold-history and fee calculations, an editable review grid, and explicit publish-and-verify controls.

A local review path

Folder intake, garment processing, review, required listing fields, and explicit confirmation for each applicable “Size reads” field lead into publish preflight. The credentialed sandbox publish, retrieve, and verify path is complete. An ordinary real-item acceptance pass remains pending; production publishing requires separate owner approval.

  • Local photo intake, gemma3:12b structured vision, and bounded clothing attributes
  • Deterministic titles, modular descriptions, fee math, and imported sold-history support
  • Editable review grid with mandatory size evidence, explicit size confirmation, and condition gates
  • Batch publish and verification results plus a Docker and Unraid runtime contract

Safeguards & boundaries

Every standardized size requires explicit human confirmation; anything below Excellent, any possible damage, missing costs, or uncertain required data enters manual review.

Personal photos remain local, Nifty remains the separate cross-listing and per-platform pricing tool, and production publishing stays disabled pending ordinary real-item acceptance and separate owner approval.

Sandbox proof is technical evidence and does not substitute for owner acceptance or approval for day-to-day production publishing.

What supports the status today

Private local-first listing workflow. Sandbox publishing and retrieval verification are complete; ordinary real-item acceptance and separate owner approval for production publishing remain required. Production publishing remains disabled.

  • The latest source-recorded technical checkpoint reports 3,018 tests passed and six skipped; these are recorded results, not tests run for this marketing update.
  • The completed 51-item evaluation records fresh unified two-pass results: gemma3:12b size 49/51 and item type 44/51; gemma3:27b size 47/51 and item type 46/51; the field-wise combination (12b size + 27b item type) gets both priority fields right on 45/51 (88.2%); measurement abstention is 51/51 for both.
  • The pipeline, review workbench, media handling, Docker/Unraid deployment, and sandbox publishing verification are documented; ordinary real-item acceptance remains pending.
Current outcome

A built private workflow with successful sandbox publishing proof; acceptance and production approval govern rollout.

Next step

Complete an ordinary real-item acceptance pass, retain the completed 51-item evaluation record, and obtain separate owner approval before enabling day-to-day production publishing.

Supporting technology
  • Python
  • FastAPI
  • SQLite
  • Ollama
  • eBay APIs
  • Docker
  • pytest
  • Ruff