
Python web scraper for e-commerce site → Google Sheets
- or -
Post a project like this- Posted:
- Proposals: 33
- Remote
- #4515187
- OPPORTUNITY
- Open for Proposals












Description
a Python developer to build a scheduled web scraper for one
competitor site in the outdoor-gear e-commerce space. This is the
first of around seven similar scripts we plan to commission over the
next quarter, so we're really looking for someone we can keep
working with.
What we need
– Python scraper for a single publicly accessible e-commerce site
– Product fields: name, SKU, price, sale price, stock status,
category, product URL, main image URL
– Pagination and category-level crawling
– Respectful crawling — user-agent, rate limiting, retries, error
handling
– Output into a Google Sheet via the Sheets API, with append and
overwrite modes
– Scheduled daily run — GitHub Actions, VPS cron, or Cloud Run,
whichever you'd recommend; we cover the infra
– Failure alert via email or Telegram
– README with setup and env-variable list
What we provide once we agree
– The target site and a sample product page
– Google service account for the Sheets API
– Private repo access for delivery
– One week of paid follow-up support if small tweaks come up
Stack is your call — BeautifulSoup, Scrapy or Playwright all work.
Readable, well-structured code matters more than a heavy framework.
If this first scraper goes well we have six to eight more sites of
similar complexity lined up. We're not chasing the lowest bid; we're
looking for a reliable collaborator.
Liam K.
0% (0)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

-/ Should each daily run replace the entire Google Sheet with the latest product snapshot, or do you also want historical price/stock changes preserved?
-/ Should products be identified and updated primarily by SKU, product URL, or another unique identifier?
-/ Do you want all categories from the competitor site crawled automatically, or only selected categories provided by your team?
-/ If a product disappears from the website, should it be removed from the Sheet, marked unavailable, or retained for historical tracking? -

do you expect the seven to eight additional sites to share a similar product structure, or should the first scraper establish a common adapter/interface pattern that allows each site to have its own parser while sharing the crawling, scheduling, Sheets, logging, and alerting infrastructure?
