Listing automation
A private local-first system intended to replace Spadeberry while keeping personal photos and processing on owner-controlled infrastructure. Its core pipeline, review workbench, and deployment contract are built; Nifty remains the separate cross-listing tool, and production publishing remains disabled.
Local listing workbench
Private local system · production publishing disabledPreparing 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.
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.
Folder-based intake and processing feed the built review workbench, where required data and a human-confirmed standardized size gate approval. Per-item and batch publishing and verification are implemented, but a real eBay sandbox publish-retrieve-verify run still requires developer access, credentials, configuration, safe fixture URLs, and explicit authorization.
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 until sandbox proof succeeds and a separate rollout is approved.
Private local-first workflow; production publishing remains disabled pending sandbox proof and approval
Maintain the completed 51-item evaluation record, obtain the required sandbox access and configuration, record an authorized end-to-end sandbox run, and seek separate approval before production rollout.