Python Developer - Marketplace Scraping

We are building a full internal marketplace analytics web system, not just a reporting script. The system is designed to combine competitive intelligence with internal sales and stock analytics in a single interface.

Functional Requirements
The system must provide the following capabilities:

1. Product and SKU structure
- Each product must be split into individual SKUs based on flavor and volume.
- All analytics and reports are built at the SKU level.

2. Our product analytics (primary focus)
- Current stock levels (total and per SKU).
- Sales volume for selected periods (daily / weekly / monthly).
- Reorder recommendations based on stock thresholds and sales dynamics.
- Revenue calculations per product and per SKU with period filtering.

3. Competitive analytics
- Automated collection of publicly available data from competitor product pages.
- Price, rating, review count, order count (if available), “new” status.
- Historical tracking of changes over time.
- Sales and price comparison with competitors by selected period.

4. Analytical dashboards
- KPI cards for key metrics.
- Sales trend charts over time.
- Weekly sales analysis.
- Category-level distribution of sales and revenue.
- SKU-level analysis with the ability to switch between units and monetary values.

5. Reporting and exports
- Excel export generated directly from the system.
- Ability to modify and customize Excel report templates.
- Consistent column structure and formatting.

Technical Requirements
- Python-based backend.
- Web scraping and automation for Uzum and Yandex Market.
- Use of HTTP scraping where possible (Uzum).
- Use of headless browser automation and API/XHR interception for Yandex Market.
- Stable data processing and normalization layer.
- Data storage with historical snapshots.
- API layer for frontend integration.
- Frontend web dashboard (React or similar).

Non-Functional Requirements
- Stable and maintainable architecture.
- Scalable design to support additional marketplaces in the future.
- Clear documentation of key components and logic.
- Compliance with public data usage and technical limitations of marketplaces.

Project Approach
- Development may be done sequentially or in parallel depending on the final team setup.
- The system is intended for long-term internal use, not as a temporary solution.
- NDA will be required before sharing full technical details.

Budget and Timeline
We are open to reasonable and well-justified proposals regarding pricing and timelines.

Show More