Request type
Product data collection
Names, prices, stock, and any field a store shows.
First release
In scope for the first release.
Who asks for this
Ecommerce operators and agencies.
Say it like this
“Collect the products on these two stores with name, URL, price, currency, availability, and category.”
What you supply
- Store or category URLs
- Product fields
- Include out-of-stock or not
What you get back
Your table · 4 rows shownIllustrative
| product_nametext · collected | urlurl · collected | pricecurrency · collected | currencytext · collected | in_stockboolean · collected | categorytext · collected |
|---|---|---|---|---|---|
| Linen Crew Tee | store-a.example/tee | 38.00 | USD | true | Tops |
| Canvas Weekender | store-a.example/weekender | 148.00 | USD | false | Bags |
| Wool Beanie | store-b.example/beanie | 32.00 | USD | true | — |
| Ripstop Shell | store-b.example/shell | 210.00 | USD | true | Outerwear |
collected from the page · derived at no cost · extra work raises the estimate
Workflow
How the agent handles it.
- 1
You give us store URLs.
- 2
We match a tested recipe and confirm fields.
- 3
You choose columns and approve.
- 4
We collect and normalize prices.
- 5
Export, or save to rerun.
Cost and limits
What moves the price, and where the answer can be no.
Cost drivers
- Catalog size
- Fields only on product pages
- Sites that need a browser
Where we say no first
- Regional or logged-in prices can differ.
- Some marketplaces block automated access. We tell you first.
Early access
Want product data collection?
Describe the sources, the columns, and roughly how many rows.