This tutorial shows how to scrape Coppel product details into CSV with the Coppel Product Details Scraper for UScraper. You will import the workflow, add product URLs, set the export path, run a dry test, and validate the result before scaling.
Before you start
Prerequisites and scope
You need UScraper installed as a local desktop app, a folder for CSV exports, and a short list of Coppel product detail URLs you are allowed to process. If you are building a URL list from category or search pages first, use the Coppel listing scraper or a manual shortlist, then send the detail URLs into this tutorial.
This guide covers supervised product research from pages you can inspect in a browser. It does not cover private account areas, checkout flows, CAPTCHA bypassing, login-only pricing, or aggressive crawling. Before running automation, review Coppel's current terms and conditions, robots.txt, and public help guidance.
Technical access is not the same as permission. Keep runs modest, collect only what you have a lawful basis to use, and prefer official or contractual data access when the output will feed production systems.
Workflow anatomy
What the Coppel product details scraper does
The template graph is intentionally simple: Navigate -> Wait for Page Load -> Wait for Element -> Sleep -> Inject JavaScript -> Wait for normalized row -> Structured Export -> Loop Continue. Navigate holds your product URL list. The wait blocks give the page or readable endpoint time to return content. The JavaScript block creates one hidden normalized product row. Structured Export appends that row to CSV.
The bundled workflow was built as a best-effort details scraper. During validation, direct automated navigation to Coppel product pages could fail in some sessions, so the template uses a readable endpoint pattern and derives safe fallback fields from the original URL. If readable page text is available, the export can include richer price, availability, discount, and feature data. If Coppel returns a blocked response, the workflow still attempts to derive SKU, model text, and expected image URLs from the product ID.
| CSV field | What it means | Validation check |
|---|---|---|
SKU | Product identifier derived from the URL or page text | Compare against the product URL and any internal product barcode database you maintain. |
Modelo | Cleaned product title or URL-slug fallback | Open the source URL and confirm the name still represents the product. |
Disponibilidad | Visible stock wording when available | Treat blanks as unknown, not in stock. |
Precio, Precio_original, Descuento | Current price, second price candidate, and savings text | Verify with the live page because prices can change quickly. |
Talle, Caracteristicas | Derived size, color, and feature notes | Expect fallback notes when Coppel blocks full text. |
Imagen1 to Imagen5 | Coppel CDN image URL candidates | Open a few image links before importing them into a catalog. |
Runbook
How to scrape Coppel product details to CSV
Import the template
Open Coppel Product Details Scraper, download the JSON, and import it into UScraper.
Replace the sample URLs
In the Navigate block, replace the refrigerator examples with Coppel product detail URLs from your approved list. Keep one URL per loop input.
Confirm waits
Keep the page-load wait, body check, and short sleep while testing. If Coppel responds slowly, increase waits before changing extraction logic.
Set the export folder
In Structured Export, confirm coppel-detalles-scraper.csv, headers, append mode, and a project-specific local save folder.
Run one URL first
Run a single product, inspect the CSV row, compare the source page, then reconnect the loop for the remaining URLs.
After the first export, sort by SKU and Modelo. One source URL should create one row. If rows repeat, check for duplicate input URLs or a paused loop that resumed after Structured Export already appended a row.
Quality control
Validate the Coppel product data extraction
Do not treat the first CSV as production-ready. Open the file beside the source page and review one row from the start, middle, and end of the run. Product detail pages are especially sensitive to layout changes because price, availability, installment text, image galleries, and product specifications often load from different page modules.
| Symptom | Likely cause | Fix |
|---|---|---|
SKU is blank | Product ID could not be found in the URL or text | Confirm the URL contains a product identifier such as a pm or mkp suffix. |
Precio is blank | Page text was blocked, hidden, or formatted differently | Rerun one URL, inspect visible price text, and update the parsing rule only after confirming access. |
| Availability is missing | The page did not expose stock wording | Keep the field blank rather than inventing a status. |
| Image URLs 404 | CDN pattern changed or the product uses fewer images | Open sampled image links and keep only valid URLs. |
| Feature notes look generic | The fallback parser ran because full text was unavailable | Mark the run as partial and retry later with slower pacing. |
Alternatives
UScraper vs Octoparse, Apify, and hosted Coppel scraper tools
Searches for best Coppel scraper tools usually surface three categories: no-code hosted templates, cloud actors, and managed data services. Octoparse has Coppel listing and details templates, Apify has a Coppel product search actor, and services such as Thunderbit, Bright Data, Spider, or RetailGators position Coppel scraping around managed extraction, APIs, or cloud throughput.
UScraper is a better fit when the job is a supervised local CSV export. You can see the browser context, edit the workflow visually, keep files on your machine, and use the template library for adjacent ecommerce extractors. Hosted tools can be better when you need managed scheduling, proxy infrastructure, APIs, or vendor support for higher-volume pipelines.
| Approach | Best fit | Trade-off |
|---|---|---|
| UScraper local desktop template | Analyst-run Coppel product data extraction to CSV | You validate access and maintain workflow behavior when the page changes. |
| Octoparse-style no-code template | Cloud-assisted visual scraping with packaged templates | Data custody, pricing, and runtime behavior depend on the platform. |
| Apify actor or scraper API | Programmatic runs and integration with cloud datasets | You manage actor inputs, usage cost, and vendor terms. |
| Managed data provider | Recurring feeds with service-level expectations | Less control over workflow internals and usually more procurement overhead. |
FAQ
Frequently asked questions
Only collect Coppel pages you are allowed to access. Review Coppel terms, robots guidance, privacy rules, copyright, marketplace restrictions, and local law before using exported product data. Do not bypass login walls, CAPTCHA, access controls, or bot protection.