A former FBA seller (RA/OA background) is building a new sourcing tool and asking the community directly: what features matter, what frustrates you about current options, and would you actually use a unified mobile + web + browser extension solution?
This is a chance to shape a tool around real seller pain points rather than guesswork.
The Proposed Solution
Multi-surface approach:
- Mobile app: Barcode scanning in-store with instant profit estimates (after FBA fees and shipping), sales rank, and buy/skip recommendation
- Web app: Desk research version for deeper analysis
- Browser extension: Quick deal-checking while browsing
- Design philosophy: Single-screen simplicity, no subscription bloat
Key Questions the Builder Is Asking
- Do you currently use a sourcing tool? If so, which one—and what do you dislike about it?
- Which interface (mobile, web, browser, or mix) would you actually use most?
- What’s your absolute minimum feature set to replace what you have now?
- Would early-access pricing incentivize you to switch?
The builder is explicitly open to learning this is already a solved problem—validation beats false confidence.
Why This Matters
Sourceing tool selection directly impacts your sourcing speed, accuracy, and profitability per unit. If your current tool is slowing you down, introducing friction across devices, or charging for features you don’t use, this research phase is your chance to speak up before launch.
How Squatio Helps
If you’re evaluating sourcing workflows, Prospect (Product Database) lets you search and filter products by category, price, and demand signals without leaving the app—complementing barcode scanning with deeper market context. For sellers exploring new niches or validating sourcing categories, Cortex (AI niche & category analysis) can help you identify which product categories are worth sourcing into in the first place, so your sourcing tool time is spent on high-potential SKUs, not dead ends.
Discussion
What’s the single biggest friction point in your current sourcing workflow—is it the lookup speed, missing data fields, needing to switch between tools, or something else entirely?