Automate Daily Tender & Bid Reports

@mkh559a5a1fd66e9

As a seasoned Python developer with an extensive background in automation, I am confident in my ability to successfully automate your daily tender and bid reports. My expertise in web scraping using tools such as BeautifulSoup aligns perfectly with your project requirements. By utilizing these skills, we can efficiently retrieve data from not just government portals like GeM, CPPP, and IREPS but also private portals that we'll agree upon. At the heart of my approach is not only the creation of a reliable and efficient script but also ensuring its accuracy and punctuality. I have experience in handling captchas and building robust data pipelines that keep up with changing website structures. My knowledge in file handling makes data cleaning and structuring for your Excel report an easy task. In addition to technical skills, I value clear documentation and effective collaboration. I will provide not just a working script for you, but also a simple read-me that explains setup, credentials management, and even how to add new sources later. This means that even if changes arise or if you decide to expand the project's scope, you can count on me to handle those adjustments elegantly. Let's transform what is currently a time-consuming manual process into an efficient automated workflow together.

@Hrolgar

GeM, CPPP, and IREPS each handle authentication and search URLs differently, so the design that makes this maintainable is per-portal adapter modules feeding a shared output schema. Adding a private portal later is a config change, not a rewrite. The pipeline runs on cron at a fixed local time. Each adapter authenticates, pulls tenders posted since yesterday, cleans to your six fields (title, publishing authority, reference number, value band, closing date, URL), deduplicates across portals, and drops a structured Excel into your inbox before business hours. Captchas that expose a solver endpoint are handled inline; persistent ones fall back to 2Captcha (paid, optional) or flag a "needs human attention" log line so nothing silently drops. Transient site failures get retry-with-backoff; a missed-run alert fires if the morning delivery does not complete. Milestones: M1 (INR 4200, 2d): GeM connector end-to-end, auth + search + parse + sample Excel export, README scaffold M2 (INR 4200, 2d): CPPP + IREPS adapters, cross-portal dedupe, unified Excel formatter with all required fields M3 (INR 3600, 2d): Daily scheduler, inbox delivery, missed-run alert, credentials management doc and "how to add a portal" guide Effort: AI-assisted dev ~5h, human review and integration ~5h. One thing to confirm before M1: do you have GeM credentials in hand already, and are there specific private portals you want included in M2 versus later phases?