This tutorial shows how to scrape Elektra product data into CSV with the Elektra Details Scraper for UScraper. You will import the workflow, replace the sample listing URLs, confirm the export path, validate the product rows, and handle common Elektra or VTEX listing issues.
Before you start
Prerequisites and scope
You need UScraper installed as a local desktop app, one or more Elektra listing URLs you are allowed to process, and a local folder for the CSV export. Start with one category or offer page from the official Elektra storefront or Elektra offers catalog, then add more URLs after the first file checks out.
This guide covers visible product listing cards, not account pages, cart flows, checkout, private customer data, or CAPTCHA bypassing. Review Elektra's terms and conditions, robots.txt, and your own permitted-use policy before collecting data. If the site asks for manual verification, pause automation, complete only allowed checks, and resume at a slower pace.
Technical access is not permission. Keep batches modest, preserve source URLs and run dates, and use an official or contracted data route when your output will power a production system.
Workflow anatomy
What the Elektra details scraper does
The companion JSON is the authoritative workflow definition: Navigate -> Wait for Page Load -> Sleep -> dismiss prompts -> Wait for Element -> Scroll -> load-more loop -> Structured Export -> Loop Continue. Navigate contains the input URL list. The wait and sleep blocks give the page time to hydrate. The JavaScript prompt cleanup handles common postal-code overlays. The scroll and condition blocks keep loading product cards until the show-more button is gone or disabled.
The workflow targets rendered Elektra product cards, so it is useful when an analyst needs the same visible fields they would review in the browser. It is not the same job as a sanctioned VTEX integration. VTEX documents Search, Intelligent Search, and Catalog APIs for authorized commerce integrations, while this tutorial is a supervised no-code CSV workflow from pages you can inspect.
| Workflow block | Purpose | What to check |
|---|---|---|
| Navigate | Opens each Elektra category, offer, or filtered listing URL | Replace the sample furniture, ventilation, and footwear URLs with your approved inputs. |
| Prompt cleanup | Removes common postal-code and location overlays | Confirm the page remains scrollable and product cards are visible. |
| Load-more loop | Scrolls and clicks the VTEX-style show-more control | Watch the product count increase before the export starts. |
| Structured Export | Writes one row per loaded product card | Confirm headers, append mode, filename, and save folder. |
| Loop Continue | Advances the next URL in the input list | Use unique URLs to avoid duplicate rows. |
Runbook
How to scrape Elektra product data to CSV
Replace listing URLs
Paste Elektra category, offers, or filtered listing URLs into Navigate. Keep filters in the URL when they define the product segment you are researching.
Run one page visibly
Let the browser load, handle any allowed prompt manually, and confirm product cards appear before the load-more loop begins.
Confirm the CSV destination
In Structured Export, check elektra-detalles-scraper.csv, headers, append mode, and the local save folder.
Validate, then scale
Open the CSV after one URL, compare several rows against the browser, then add the rest of your URL list.
Output
Elektra CSV fields and sample rows
The bundled export has no finished CSV sample, so treat the JSON definition and a dry run as the contract. Each row represents one loaded product card. The output is meant for spreadsheet review, price tracking, assortment checks, and handoff to a follow-up enrichment workflow.
elektra-detalles-scraper.csvColumn
titulo
Product title from the Elektra listing card.
Column
precio
Current visible price after filtering weekly-payment text.
Column
precio_original
Previous or crossed price when a second product price is visible.
Column
prestamo
Weekly loan, credit, or payment wording shown on the card.
Column
imagen_url
Primary product image URL from the card image element.
Column
producto_url
Detail page URL from the product-card link.
Sample rows
2 of many
| titulo | precio | precio_original | prestamo | imagen_url | producto_url |
|---|---|---|---|---|---|
| Comoda de 5 cajones color chocolate | $2,499 | $3,299 | Desde $125 a 24 semanas | ||
| Ventilador de pedestal 18 pulgadas | $899 | $45 semanales con credito |
| CSV field | Validation check |
|---|---|
titulo | Compare the title against the product card, not the browser tab title. |
precio | Confirm the value is the product price, not a weekly payment fragment. |
precio_original | Treat blanks as valid when no original price is shown. |
prestamo | Keep as text because credit wording can include weeks or terms. |
imagen_url | Open a few links if images matter for your downstream system. |
producto_url | Use this as the audit key for dedupe and follow-up checks. |
Quality control
Validate the Elektra export before using it
Open the CSV beside the browser and check the first, middle, and last rows from the run. Count visible cards after the load-more loop and compare that number to exported rows for the same URL. If the page changed while the run was in progress, record the time and rerun the URL later rather than mixing inconsistent snapshots.
| Symptom | Likely cause | Fix |
|---|---|---|
| Zero rows | Product cards never rendered or an overlay blocked the selector | Handle prompts, reload one URL, and wait for cards before export. |
| Duplicate rows | Same URL appears twice or a loop resumed after export | Deduplicate by producto_url and clean the input list. |
| Prices look like loans | Weekly payment text was captured before the product price | Inspect one card and adjust the price extraction logic. |
| Missing images | Lazy images had not resolved when export ran | Add a short scroll-and-sleep before Structured Export. |
| Export stops early | Show-more control changed, disappeared, or was disabled | Run visibly and refresh the condition selector if the button still exists. |
Use UScraper when a researcher needs a controlled CSV from a short list of approved Elektra category URLs and wants to inspect the page while it runs.
Alternatives
Octoparse, Bright Data, VTEX API, or UScraper?
Octoparse publishes an Elektra template, and Bright Data offers Elektra scraping and price-tracking products. Those can make sense when you want a hosted vendor workflow, managed infrastructure, or a broader data service. UScraper fits a narrower job: an analyst-controlled local CSV export with visible blocks, editable waits, and a file written to a folder you choose.
| Approach | Best fit | Trade-off |
|---|---|---|
| UScraper template | Local no-code workflow, browser QA, CSV custody | You maintain selectors when Elektra changes markup. |
| Octoparse Elektra template | No-code users already working in Octoparse | Vendor environment and plan limits apply. |
| Bright Data Elektra products | Managed web data, price tracking, larger programs | Better for procured data operations than quick local CSV checks. |
| VTEX or official integration | Authorized catalog, search, or commerce pipeline | Requires permission, credentials, engineering work, and a different data contract. |
FAQ
Elektra product scraping FAQ
Elektra product pages may be visible in a browser, but automated collection can still be restricted by Elektra terms, robots directives, copyright, marketplace rules, privacy law, and local regulations. Review current policies, avoid bypassing access controls or CAPTCHA checks, and get legal review before commercial reuse.
Next step
Download the Elektra details scraper template
When you are ready to run the tutorial, download the JSON from Elektra Details Scraper and keep this article open for QA. For adjacent no-code scraping workflows, browse the UScraper template library or the UScraper blog for more CSV export tutorials.