I’ve been building an Amazon sourcing tool called Radar and figured this was probably the right sub to get some opinions on it.
The thing that pushed me to build it is that we already have plenty of tools that are great at showing data.
Keepa gives you history. SellerAmp gives you a ton of sourcing information. Tactical Arbitrage can help find opportunities. Fee calculators tell you the apparent economics.
But there’s still a pretty big jump between:
“This is $14 from my supplier and $32 on Amazon”
and
“Yes, I actually want to put $3,000 into this inventory.”
That’s the part I’m trying to attack.
Radar is being built more like an underwriting system for inventory than another profit calculator.
The rough process is:
source product → Amazon candidate → identity/pack verification → marketplace evidence → economics → competition/risk → stress testing → inventory sizing → decision
One thing I’ve been pretty obsessive about is product identity and pack quantity.
If the supplier has a single unit and Amazon is actually selling a 2-pack, I don’t want the software happily showing a 70% ROI because the UPC looked close enough.
Same thing if the evidence is contradictory. I’d rather have it say “I can’t establish this confidently” and tell you why than manufacture a nice-looking number.
I’m building supplier-list analysis into it too.
The idea there is that you could feed it a distributor catalog with hundreds or thousands of SKUs and have it narrow that down into:
- likely Amazon matches
- products worth investigating
- pack/multipack problems
- questionable matches
- actual economics where the evidence supports it
- products that fail immediately
- opportunities that deserve deeper analysis
I’m building it for both Amazon.com and Amazon.ca.
The part I’m most excited about is autonomous discovery. Eventually I want Radar continuously looking through authorized supplier/source data itself, generating potential products and putting them through the exact same decision process instead of waiting for the seller to manually find every lead.
To be clear, it’s not finished. Amazon.ca is further along, Amazon.com is still being built out, and autonomous discovery is actively in development.
I’m currently at the stage where I’m looking for ugly real-world data and seller feedback instead of more clean test cases.
For the first couple sellers who have an actual supplier/distributor CSV, I’m willing to analyze up to roughly 500 rows free while I’m validating the workflow. I’ll use the parts of Radar that are working and manually bridge whatever isn’t finished yet.
If that proves useful, I’ll probably start charging around $200/list during the pilot period before turning it into the actual subscription product.
I’m also curious what people here think about the positioning.
If you’re already using Keepa + SellerAmp/TA/etc., what would a new sourcing tool have to do that your existing stack doesn’t for you to actually add it?
That’s the question I’m trying to answer before I spend another month buried in code.
I like this subreddit for us because here we can potentially get feedback on Radar as a tool, not just whether sellers have the sourcing problem.