Custom scraper

Westwing Scraper

We do not have a dedicated Westwing data API. What we do have is an AI scraper that reads a westwing.de 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.

  • westwing.de
Three stages of a Westwing run: paste a westwing.de URL billed from the render price of EUR 0.75 per 1,000 pages; declare columns such as product_title and brand; and the 12 columns it returns.

How to scrape Westwing

Westwing 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. Westwing runs a club model alongside its open shop, so a lot of its pricing is only visible to members. The way to get the data is to read the page the way a customer sees it. Furniture prices move on configuration and lead time rather than on daily repricing: the same sofa is three prices depending on fabric, and the delivery estimate is part of the offer.

How westwing.de is laid out

What a run needs to know about Westwing before you pick the URLs.

  • Club and Shop on one domain

    Since 2023 the time-limited Club sales and the permanent shop share one domain. The same item can appear in a campaign and in the shop at different prices.

  • Campaigns with countdowns

    Club campaigns show a countdown such as Ends in 1D 1H 24M and discounts up to 60%. Store the end time with the price.

  • Westwing Collection

    Westwing Collection is the own brand, designed in Munich and shown under the product name. Only branded items can be matched to other shops directly.

  • Branded items

    About 70% of Club items come from outside brands. These are the ones worth comparing across shops.

  • Eleven countries

    Westwing sells in eleven European countries on domains such as westwing.de, .ch and .it. List each market on its own.

What the AI scraper does with a westwing.de link

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

  1. Paste the link

    Give it a westwing.de 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 a Westwing pagerequired

    Open the product or category page in your browser and copy the address. Any Westwing country domain works the same way.

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

One row per product on the page, 12 columns each

  • product_title
  • brand
  • sku
  • variant
  • price
  • was_price
  • currency
  • availability
  • delivery_estimate
  • dimensions
  • product_url
  • checked_at

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

The columns a Westwing run comes back with

We are not going to print a table of invented home and furniture prices and call it real output. Westwing answers an ordinary request with Cloudflare rather than a product page, so we have no run of our own to quote from. So what is published here is the column list you declare before the run, which is the same list every run comes back with.

product_titleProduct title as the site writes it
brandBrand or own-label name
skuSite's own article number
variantFabric, finish or size the page is showing
pricePrice for that configuration today
was_priceStrike-through price, only where the page shows one
currencyCurrency the page quoted
availabilityStock state as the page states it
delivery_estimateLead time or delivery window shown
dimensionsDimensions as the page prints them
product_urlLink back to the page the row came from
checked_atWhen this run collected the page (UTC)

Every column here is one you name yourself in the schema. If a field is not on the page on the day of the run, it comes back empty rather than guessed.

What a Westwing page costs

Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count. The price shown is the starting price: €0.75 per 1,000 pages with a browser render. If a run also needs a residential proxy it costs €3.75 per 1,000 pages.

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

Measured on 3 October 2026, not assumed. A plain request for a westwing.de page returns a document rather than a refusal, but Cloudflare is in front of it, and the parts of the page that carry price are filled in by JavaScript after load, so a browser is what makes the run reliable.

Worked example

500 Westwing pages checked once a day for a month is 15,000 pages.

about EUR 11.25 for the month at the render price, about EUR 56.25 if the pages also need a residential proxy

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 a Westwing 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.

Configuration is the price

A single product page can hold a wide price range, and which configuration is shown by default is a merchandising decision, not a fact about the product.

  • Price for the configuration the page is showing
  • Which fabric, finish or size that is
  • Price range across configurations, where the page prints one
  • Strike-through or was-price where shown
  • Promotion or sale event wording

Lead time, which is half the offer

In furniture a lower price with a fourteen-week lead time is not competing with a higher price in stock.

  • Delivery window or lead time shown
  • Stock state as the page states it
  • Whether the item is made to order, where the page says
  • Delivery or assembly charge, where quoted
  • Showroom availability, where exposed

Specification

Furniture comparisons live or die on dimensions and materials, and both are usually rendered as a table.

  • Dimensions as printed
  • Material and finish description
  • Site's own article number
  • Range or collection name
  • Rating and review count, where shown
  • 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 Westwing publishes them.

What people use Westwing data for

01

Price and promotion tracking through sale events

Home retail runs on sale events rather than daily repricing. Collecting daily through an event reconstructs exactly when each line moved and by how much.

02

Lead-time competitiveness

Delivery estimates next to prices turn a price comparison into an offer comparison, which is the one customers actually make.

03

Range and specification research

What a category carries, at what dimensions and price points. A few weeks of scraped data answers that before a buy.

04

Configuration price mapping

The real price range of a product across its fabrics and finishes, rather than the entry price the listing advertises.

05

Brand and partner price checks

If you supply into home retailers, this is how you see what your products are actually listed at, with the date attached.

What makes Westwing harder than an ordinary storefront

Here is what the scraper is actually up against on westwing.de, measured rather than assumed.

Access

  • Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
  • Named protection on the response: Cloudflare
  • robots.txt publishes sitemaps, which is the cheapest way to build the URL list a run works through

One page, a price range

  • Fabric, finish and size options can each carry their own price, so the page has a range rather than a price
  • Which configuration is shown by default changes, which makes a single-number scrape unstable
  • Lead time is part of the offer and lives in a different part of the page from the price
  • Configuration options are often loaded only after interaction, so a rendered page is required rather than optional

What the page publishes

  • Structured data is published but not at product level (ContactPoint, ImageObject, MerchantReturnPolicy), so price comes from the rendered page rather than a feed
  • Club prices sit behind a login while the open shop prices the same items higher.
  • 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 westwing.de

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.

  • Westwing has one specific trap

    Time-limited Club campaigns and the permanent shop sit on one domain, so the same item can carry a campaign price in one place and a regular price in the other.

FAQ

Westwing scraping — questions

What people ask before pointing the scraper at westwing.de.

Westwing 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 Westwing data into your stack?

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