Amazon.com Seller Storefront Daily ASIN & Price Tracker (10 Sellers, Scalable, Sold Detection)
Budget: ₹12,500 – ₹37,500 INR
Project Description:
We are looking for a developer to build an automated scraper / bot to monitor Amazon.com Seller Storefront pages, extract ASINs and their prices daily, and output structured data for business use.
Goal:
To monitor 10 selected seller storefronts on Amazon.com (US)
To track the daily change of ASINs and prices
To detect ASINs that disappeared (assumed sold) and output a "sold ASINs" list
The data will be used internally for business analytics and inventory sourcing decisions.
Target pages:
Amazon.com Seller Storefront (example):
https://www.amazon.com/s?me=SELLER_ID&marketplaceID=ATVPDKIKX0DER
Core Functionalities:
Daily scrape (1 run per day)
For each seller:
Extract ASIN
Extract current price (USD) (without $ symbol, as a number)
Extract date of extraction
For each day, compare with previous day's data. If an ASIN disappears, mark it as "sold".
Output two types of files:
Main Timeseries Table (final business output):
date A_seller_name sales B_seller_name sales C_seller_name sales ...
2025/06/07 B079BVQMNC 130 B00005LEOO 140
2025/06/08 B00HQ4W1QE 140 B000AXTQQDS 140
One column for ASIN
One column for Price (USD)
Each seller gets 2 columns (ASIN and sales)
Table grows vertically (one row per date per ASIN)
No "status" field. Disappearance means sold.
Sold ASINs list (separate output):
Sold Date Seller ID ASIN Product Title (from master table) Last known price
2025/06/08 ACWE9RE1UNZTU B000XXXX Canon XX-XX 199.99
This file helps for "sold" detection and is used for business decisions.
Product title is looked up from ASIN master table (maintained separately).
Additional Notes:
ASIN master table is managed separately. Product title is not included in main timeseries output to keep it clean.
Pagination must be handled correctly. Scrape full seller storefront.
No hard limit per seller. Scrape all items per seller.
Sellers may have varying ASIN counts (average 300 per seller, up to 500 per seller).
Initial scale target:
10 sellers
Approximately 3000 ASINs per day total
Code should be scalable (easy to add more sellers).
Must handle randomized delays, retry logic, User-Agent control to prevent bans.
Proxy support is optional (may add later).
Delivery Requirements:
Code (Python preferred but flexible).
Deployment instructions (Dockerized or simple VPS deployable is ideal).
Outputs as CSV or GoogleSheet sync (Google API is acceptable).
Clear config file for Seller IDs (easy to add or remove sellers).
Out of scope:
Any Japan domestic market features (example: Yahoo auctions) are not required.
Summary:
Simple and clean daily ASIN and price tracker for Amazon seller storefronts.
Detect sold ASINs (based on disappearance).
Outputs:
Timeseries table
Sold ASINs list
Budget:
Please provide your quote. Target budget is 400 to 600 USD for MVP (negotiable if scope matches).
Ready to proceed immediately.
We are looking for a developer to build an automated scraper / bot to monitor Amazon.com Seller Storefront pages, extract ASINs and their prices daily, and output structured data for business use.
Goal:
To monitor 10 selected seller storefronts on Amazon.com (US)
To track the daily change of ASINs and prices
To detect ASINs that disappeared (assumed sold) and output a "sold ASINs" list
The data will be used internally for business analytics and inventory sourcing decisions.
Target pages:
Amazon.com Seller Storefront (example):
https://www.amazon.com/s?me=SELLER_ID&marketplaceID=ATVPDKIKX0DER
Core Functionalities:
Daily scrape (1 run per day)
For each seller:
Extract ASIN
Extract current price (USD) (without $ symbol, as a number)
Extract date of extraction
For each day, compare with previous day's data. If an ASIN disappears, mark it as "sold".
Output two types of files:
Main Timeseries Table (final business output):
date A_seller_name sales B_seller_name sales C_seller_name sales ...
2025/06/07 B079BVQMNC 130 B00005LEOO 140
2025/06/08 B00HQ4W1QE 140 B000AXTQQDS 140
One column for ASIN
One column for Price (USD)
Each seller gets 2 columns (ASIN and sales)
Table grows vertically (one row per date per ASIN)
No "status" field. Disappearance means sold.
Sold ASINs list (separate output):
Sold Date Seller ID ASIN Product Title (from master table) Last known price
2025/06/08 ACWE9RE1UNZTU B000XXXX Canon XX-XX 199.99
This file helps for "sold" detection and is used for business decisions.
Product title is looked up from ASIN master table (maintained separately).
Additional Notes:
ASIN master table is managed separately. Product title is not included in main timeseries output to keep it clean.
Pagination must be handled correctly. Scrape full seller storefront.
No hard limit per seller. Scrape all items per seller.
Sellers may have varying ASIN counts (average 300 per seller, up to 500 per seller).
Initial scale target:
10 sellers
Approximately 3000 ASINs per day total
Code should be scalable (easy to add more sellers).
Must handle randomized delays, retry logic, User-Agent control to prevent bans.
Proxy support is optional (may add later).
Delivery Requirements:
Code (Python preferred but flexible).
Deployment instructions (Dockerized or simple VPS deployable is ideal).
Outputs as CSV or GoogleSheet sync (Google API is acceptable).
Clear config file for Seller IDs (easy to add or remove sellers).
Out of scope:
Any Japan domestic market features (example: Yahoo auctions) are not required.
Summary:
Simple and clean daily ASIN and price tracker for Amazon seller storefronts.
Detect sold ASINs (based on disappearance).
Outputs:
Timeseries table
Sold ASINs list
Budget:
Please provide your quote. Target budget is 400 to 600 USD for MVP (negotiable if scope matches).
Ready to proceed immediately.