Spreadsheet-first workflow
Many Amazon data projects start with a spreadsheet because the first user is an operator, analyst or founder. ParseShelf supports that path directly through CSV and XLSX exports that preserve normalized product fields.
A developer can create the job through the API, while the analyst receives a signed export link or workbook. The same job remains visible in the dashboard for review.
Recommended columns
Keep asin, title, brand, price, currency, rating, reviews_count, stock_status, stock_text, category_path and product_url in the first sheet. These fields cover the majority of product research, competitor pricing and catalog QA use cases.
For search and category jobs, keep source_url and position as well. They explain where a product came from and make rank changes auditable. product_id remains available only as a compatibility alias.
Refresh pattern
For recurring reports, create a fresh job for each date or campaign instead of overwriting one spreadsheet forever. Historical sheets make it easier to compare price, stock and review changes over time.
If the team later needs automation, the same exported rows can move into JSONL or warehouse imports without changing the source workflow.
Production checklist
Start with one small input and compare the delivered fields with the report, catalog or pipeline you actually need.
Keep the job ID, source URL, mode and run date with downstream exports so operators and developers can audit the same result.