Autonomous Amazon & Flipkart Crawler
Budget: ₹1,500 – ₹12,500 INR
I need two separate, non-blocking crawlers—one targeting Amazon, the other Flipkart—each operating with our seller accounts. Every 24 hours the system must fetch fresh data for the ASINs I supply: product name, seller name, star rating, ratings count, MRP, and current selling price. The information should be written straight into a MySQL database and the entire cycle has to repeat indefinitely without manual intervention.
Reliability is critical. If either crawler encounters captchas, rate limits, network drops, or any other interruption, it should automatically recover (self-healing logic) and continue from the exact point of failure. Should a fault persist beyond the retry logic, I want an immediate email alert with a concise error report so I can act quickly.
Please structure the project so both crawlers can run independently—separate queues, logs, and threads/processes—while sharing the same MySQL instance. A lightweight dashboard or log file that summarises the last run, next scheduled run, and any error history will help me monitor health at a glance.
Deliverables
• Clean, well-commented source code for both crawlers
• MySQL schema and any migration scripts
• Configuration for scheduling (cron, systemd timer, or equivalent)
• Self-healing and retry mechanisms baked in
• Email notification module with simple SMTP settings file
• README covering setup, environment variables, and how to add new ASINs without touching the code
Feel free to suggest the best stack—Python with Scrapy or Playwright, Node.js with Puppeteer, or another proven toolset—as long as it stays headless, avoids blocking, and scales smoothly.
Reliability is critical. If either crawler encounters captchas, rate limits, network drops, or any other interruption, it should automatically recover (self-healing logic) and continue from the exact point of failure. Should a fault persist beyond the retry logic, I want an immediate email alert with a concise error report so I can act quickly.
Please structure the project so both crawlers can run independently—separate queues, logs, and threads/processes—while sharing the same MySQL instance. A lightweight dashboard or log file that summarises the last run, next scheduled run, and any error history will help me monitor health at a glance.
Deliverables
• Clean, well-commented source code for both crawlers
• MySQL schema and any migration scripts
• Configuration for scheduling (cron, systemd timer, or equivalent)
• Self-healing and retry mechanisms baked in
• Email notification module with simple SMTP settings file
• README covering setup, environment variables, and how to add new ASINs without touching the code
Feel free to suggest the best stack—Python with Scrapy or Playwright, Node.js with Puppeteer, or another proven toolset—as long as it stays headless, avoids blocking, and scales smoothly.
Related categories:
PHP
Business, Accounting, Human Resources & Legal
Python
Web Scraping
Software Architecture
MySQL
Node.js
Scrapy