Custom scraper

El Corte Inglés Scraper

We do not have a dedicated El Corte Inglés data API. What we do have is an AI scraper that reads an elcorteingles.es page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.

  • elcorteingles.es
  • elcorteingles.pt
Three stages of an El Corte Inglés run: paste an elcorteingles.es URL billed on the render plus residential tier at EUR 3.75 per 1,000 pages; declare columns such as product_title and brand; and the 12 columns it returns.

How to scrape El Corte Inglés

El Corte Inglés publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. El Corte Inglés is the Spanish full-line reference and prices above the specialists in nearly every category it sells. The way to get the data is to read the page the way a customer sees it. A broad-range retailer prices thousands of unrelated categories on different logics, so the useful scrape is narrow and deep rather than catalogue-wide.

How elcorteingles.es is laid out

What a run needs to know about El Corte Inglés before you pick the URLs.

  • A department store online

    El Corte Inglés covers fashion, electronics, home, beauty and a supermarket under one domain, each with its own structure. Scope runs to one department at a time.

  • Supermarket is its own section

    Groceries live under /supermarket/ with their own search, offers and product pages. Treat them as a separate site.

  • Discount filters

    Category pages can be filtered by discount band (for example 21–31%). Useful for finding what is on promotion.

  • Energy labels and colours

    Electronics listings show the energy label and the colour options. Each colour can be a separate offer.

  • Card financing

    Many items promote financing with the El Corte Inglés card. That is credit, not a lower price.

What the AI scraper does with an elcorteingles.es link

The same three steps as any other page you point it at. Nothing about El Corte Inglés is pre-built, which is exactly why it works on pages nobody wrote a connector for.

  1. Paste the link

    Give it an elcorteingles.es product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.

  2. Declare the columns

    Name each field, give it a type and write a line telling the AI what to look for. “product_title” and “brand” are the two most people start with. The schema is yours and you can change it between runs.

  3. Schedule it and collect

    Run it daily, weekly or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.

Set it up once. The data keeps coming.

Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.

  1. Set it up once

    Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.

  2. Runs on your schedule

    Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.

  3. Saved in your database

    Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.

  4. Use it your way

    Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.

Ask your AI assistant about your own data

Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.

  • Which of my ASINs lost the Buy Box this week?
  • Which competitor cut prices the most since Monday?
  • Show the keywords where I dropped out of the top 10.

What you send and what you get

You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.

You give
  • Link to an El Corte Inglés pagerequired

    Open the product or category page in your browser and copy the address. Any El Corte Inglés country domain works the same way.

    https://www.elcorteingles.es/
  • Your column listrequired
    product_title, brand, sku, price
  • How often it runsoptional
    Daily at 06:00 UTC
You get

One row per product on the page, 7 columns each

  • product_title
  • price
  • currency
  • availability
  • brand
  • sku
  • source_url

REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.

What a run on El Corte Inglés actually returned

This is real output, not a mock-up. 2 rows, collected on 3 October 2026 from live elcorteingles.es product pages through our own engine, the same way one of your runs would. Prices move, so treat the numbers as a sample of shape rather than a current price list.

All 7 columns

  • product_title
  • price
  • currency
  • availability
  • brand
  • sku
  • source_url

2 sample rows, all 7 columns seen across sample calls.

2 sample rows, all 7 columns seen across sample calls.
product_titleproduct_titleProduct title as the retailer writes itpricepricePrice the page is charging todaycurrencycurrencyCurrency the page quotedavailabilityavailabilityStock state the page publishedbrandbrandBrand as the retailer labels itskuskuThe retailer's own product codesource_urlsource_urlThe exact page this row was read from
Set de escritorio 30 Boss Original x Pantone STABILO49.95EURInStockSTABILO4006381632225https://www.elcorteingles.es/papeleria/A202365597-set-de-escritorio-30-boss-original-x-pantone-stabilo/?stype=text_box_multi
El día de la Trilla (Empíreo, 4) (Tapa dura)21.75EURInStockPLANETA9788408326847https://www.elcorteingles.es/libros/A201002378-el-dia-de-la-trilla-empireo-tapa-dura/?stype=text_box

Column names are ones we chose when declaring the schema for this run. Yours can be named whatever your downstream job already expects. We pointed the run at 14 El Corte Inglés product pages and 2 came back with a readable price. The rest returned something other than a product page, which is ordinary on this storefront and the reason the tier named above is what it is. We publish what we measured, not what we expect.

What an El Corte Inglés page costs

Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count.

€3.75per 1,000 pagespay-as-you-go, no plan

Measured on 3 October 2026, not assumed. A plain request for an elcorteingles.es page is refused with HTTP 403 by Akamai, and so is the bare homepage, which rules out a bad path as the explanation. Clearing that needs both a real browser and a residential exit.

Worked example

500 El Corte Inglés pages checked once a day for a month is 15,000 pages.

about EUR 56.25 for the month

You are charged for what a run actually used, not what it was expected to need, and your balance never expires.

See the full price list →

Typical fields the AI scraper extracts from an El Corte Inglés page

Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.

Price and promotion

On a broad-range retailer the promotion mechanic varies by category, so capture the wording rather than trying to parse it into a number.

  • Current price
  • Strike-through or was-price where shown
  • Promotion or voucher wording as printed
  • Multibuy conditions, where stated
  • Currency and market the price belongs to

Stock and fulfilment

A cheaper competitor who cannot deliver this week is not a cheaper competitor.

  • Stock state as the page states it
  • Delivery window shown
  • Click-and-collect availability, where exposed
  • Delivery charge, where quoted
  • Seller or fulfiller, where the page names one

Product identity

Broad catalogues mix branded and own-label lines, so the retailer's own code is the one field always present.

  • Site's own article number
  • EAN or GTIN, where published
  • Brand, or own-label name
  • Category breadcrumb
  • Rating and review count
  • Product image URLs

The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →

What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when El Corte Inglés publishes them.

What people use El Corte Inglés data for

01

Daily competitor price tracking

A list of product URLs, a daily schedule, and a table you can diff against yesterday rather than a tab somebody checks by hand.

02

Own-label versus brand price gap

The gap between a retailer's own label and the branded equivalent on the same shelf, measured rather than estimated.

03

Promotion calendar reconstruction

Which lines go on promotion, when, and how deep. Public information that is only visible if you collected it.

04

Availability and delisting alerts

Whether your lines are listed, in stock and findable. Suppliers usually discover delisting late.

05

Price-index reporting

A fixed basket of lines read daily is a price index you own, rather than one you buy with a lag.

What makes El Corte Inglés harder than an ordinary storefront

Here is what the scraper is actually up against on elcorteingles.es, measured rather than assumed.

Access

  • Plain HTTP requests are refused at the edge — a naive fetch returns HTTP 403, not a page
  • Named protection on the response: Akamai
  • No usable sitemap directive in robots.txt, so the URL list comes from your own category pages

Breadth is the difficulty

  • Different categories use different promotion mechanics, so one parsing rule does not fit the catalogue
  • Own-label lines carry no manufacturer identifier, so cross-retailer matching needs titles or your own mapping
  • Catalogues run to hundreds of thousands of lines, so scope the page count deliberately rather than sweeping
  • Category pages are paginated and lazily loaded, so a sweep is a list of URLs rather than one request

What the page publishes

  • No product-level structured data is published, so every field is read off the rendered page
  • Each category runs a different price structure under one domain, so a run has to scope to a category rather than the site.
  • Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number

What to watch on elcorteingles.es

The one thing specific to this site. The general limits — public pages only, no field the page does not show, your URLs rather than a full crawl — are in the custom scrapers FAQ.

  • El Corte Inglés has one specific trap

    Each category runs a different price structure under one domain, so a run has to scope to a category rather than the site.

FAQ

El Corte Inglés scraping — questions

What people ask before pointing the scraper at elcorteingles.es.

El Corte Inglés publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.

Questions that apply to every site — scheduling, exports, what it will not do — are answered in the custom scrapers FAQ.

Ready to pull El Corte Inglés data into your stack?

Start free — or talk to our team about your exact fields, refresh cadence and volume.