Marks & Spencer Product Scraper

This unofficial actor extracts product listings, item details, filters, and navigation categories from Marks & Spencer UK. It is useful for price monitoring, retail research, product discovery, and catalog enrichment workflows.

This actor is not affiliated with, endorsed by, or sponsored by Marks & Spencer.

Quick Start

{
  "operation": "search",
  "query": "dress",
  "maxItems": 5
}

Supported Operations

Operation	Purpose	Required Input	Example
search	Search product listings by keyword.	query	{"operation":"search","query":"dress","maxItems":5}
category	Browse one category listing.	slug or url	{"operation":"category","slug":"l/home-and-furniture/lighting","maxItems":5}
item	Extract one product detail page.	slug or url	{"operation":"item","url":"https://www.marksandspencer.com/velvet-lamp-shade/p/hbp60555148","includeReviews":true}
filters	Return filter/facet groups for a search or category context.	query, slug, or url	{"operation":"filters","query":"dress"}
categories	Return top-level M&S navigation categories.	None	{"operation":"categories"}

The actor also accepts old nested compatibility inputs such as search_params, category_params, and item_params. New clients should use the top-level fields shown above.

Input Fields

operation selects the workflow. query is used by search and search-based filters. slug and url identify category and item pages. category_id is accepted when a category can be resolved from navigation, but a slug or url is more reliable. maxItems controls listing result size and defaults to 5 in the Apify UI. page is 1-based. sort accepts values discovered from the filters output. includeReviews and reviewLimit apply to item pages when review data is present in the page payload.

proxy_configuration accepts direct, apify, custom, or auto. Direct requests are fastest; Apify proxy is useful when direct access is blocked.

Output

For search and category, the actor pushes one metadata row followed by individual product rows. Metadata rows include _type, operation, query or category fields, totals, filters, category filters, sort options, and the M&S Next.js build_id observed during the run.

Product rows commonly include _type, operation, id, product_external_id, slug, name, brand, source_url, price, discount_price, current_price, currency, image, images, category, breadcrumbs, in_stock, rating, review_count, variants, and promotions.

filters returns a structured row with filter groups, category filters, and sort options. categories returns a structured row containing navigation results, an ID-to-URL index, and candidate category URLs.

Limitations

M&S pages are rendered from server-side Next.js data. If a page no longer exposes the expected payload, the operation can fail or return fewer fields. Review data is only returned when it is present in the page payload. Category IDs are not always resolvable without a fresh navigation or filter discovery step, so URL and slug inputs are recommended for category operations.

Troubleshooting

Use the default search first to confirm access. If category filtering fails with category_id, retry with the category slug or full url. If item extraction fails, use a product URL from a fresh search or category result. If direct access is blocked, rerun with proxy_configuration set to apify.

Privacy And Publication

This actor is intended to remain private until the owner publishes it manually. No publication or visibility changes are required for normal testing.