A developer is required for parsing the catalog and automating data import.

Hello, Tatiana. I looked at your catalog on Lovable. The real challenge here is not in the uCoin catalog itself, but in the second stage, linking PCGS data to the cards. A catalog of ~100,000 coins is large but linear in volume. And going through PCGS page by page makes no sense: they have a Public API (search by cert number, barcode, PCGS number plus grade), which should be the entry point instead of browsing millions of pages. The entire budget for the second stage depends on this, so I won't estimate it blindly.

A bit about me: I have my own production-ready parsing platform that collects large catalogs from several protected sources every day, bypasses anti-bot measures, normalizes and deduplicates data, and loads it in batches into PostgreSQL. So, bypassing Cloudflare at uCoin, mass importing into your Supabase, and entity matching is exactly what I do in production.

How I would do it:
Stage 1 (catalog): collect the structure of uCoin according to your criteria (regular plus anniversary, without collectible and without photos), normalize countries, denominations, years, and attributes, deduplicate, and batch import into your structure on Supabase. A separate import log and a list of cards for manual verification, so that after the upload, we don't have to clean 100,000 records manually. Incremental updates so that the catalog can be refreshed rather than completely re-uploaded.
Stage 2 (PCGS): I start with a short API test on a small sample (which fields and photos are available, what limits, and which attributes reliably match). After the test, I will provide an exact price and timeline.

Regarding your questions:
… 1. I have experience with large catalogs; this is my specialty: parsers in production, anti-bot, normalization, entity matching.
2. I am ready to do Stage 1 for a fixed price of 7,000 UAH in 4-5 days. I will estimate Stage 2 after the API test to avoid giving a blind figure.
3. The main challenges: Cloudflare at uCoin (rotation of residential proxies and request rate), daily limits and access to the PCGS API, careful entity matching, and incremental updates without duplicates.

I suggest starting with Stage 1 as a separate step so you can evaluate the result before tackling PCGS. Is the import needed directly into the Supabase database via the website's backend or into a separate database?

Vladislav

Show original

Translate

Hello! I specialize in parsing large catalogs — I will look at your catalog and gather the import in the required format with further auto-updating. The main difficulties here are usually pagination, variations of positions, and bot protection, but I don't see any problems with a lovable site. I will give a more accurate estimate as soon as I look at the specifications in the attachment. Approximately 3-4 days. In which format should I export — CSV/XLSX or directly import into your database?

Show original

Translate

Good day! Experience working with catalog parsing in Python (BeautifulSoup, Selenium, requests). I have worked with large eCommerce projects and understand the specifics of structured catalogs.
Regarding your project:

— I can implement catalog parsing with automatic data import.

— Possible challenges: anti-scraping protection, dynamic content (JS rendering) — solvable.

— Result: structured data in CSV/Excel/DB.
Estimated cost: 3000–5000 UAH. 3–5 days.
… Please send the technical specifications — I will provide an accurate estimate.

Show original

Translate

Hello! Parsing large catalogs and automating imports is my daily work (in production, parsers for competitors' catalogs with anti-bot bypass, normalization, and AI matching of products). I will look at the technical specifications and provide an exact cost and timeline; the main risks are usually anti-bot protection and unstable layout, which can be resolved. The price in the bid is conditional.

Show original

Translate

Tatiana, the most interesting part of this task lies not in parsing, but in linking two data sources. The 100,000 catalog cards themselves represent a large but fairly linear volume of work. The main complexity arises at the stage of automatically linking PCGS data to the already created cards.

From the description, it seems you already have a working model for importing a single coin through an extension. This is a good sign because the logic for matching entities already partially exists. I would first analyze this process and understand which attributes are actually used to find the corresponding card before launching mass automation.

I also noted the need to iterate through PCGS certificates. If the range indeed spans tens of millions of pages, it would be wise to spend time researching the data structure before development. Often, such sites leave indirect entry points: search queries, internal APIs, sitemaps, archives, or series pages. This will affect the entire budget for the second phase.

In terms of volume, I see this more as a full-fledged project for data collection and normalization rather than a regular parser. I would estimate the catalog stage at about 40–60 hours. The stage for automatically obtaining and matching PCGS data is difficult to estimate without prior research, but realistically, it could take another 40–100+ hours of work. The overall budget appears to be in the range of $1200–3200.

Could you please clarify if the catalog on your site already has stable internal identifiers for coins, or is matching currently only possible by name, year, and other attributes?

Show original

Translate

Hello! The task is completely clear, I specialize in Python parsers and collecting large data catalogs. I saw your site on Lovable — it's a great option, as I will prepare a clean CSV or JSON file for you that you can download with one click for automatic filling of coin cards without the help of programmers.
For the collection, I will use asynchronous scripts with human action simulation and rotating proxies, which will easily bypass the protection of the donor site (like Cloudflare or captchas), intercept dynamic content, and clearly structure all specific numismatic characteristics in separate columns of the database. I am ready to connect today, send the link to the donor site in private messages, and I will calculate everything in detail!

Show original

Translate

Hello! I am a backend developer, working with PHP (CLI/scripts), which is perfect for Big Data without excessive memory load. Your stack on Lovable (React + Supabase/PostgreSQL) is completely clear to me - the import will go directly into the database through batch SQL queries for maximum speed.

Technical vision for implementation:

Stage 1: Parsing uCoin (Skeleton of 100,000 cards)
• Filtering: The script will traverse the uCoin country tree, cutting out collectible sets and collecting only regular and anniversary coins.
• Optimization: We will collect only text (name, year, characteristics). To bypass Cloudflare, I will use header rotation and proxies.

Stage 2: Optimizing PCGS (Instead of 30 million pages)
… • Solution: Iterating through 30 million certificates head-on is inefficient. I will find the internal structure of the site through the Population Report or Set Registry. We will parse the group tables by unique Coin Number, which will reduce the number of queries by thousands of times.
• Proxies and mapping: The script will work through foreign residential proxies (PCGS blocks the CIS). It will automatically extract photos of slabs, grades, certificate numbers, and link them to cards from Stage 1.

The process is divided into two logical steps:

• Stage 1 (uCoin - Catalog Skeleton): Development of a CLI parser and batch import of text into your Supabase database.
Cost: 7000 UAH | Deadline: 4 days (considering proxy runs).

• Stage 2 (PCGS - Photos and Metadata): Automation of bypassing, downloading images, parsing grades, and auto-linking.
Cost: We will estimate after analyzing your database in Stage 1 (approximately $400-500, 7-10 days).

In the bidding field, I indicated the cost for Stage No. 1. I am waiting in private messages to discuss the details!

Show original

Translate

Hello.

I have reviewed the specifications and looked at your catalog on Lovable. For the first phase, I can compile the import of the basic catalog: structure from uCoin, filtering of necessary categories, normalization of countries / denominations / years / attributes, and uploading to your structure on the website.

I will also include a check for duplicates, an import log, and a list of entries that require manual clarification. For such a volume, it is important to avoid cleaning 100,000 cards manually after the import.

Regarding PCGS, I checked the official Public API: it supports searching by cert number, barcode, and PCGS number + grade, but requires an account/API access and has a daily request limit. Therefore, the second phase should start with a technical test of the API on a small sample: to check available fields, photos, limits, and the logic of linking to catalog cards.

I have relevant experience with parsing, catalog normalization, data preparation for import, and working with large volumes of records.
…
Before starting work, I need to clarify:
- which categories from uCoin we are excluding
- whether there is access to Supabase / your website's backend
- which fields are mandatory for the coin card
- whether there is a PCGS account/API access
- whether there is a ready list of cert / PCGSNo for testing

After checking the PCGS API, we can separately finalize the second phase with photos and metadata.

We can discuss the details in private messages.

Show original

Translate

Hello! I have worked on parsing a large amount of graphic data that required further processing and structuring, so I can fulfill your order.

Among the challenges that may arise is bot protection on the websites that need to be parsed, but a way to bypass it can be found.

I can create a structured database from the data extracted from the target websites, or add it to an existing database.

Currently, I can estimate the project at 3000 hryvnias with a deadline of 5-6 days.

Show original

Translate

Hello. From the description, I see the task as parsing a large catalog with subsequent automation of data import. A detailed technical specification is in the attached document; I am ready to study it and provide a specific estimate for cost and timelines.

I have experience working with parsing large catalogs: I have written parsers in Python that are resilient to pagination, dynamic loading, and protections, with data normalization and loading into a database. Typical challenges with large catalogs that I immediately account for include: protection against blocking and throttling requests, rendering JavaScript where data is loaded dynamically, careful deduplication and field matching during import, as well as downloading and updating instead of a full restart, so the catalog can be refreshed incrementally.

To provide accurate figures: I will review your document with the technical specification and look at the catalog via the link. Just let me know where exactly the data needs to be imported: into your website's database on Lovable through its backend or into a separate database. After that, I will return with an exact timeline estimate.

Show original

Translate

Hello! I have extensive experience in data parsing, and you can view my work in the portfolio on the website. I offer quality and fast work. A potential issue is that the pcgs site actively blocks IP addresses due to bots; the solution for this is a residential proxy. Feel free to write.

Show original

Translate

Hello. I have extensive experience in developing parsers in Python. I am ready for collaboration.

Show original

Translate

Hello!

Price and terms: 10,000 UAH, and from 2 days to a maximum of 1 week.

Experience: parsing large catalogs, importing into PostgreSQL, queues, deduplication, resume after failure. I can send some parsers in private messages.

Stage 1
Skeleton like ucoin.net: countries, denominations, years, regular/anniversary. No photos and no unnecessary categories. Filters according to your criteria, import into the structure as on /catalog/usa. Target ~100k cards, in batches with progress logging.

… Stage 2
PCGS: photos + metadata (year, grade, cert, etc.), linking to cards from stage 1. We do not process 20-30 million cert IDs. We are looking for a workaround: site structure, search by attributes, match by country/year/denomination. The logic of your Chrome extension - into automation (Playwright + proxy for US IP). Not every coin will have a cert - some will be manual or a queue of exceptions.

Difficulties
ucoin: rate limit, layout changes. PCGS: geoblock, anti-bot. Matching is not 100%. Mass copying of data/photos - check ToS.

From you: Technical specification from the file, list of excluded categories, access to DB/API, examples of PCGS URLs for testing.

I am ready to clarify the scope after the document.

Show original

Translate

Good day!

Parsing large catalogs is our specialized area, and the task is clear. I will divide the project into two stages, as they differ in complexity.

Stage 1 — catalog ucoin.net → your site (~100,000 cards):

- parsing the structure by criteria (regular mint + anniversary, without collection items);
- cards: country → denomination → type (year, metal, diameter, KM#), without photos and unnecessary details;
- import into your site on Lovable through its backend (Supabase API / bulk-import);
… - we work through proxies and throttling to bypass limits. 100k is a large volume, but entirely feasible.

Stage 2 — PCGS (images + metadata, linking to cards):
Here there is a real limitation that you have noticed yourself. Scraping 20–30 million sequential cert pages is not an option: it would take months of parsing + guaranteed ban, plus PCGS blocks IPs from Ukraine (US-resident proxies are needed).

The correct approach is to first conduct reconnaissance: find the internal API/endpoint of PCGS that returns cert data in a structured format (often such sites load data via a separate JSON request — we will use that instead of scraping HTML). The outcome of the reconnaissance will determine whether full automation is possible or if it will remain semi-automated.

Possible difficulties (as you requested): IP blocking on PCGS, lack of catalog structure on PCGS, linking logic (cert = specific instance, card = type of coin — mapping by denomination/year/grade), anti-bot measures on large volumes.

We have experience in parsing large catalogs. Details about the project, timelines, and costs will be discussed privately. We are ready to start working.

Show original

Translate

Hello. I can implement this project. I have some developments. If it's relevant, write to me, and we will discuss.

Show original

Translate

Good day, I am ready to complete your order and will be happy to collaborate further. Write to me here in private messages, and I will send you examples of my work. I can also send a link to my portfolio.)

Show original

Translate

Ready to complete your task, I have experience, write if needed, then I will analyze and tell you how I see the implementation.

Show original

Translate

Hello.

I am developing parsers in NodeJS. I am ready to take it on. Write to me, and we will discuss.

Show original

Translate

Hello. My name is Dmitry. I am interested in your project. I have experience in developing parsers, working with large product catalogs, and automating data processing with subsequent export to databases, CRMs, and online stores.
I have worked with catalogs containing tens and hundreds of thousands of items, including protection against blocking, scheduled data updates, image processing, characteristics, and categories.
Based on a preliminary assessment, the timelines and costs depend on the volume of data, the structure of the source website, and the requirements for updating the catalog, so after reviewing the full technical specifications, I will be able to provide a more accurate estimate.
Possible challenges usually include limitations from the donor site, protection against parsing, unstable data structure, request speed limitations, and the need for regular synchronization of changes. All of this can be addressed during the design phase of the parser's architecture.
I am ready to review the technical specifications and propose the optimal implementation option considering the future scaling of the project. 👍

Show original

Translate

Hello.
I am ready to take on the project as a Python developer.
I have experience in parsing large catalogs, processing large volumes of data, normalizing attributes, removing duplicates, and importing data into a website/database/API. For implementation, I can use Python, Scrapy/BeautifulSoup, Playwright/Selenium, requests/aiohttp, PostgreSQL/MySQL, queues, and logging.

Show original

Translate

Hello! I will take on the parsing of the catalog and automated data import.

I looked at your catalog (coin catalog on lovable.app) — I will collect all positions with the required fields (name, year, description, price, image, ID/link) and set up automatic import into your system.

I answer your questions:
1. Cost — within your budget; the timeframe is approximately 4 working days (I will confirm exactly after the technical specifications and access to the target database).
2. I have experience with parsing: I write parsers in Python (requests/httpx, BeautifulSoup/lxml, and if needed, Playwright for JS pages) with normalization, deduplication, and exporting to CSV/JSON/DB; I work with large volumes and automation of imports.
3. Possible difficulties that I will consider right away: dynamic content loading (JS rendering), limits/blocking on frequent requests (I do throttling + retries), correct mapping of fields to your DB schema, image processing, and incremental updates (to avoid duplication on repeated runs).

… Two clarifications:
1) Where do we import — your DB (which DBMS) / CMS / Google Sheet / API?
2) Is the parsing one-time or do you need regular updates on a schedule?

I work through Safe.

Show original

Translate

Hello!

I have reviewed your task - I have relevant experience in similar projects, so I understand how to implement everything efficiently and without unnecessary delays.

I can start working immediately after we agree on the details. Upon completion, I will also assist with setup, deployment, and provide all necessary documentation.
(I indicated the time for developing the parser, and the data collection with this parser will take somewhat longer)

I look forward to collaborating!

Show original

Translate

Good day. I can implement this parser. I am professionally skilled in parsing of any complexity, including bypassing various bot protections. I have written very complex and large parsers. For example, a parser for copart.com where it was necessary to parse 500k cars in a few hours. Feel free to contact me.

Show original

Translate

Hello! Have you already decided on the priority sources for parsing, besides the main catalog?

I will clarify the deadlines and budget in personal correspondence.

Here’s how I will execute this project:
1. I will analyze the structure of the catalog and identify optimal entry points for data collection.
2. I will set up an asynchronous parser with pagination handling and protection against blocking.
3. I will implement data export in a convenient format with duplicate filtering.

… Thank you for considering my proposal. I look forward to the opportunity to collaborate with you!

Show original

Translate

Good afternoon! We have extensive experience in parsing large catalogs with bypassing protection and automating imports via API. We implement this using Python with the Playwright and Scrapy libraries. The main challenges we see are in dynamic content loading and request limits, which we successfully mitigate through proxy rotation. We are ready to discuss the implementation details after reviewing the technical specifications.

Price for the entire project.

Show original

Translate

Parser with stable data collection — a work task. I constantly work with data processing and backend logic.

Show original

Translate

Good day!

I am ready to take on the development of a catalog parser and the automation of data import. I have experience working with large catalogs, including the use of proxies and APIs. The estimated cost and timeline will be formed after reviewing the technical specifications.

The main challenges may arise from changes in the structure of the source website and IP blocking.

Please write to me for clarification of details.

Show original

Translate