Product parsing
Let's keep working
Budget: 700 UAH Deadline: 1 day
👋 Hello! I am ready to start working right now. I clearly understand the task and have successful experience in implementing exactly such projects (examples are in the reviews). I will complete the task with high quality and without unnecessary questions. Let's discuss the details and get started! 🚀
Budget: 700 UAH Deadline: 1 day
Good day. I create parsers that work stably and restart themselves in case of errors. I will be happy to help you.
Budget: 1000 UAH Deadline: 1 day
Hello. I have experience, but I am interested in what is an adequate price for you?
Budget: 2000 UAH Deadline: 3 days
I have familiarized myself with the task. I understand that regular parsing of products from various websites is needed, with the possibility of long-term cooperation.
I have basic experience in data collection and processing, have worked with parsing and structuring information. I understand that each website has its own structure, so the approach may differ.
I can start working on:
— collecting products (name, price, description, specifications, etc.)
— formatting the data into a convenient format
— working on a permanent basis
I am ready to discuss the details and an example of the task.
Thank you.
Budget: 2000 UAH Deadline: 1 day
Good day!
I have experience in parsing products from online stores, structuring data, and preparing results in a convenient format for further work.
I have worked on both one-time tasks and regular data collection, where stability, accuracy, and the ability to scale the process for large volumes are important.
I suggest discussing the details, as well as the cost and timelines, in private messages.
Budget: 700 UAH Deadline: 1 day
Good day, let's start with examples and references. I think I can offer a reasonable price, but first, it is necessary to understand where it comes from, in what format, and in what volumes.
Budget: 700 UAH Deadline: 1 day
Ready to work, have experience with Polish sites like x com, euro com, for goodop, prom, using AI. Write to discuss.
Budget: 700 UAH Deadline: 2 days
I have been doing parsing for a long time. I mainly parse for Opencart, Prom, Khoroshop... I have parsed both Ukrainian sites and Polish, European... Write to me in private for details...
Budget: 700 UAH Deadline: 2 days
Hello! I am ready to complete your task, I have experience working with similar tasks.
Budget: 1000 UAH Deadline: 1 day
Ready for cooperation
Ready for cooperation
Ready for cooperation
Ready for cooperation
Ready for cooperation
Ready for cooperation
Budget: 700 UAH Deadline: 1 day
Hello!
I regularly engage in parsing from various sources.
Write to me privately to discuss the details of cooperation.
Budget: 700 UAH Deadline: 1 day
Ready for cooperation
Budget: 775 UAH Deadline: 4 days
Good day
I have been doing parsing for several years
Write to me, we will discuss the details
Budget: 700 UAH Deadline: 3 days
Good day or Good evening!
I have significant experience in creating reliable parsers, particularly for products, using APIs, proxies, and bypassing protection. I am ready to responsibly and efficiently implement continuous parsing of stores in Ukraine and Poland.
Write to me in private messages, and we will clarify the details.
Budget: 2000 UAH Deadline: 1 day
Hello.
I develop parsers in NodeJS. I have experience with various websites. Write to me, we will discuss.
Budget: 1500 UAH Deadline: 1 day
Good day, the price is indicated for one source, write to discuss. Thank you in advance.
Budget: 700 UAH Deadline: 1 day
Good day
I am interested in your project.
I would like to discuss everything in more detail.
Budget: 700 UAH Deadline: 1 day
Hello! I have experience in parsing using Python (Bs4, requests, selenium). Show me the sources that need to be parsed, and I will start working on it today.
Budget: 700 UAH Deadline: 1 day
Hello, I am a Python developer, I have experience in developing parsers of varying complexity. I can complete your project quickly and efficiently. Write to me - we will discuss the details. I am ready to start working today.
Budget: 1000 UAH Deadline: 1 day
Good day. I have extensive experience in parsing. The price depends on the complexity/protection of the website. Feel free to contact me, we will discuss, I will be happy to collaborate.
Budget: 700 UAH Deadline: 1 day
Good day, I am ready to complete your task quickly and efficiently. I have extensive experience in creating various parsers. Please write to me in private messages to discuss the details. I will be happy to help)
Budget: 1000 UAH Deadline: 1 day
I have been engaged in parsing for more than 15 years, I write parsers, etc. Almost everything can be parsed. What is an adequate price for you? The price often depends on the complexity of the site (protection/blocking/logic) and a little on the number of products (there is a difference between parsing 10,000 products and 1 million). We need to discuss.
Budget: 700 UAH Deadline: 3 days
Hello! I have reviewed your project and am ready to start working. I can guarantee excellent results in a short time.
Budget: 700 UAH Deadline: 3 days
Good day.
Let's please discuss the task in more detail.
Budget: 799 UAH Deadline: 1 day
Good day. I have good experience in parsing various platforms. Feel free to contact me, I will show examples and will be happy to help you.
Budget: 3700 UAH Deadline: 21 days
Good day! We are the SDEV team, specializing in complex technical solutions, particularly in parsing and automating data collection. We have extensive experience working with online stores in Ukraine and Poland, including bypassing protections (Cloudflare, CAPTCHAs, dynamic websites on JavaScript), working with proxies, authorization, and stable data collection on a regular basis.
We can set up a full-fledged parsing system: from collecting products, prices, availability, photos to their structuring and exporting in a convenient format (JSON, CSV, Google Sheets, databases, etc.). We also implement monitoring of changes (for example, price drops or new items) and notifications.
We are ready for close collaboration, regular updates, and scaling the system. We work transparently, with logging, error monitoring, and technical support.
More about us and our projects — at https://s-dev.tech/freelance
Budget: 700 UAH Deadline: 7 days
Ready to cooperate.
Budget: 998 UAH Deadline: 1 day
Hello. I am interested in your project. I am ready to discuss and complete it!
Budget: 700 UAH Deadline: 1 day
Good day. We have already worked with you, completed data collection from several stores and prepared for import to yours. I am ready to continue.
Good day! Two tasks need to be completed: 1. Develop a product parser from an external website (10–40 thousand items, marketplace) with structured data saved in MySQL for subsequent output in WordPress. 2. Install and configure n8n on VPS, as well as organize AI content processing: prompt setup, text rewriting, image processing, SEO optimization, and text checking for AI detection. You can estimate the cost of completing both the entire project and each task separately. .
It is necessary to perform parsing from Viber channels (Total number - 49 channels, about 80 thousand subscribers).
An independent service handler for Excel files is required for the existing microservices system. The task involves creating a reliable pipeline for receiving, validating, and transforming data from tables into a structured database format. Functional tasks: Development of an API based on gRPC for receiving processing commands and returning execution statuses. Implementation of file parsing logic: reading large volumes of data (XLSX), cleaning, type checking, and mapping to business models. Implementation of a data access layer (Repository/Unit of Work) for saving results in PostgreSQL via Entity Framework Core. Ensuring thread safety and efficient resource usage (especially when processing large files). Technical requirements: Platform: .NET 10. Architectural patterns: Dependency Injection, CQRS, modular project architecture. Communication: Strictly gRPC. Working with Excel: Use of efficient libraries (e.g., EPPlus, OpenXML, or similar of your choice). Modularity: Code should be organized so that the service is easily scalable and testable. Expected results: A fully functional microservice ready for deployment in a containerized environment. A clean codebase adhering to SOLID principles. Documented .proto files. Basic unit tests for critical data processing nodes. Candidate requirements: In your response, please specify: Your experience with .NET in microservices architecture. Examples of how you organize DI and modularity in your projects. Experience with Excel libraries in .NET. Willingness to work with gRPC contracts.
Good afternoon. I need a keyword parser that outputs results through a Telegram bot. How it should work: Automatic search on 4 websites for keywords that change from time to time. Search queries are sent every few minutes. The words are uploaded in the form of a .txt file. The Telegram bot should have buttons: start bot, stop bot, download file (downloads a file with active keywords), upload file (uploads an edited file with new words). The bot should ignore previously found results, i.e., it should not indicate the same ad twice. The result comes to the bot in the form of a link with a photo, but just a link is sufficient. P.S. searching websites without API, VPS with 6TB and 50 IPs are already available. For detailed information, please contact me via private message.
Task: one dashboard with all business metrics — advertising, funnel, payments, manager performance, revenue planning. Data is pulled automatically via API. Scope: only the YCL direction (employment in Europe). Kommo has other directions — only YCL funnel deals will be included in the repository (filter by funnel/tag to be agreed upon).1. Data Sources (Integrations) Kommo CRM — leads, deals, funnel stages, responsible persons, sources, dates of transitions between stages (must keep history), reasons for refusals, custom deal fields (see point 2). Stripe — payments, amounts, statuses (success/failure/refund), linked to deals. Meta Ads — expenses, impressions, clicks, CPL, leads by campaigns (currently operational). Google Ads, Reddit Ads, LinkedIn Ads — planned; architecture — extensible connectors without core rework. SEO/organic— Google Search Console + GA4. Cross-link: traffic source → lead in Kommo → payment in Stripe (UTM, deal ID in Stripe metadata — propose the mechanism). 2. Mandatory Cuts (Deal Fields in Kommo) Each metric must be filtered/grouped by: Client Citizenship (Kenya, Nigeria, India, etc.). Residence Status: lives in their country / expat (already in Europe). These are two different segments with different cycles, conversion rates, and checks. Country of Placement / Service: Poland, Serbia, Slovakia, Germany (ZAV). Manager, team, traffic channel, period. If any fields are missing in Kommo — the executor indicates which fields need to be added, the client adds them.3. Funnel and Leading Indicators Data by funnel, for each stage — summary and leading metrics: Traffic → lead: leads, CPL by channels + day-to-day expense/click dynamics. Lead → qualification: conversion + first response speed, touches/calls to the manager per day, unanswered leads. Qualification → contract/invoice: conversion + sent offers, stalled deals (days in stage above norm). Invoice → payment: payments, average check + unpaid invoices, failed payments. Summary: revenue, ROMI by channels, run rate to monthly plan. 4. Deal Cycle Average and median lead → payment cycle (business benchmark ~4 weeks), cycle trend over time. Breakdown of cycle by stages (how many days a deal sits at each stage) — to see which stage is dragging. List of deals that have stalled at a stage longer than normal. Cycle breakdown by segments: citizenship, residence status, country of placement, manager. 5. Early Warning of Decline (Key Block) Since the cycle is ~4 weeks, today's leads = payments in a month. The system must: Compare leads/qualifications of the current week with the moving average (4 weeks) and issue an alert if there is a downward deviation: “leads -X%, with a 4-week cycle expect a payment decline in the week [date].” Build payment forecast for 4 weeks ahead from the current pipeline: deals at each stage × historical conversion of the stage × remaining cycle. Highlight in red weeks where the forecast is below plan — with time to react. 6. Additional Payments and Sales Planning In the Kommo deal card, the date and amount of the planned additional payment are stored. The system must: Collect a calendar of upcoming additional payments: total expected, by weeks/months. Highlight overdue additional payments (date passed, no payments in Stripe) — a separate list for follow-up. Calculate the monthly plan as: plan − already paid − scheduled additional payments = how many new sales are needed (in money and in deal units at average check). Weekly schedule: additional payments + forecast of new payments against the weekly plan. 7. Manager Performance Daily snapshot for each manager: touches/calls, conversations, sent offers, payments — for each day separately, with a chart over the period. Progress on personal plan compared to monthly pace (ahead / on pace / behind). Benchmarking with colleagues. 8. Visualization and Roles “Traffic lights” (green/yellow/red) for key metrics relative to norms/plans; progress scales; trend graphs; mobile adaptive. Roles: CEO — everything; COO — entire funnel and managers; team lead — their team; manager — their metrics and position relative to colleagues. 9. Reports and AI Automated reports on schedule (daily summary, weekly report) in the dashboard and/or messenger. Free-form queries (“how has CPL from Meta changed over 2 weeks?”) — LLM over the repository. Alerts in the red zone and according to the rules from points 5–6. 10. Technical Expectations and Staging Repository (PostgreSQL/BigQuery or equivalent) + ETL: Kommo webhooks + periodic synchronization (15–60 min). Frontend: custom or BI tool — propose with justification; requirements for roles, traffic lights, forecasts, and AI queries must be implementable. Stages: (1) audit and metrics map → (2) MVP: Kommo + Stripe + Meta, funnel, traffic lights, roles → (3) deal cycle, early warning, additional payments and plan → (4) SEO, AI reports, alerts → (5) new advertising channels. Payment is staged, with a demo for each stage. In the response, indicate: similar projects (end-to-end analytics), stack with justification, timeline and cost estimates by stages, monthly ownership cost (hosting, tokens, licenses).