Supply side
Dropshipper catalog analysis
Uploading a CSV isn’t analysis. Analysis is knowing what you have, what’s stale, and which rows actually connect to demand signals this week. Most sellers skip straight to ‘sync everything’ and wonder why the feed looks random.
What to ingest (and what to skip)
Parseflow ingests CJ via API and arbitrary wholesalers via CSV—title, SKU, category, unit cost, MOQ. That’s the minimum viable row for margin math.
- CJ category sync — broader than the tiny default ‘full catalog’ slice
- Printful / regional CSV exports — great for POD overlap
- Skip: scraping Amazon as ‘supply’ — that’s retail, not wholesale
Quality checks before you blame the matcher
- 1
Costs are real
Re-sync after CJ price changes. A 40% margin that was true Tuesday can be fiction Thursday.
- 2
Titles are searchable
‘SKU-8842-BLK’ helps nobody. Titles should read like buyer queries.
- 3
Categories map to intent
‘Home’ isn’t a niche. ‘Kitchen drawer organizer’ is.
- 4
Archive stale rows
Dead SKUs pollute match confidence. Let the pipeline drop what you can’t fulfill.
From row to opportunity
Each scan tokenizes titles and keywords, compares them to active demand signals, and promotes matches above a confidence floor. You see ranked cards—not a SQL table.
Common catalog mistakes
Questions sellers ask
- How many SKUs do I need?
- Enough coverage in niches you’ll actually market—often 10k–20k across CJ + one CSV. More rows without demand alignment just adds noise.
- Is Wholesale2B required?
- No. CJ + CSV is the free path we optimize for.