Superdry Scraper — Products, Prices & Stock Data
Pricing
from $1.20 / 1,000 result scrapeds
Superdry Scraper — Products, Prices & Stock Data
Scrape products, prices, stock status, ratings, and images from Superdry.com — the UK-founded fashion brand's global storefront. Covers menswear, womenswear, outlet, and sale.
Pricing
from $1.20 / 1,000 result scrapeds
Rating
0.0
(0)
Developer
Studio Amba
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Superdry Scraper
Extract product data from Superdry.com, the UK-founded fashion brand's global storefront. Covers menswear, womenswear, outlet, and sale.
Why use this actor?
Superdry runs its own online store across menswear, womenswear, outlet, and sale sections, with roughly 9,450 live product pages. This actor collects structured product data — price, stock status, colour, rating, and images — without manual browsing.
Use cases include:
- Price monitoring: Track price and markdown changes across a section or subcategory over time
- Competitor benchmarking: Compare Superdry's pricing and range against other UK fashion retailers
- Stock tracking: Watch availability for specific styles or subcategories
- Catalogue research: Pull the full outlet or sale range to spot the deepest discounts
- Assortment analysis: See how the range breaks down by subcategory (t-shirts, jackets, shoes, etc.)
How to scrape Superdry.com data
- Go to the actor's page on the Apify Store
- Pick a section (menswear, womenswear, outlet menswear, outlet womenswear, sale, or all sections)
- Optionally narrow to one subcategory, e.g.
t-shirts,jackets,shoes - Set the maximum number of results you want
- Click "Start" to run the scraper
- Download results as JSON, CSV, or Excel when complete
Superdry.com sits behind Cloudflare but does not challenge plain requests — no browser automation or residential proxy is needed. There is no free-text search: the site's own search pagination is disallowed by robots.txt, so this actor enumerates products from Superdry's own product sitemap instead and reads each product page's structured data directly.
Input
| Field | Type | Required | Description |
|---|---|---|---|
section | String | No | mens (default), womens, outlet/mens, outlet/womens, sale, or all |
subcategory | String | No | Filter to one subcategory, e.g. t-shirts, hoodies-and-sweatshirts, jackets, shoes. Leave blank for every subcategory in the section. |
maxResults | Integer | No | Maximum products to return (default: 100, hard cap: 9,500 — the full live catalogue) |
proxyConfiguration | Object | No | Proxy settings. The default Apify proxy works — Superdry does not challenge it. |
There is no searchQuery field — Superdry's search results pagination is robots.txt-disallowed, so this actor works from the section/subcategory taxonomy instead.
Output
Each product produces a JSON object with the following fields:
| Field | Type | Description |
|---|---|---|
name | String | Product name |
brand | String | Brand name (e.g. SUPERDRY, SDX) |
price | Number | Current selling price |
currency | String | Currency code (e.g. GBP) |
originalPrice | Number | Pre-discount list price, when marked down. Null otherwise. |
color | String | Selected colourway |
inStock | Boolean | Whether the product is currently available |
rating | Number | Average customer rating out of 5, when reviews exist |
sku | String | Superdry's internal product/style number |
section | String | Top-level catalogue section, e.g. mens, outlet/womens |
subcategory | String | Subcategory, e.g. t-shirts, jackets |
imageUrl | String | First product image URL |
imageUrls | Array | All product image URLs |
productDescription | String | Plain-text product description |
url | String | Full product page URL |
scrapedAt | String | ISO 8601 timestamp when data was collected |
Example output
{"name": "Core Essential Flip Flops","brand": "SUPERDRY","price": 17.99,"currency": "GBP","originalPrice": null,"color": "Army Khaki","inStock": true,"rating": 3.2,"sku": "268872","section": "mens","subcategory": "shoes","imageUrl": "https://images.laguna-live.sd.co.uk/zoom/upload9223368955666919157.jpg?format=jpg&width=658","imageUrls": ["https://images.laguna-live.sd.co.uk/zoom/upload9223368955666919157.jpg?format=jpg&width=658"],"productDescription": "Classic flip-flop design. Rubber straps with signature text...","url": "https://www.superdry.com/mens/shoes/core-essential-flip-flops-268872.html","scrapedAt": "2026-09-09T19:52:31.266Z"}
How it works
Superdry.com runs on Salesforce Commerce Cloud (dwsid/dwanonymous_* cookies). Its robots.txt disallows the AJAX pagination parameters (start, srule, prefn*, prefv*) used by the category/search grid, so this actor never touches those endpoints. Instead it enumerates product URLs from Superdry's own dedicated product sitemaps (sitemap-customSitemap_sd-uk_en_GB_product*.xml), filters them by section/subcategory, and reads each product page's schema.org Product JSON-LD block — the same structured data Google indexes — for name, description, brand, images, rating, price, currency, and availability. Both the sitemap fetch and the product-page fetch are robots.txt-allowed.
Cost estimate
This actor uses plain HTTP requests through the standard Apify proxy — no residential proxy or browser rendering is needed, so it is one of the cheaper actors in the fleet to run. Usage cost only settles on the platform after a run reports SUCCEEDED — reading the dataset while a run is still in progress undercounts the eventual cost.
Limitations
- No free-text search — filter by section and subcategory only
- Colour reflects whichever variant the product page defaults to, not every available colourway
originalPriceis only populated when the page shows a strike-through list price- Prices and stock reflect the UK storefront (GBP); other Superdry country sites are not covered by this actor
Frequently asked questions
Does this need a login or API key? No. Superdry's product pages are public, and this actor doesn't touch any account or checkout endpoints.
How current is the data? Every run fetches product pages live — there is no caching layer. Price and stock reflect the moment the actor ran.
Can I scrape the whole catalogue in one run?
Yes, set section to all and maxResults to 9500 to cover every live product page. A full run will take longer and use proportionally more compute units than a single-subcategory run.
Why is there no keyword search?
Superdry's robots.txt disallows the query parameters its own search-results pagination depends on. Rather than scrape a disallowed path, this actor works from the site's own sitemap and category taxonomy instead, which is fully robots.txt-allowed.