datawebotCatalogue export
From a storefront URL to a usable CSV.
Start with a supported Shopify storefront, set a page budget, inspect the returned products and variants, then download a file for analysis. A bounded result is not a claim to the merchant’s full inventory.
01 / SOURCEStore URL
02 / SCOPECatalogue and follow limits
03 / FILECSV with source context
Set the scope before the run
A store URL starts at its accessible catalogue. Choose the maximum page visits and credits, then decide whether the run may follow pagination, product details or collections. The default scope is deliberately small. A currency check or discovery visit also counts toward the budget.
| Control | What it changes | Practical check |
|---|---|---|
| Page and credit maximum | Hard upper bound on source visits | Review the estimate before authorizing the run. |
| Pagination | Additional listing pages | Use only if the first page shows a meaningful continuation. |
| Product details | Additional product pages | Spend these visits when the listing omits fields you need. |
| Collections | Collection directory and selected collection pages | Keep distinct collections and duplicate products in view. |
Check the file before importing it
- Inspect product count, variant count, warnings and completeness in the saved run.
- Check a sample product against its source URL and retrieval time.
- Keep product and variant identifiers as separate columns; do not use titles as stable keys.
- Download CSV within seven days, then store the file and its run context in your own system.
Download a synthetic catalog CSV to inspect the column layout. Every row is fictional; the file has no source URL, retrieval time or live offer values.