Structure messy product information
Extract options, sizes and pack counts from product descriptions and sourcing notes into fields a seller can verify. Ambiguity stays visible instead of becoming a confident guess.
COMMERCE OPERATIONS · EARLY PRODUCT DIRECTIONLess repetitive seller work.
Less repetitive seller work.
More confident checks.
Product listings, sourcing conditions, orders and settlement records often live in separate places. SellerFlow is an existing local-first prototype built to bring that work into one workflow. Our next direction is to evaluate Claude API for reading complex information and preparing clear, reviewable actions.
Existing local-first prototype
Claude API integration planned
Human approval for consequential actions
01 / PRODUCT DIRECTION
Small sellers do not need one more dashboard.
They need fewer mistakes across notes, marketplaces and order records. Our product direction starts with three narrow, practical tasks.
Draft policy-grounded support replies
Use seller-supplied shipping, exchange and refund rules to prepare customer-support drafts with supporting policy references. The seller checks and sends the final reply.
Review operational exceptions
Summarize product notes, order states and settlement records into a short list of items requiring attention. Financial calculations and final confirmations remain deterministic and human-controlled.
02 / HOW CLAUDE FITS
Language understanding by Claude. Records and decisions kept separate.
This is not a plan to let a language model run every business process. Claude API is intended for extracting meaning from unstructured input, while business rules, data storage and approval remain in the application.
01
Seller supplies information
Product notes · sourcing details · policies
02
Claude API interprets
Structured fields · summaries · uncertainties
03
SellerFlow validates
Compare saved records · deterministic checks
04
Human approves
No unreviewed purchasing or customer replies
WHY CLAUDE API
Evaluate quality on realistic operational samples.
Product-field extraction
Track accuracy and failure cases for variants, bundles and inconsistent descriptions.
Grounding in seller policies
Check whether drafts stay within supplied evidence and acknowledge missing rules.
Latency and API economics
Measure cost, response time and recovery behavior across routine and longer inputs.
03 / BUILD STATUS
A clear distinction between what exists and what comes next.
We believe early-stage work should be described with the same care as a finished product.
SellerFlow v2.18
A Windows local web app for organizing product sourcing, pricing, orders, purchasing, shipping and settlement. Built with Python and SQLite. Further development is currently paused.
- Supplier pricing and product price history
- Estimated vs. verified settlement profit
- Review checkpoints and backup/restore safeguards
Shortform Intelligence OS
A React-based frontend prototype for creator research and production handoffs. Live third-party AI integrations remain unverified.
Claude-assisted Operations
Claude features are not presented as already integrated. Initial experiments will focus on product extraction, policy-grounded response drafts, and reviewable operational summaries.
EARLY-STAGE INQUIRIES
Email the team ↗Interested in less manual overhead for seller operations?
Questions about the product direction, technical work or a possible future pilot are welcome. No commercial service has launched yet.