Lidl UK Product, Price & Category Scraper

Extract public Lidl UK product search results, category listings, prices, availability, barcodes, images, and detailed product pages. Use the data for price monitoring, catalogue research, product discovery, and retail market analysis.

This Actor is independently maintained and is not affiliated with or endorsed by Lidl.

Supported operations

• search — search Lidl UK products by keyword.
• category — list products from a category ID, slug, or URL.
• item — extract one product using a product ID, barcode, slug, or URL.
• categories — discover live Lidl UK categories and category IDs.
• search_filters — inspect available search or category filters.
• probe — check source availability without writing product rows to the dataset.

Common controls

• page is 1-based; default 1.
• limit is bounded to 1–100; default 24.
• sort supports relevance, price_asc, price_desc, title_asc, and title_desc.
• includeRaw=true adds the source payload to OUTPUT for diagnostics; semantic Dataset rows remain normalized.

Product search

{
  "operation": "search",
  "query": "wine",
  "page": 1,
  "limit": 10
}

Search results may contain product ID, title, barcode, category breadcrumbs, price, currency, stock indicator, badges, images, and official product URL.

Category products

First run categories, then pass a returned category ID:

{
  "operation": "category",
  "category_id": "a10024029",
  "page": 1,
  "limit": 10
}

Item details

{
  "operation": "item",
  "url": "https://www.lidl.co.uk/p/cotes-de-provence-premium-wine/p10049229"
}

Product IDs returned by search/category can be resolved directly across independent runs. URL input remains the fastest explicit path. Only lidl.co.uk page URLs are accepted for fetch operations; external hosts are rejected.

The same item can be resolved from a search/category result without copying the full URL:

{
  "operation": "item",
  "product_id": "10051842"
}

barcode is emitted only when Lidl exposes a barcode/IAN/GTIN. Lidl Article numbers are kept as product IDs and are never relabeled as barcodes.

Category directory

{
  "operation": "categories"
}

Category records include names, official URLs, category IDs, product counts, breadcrumbs, and sample product IDs when published by Lidl.

Search filters

{
  "operation": "search_filters",
  "query": "wine"
}

With no query/category context, search_filters uses the bounded wine starter and returns structured filter metadata only.

Output

Product and category records are written to the default dataset and can be exported as JSON, CSV, Excel, XML, or through the dataset API. Every run also writes a structured OUTPUT record with operation status, counts, errors, proxy mode, and budget information.

The Actor includes a dataset table view for common fields such as product name, price, availability, barcode, category ID/breadcrumbs, filter metadata, and source URL.

Access and cost

Normal bounded runs use direct HTTP and do not require a browser or paid proxy. The Actor keeps fallback transports available if Lidl changes its access rules. The default workflow is intentionally small and cost-conscious.

Limitations

• Lidl does not publish an online price for every product or category record.
• Some products are marked as available in store only.
• Category contents, prices, badges, and availability can change by time and source publication.
• Always verify important purchasing information on the linked Lidl product page.

AI / MCP / API contract

• Empty input, or search without a query, runs a bounded buyer-useful wine starter.
• Dataset contains semantic rows only: products, categories, or structured filter groups.
• Search relevance is accent-insensitive and token-aware (for example rose matches Rosé) while broad umbrella breadcrumbs are excluded from semantic matching.
• A true no-match search returns an exact empty Dataset ([]).
• search_filters can run without context and returns filter metadata only; it never publishes sample products as filter results.
• OUTPUT contains status, counts, supported operations, errors, budget metadata, and an agent provenance envelope.
• Product IDs from search/category can be passed to item; the Actor uses a bounded exact Lidl product route before any catalogue fallback.