Coles AU Product, Specials & Price Scraper

Extract Coles Australia products, weekly and half-price specials, regular and discounted prices, unit pricing, nutrition, ingredients, category shelves, and postcode-aware availability context. Use the structured data for grocery price intelligence, specials tracking, assortment monitoring, product enrichment, and ecommerce research.

This is an unofficial actor and is not affiliated with Coles.

Supported operations

Stable product and offers workflows

• categories
• search
• search_filters
• item
• category
• specials
• specials_filters
• specials_catalogue
• item_store_context
• availability_by_store

Experimental / best-effort workflows

These remain in the input schema for backward compatibility, but should not be the first workflow used by a new buyer:

• item_by_barcode
• item_by_gtin
• store
• stores_by_postcode
• nearby_stores
• stores_search

Reverse barcode/GTIN lookup is currently unreliable even when the same barcode is present in product output. Standalone store discovery can return zero rows or an upstream locator error. For location-aware workflows, use product search/item context with postcode, state, and contextMode.

Operation guide

The Apify Console form shows the union of all supported fields, so the visible inputs do not change when you switch operation. Use the guide below to know which fields are required.

• categories Required: none Optional: refresh, includeRaw
• search Required: query Optional: page, limit, details, storeId, postcode, state, contextMode, includeRaw
• search_filters Required: none Optional: query, storeId, postcode, state, contextMode, includeRaw
• category Required: categorySlug, categoryId, or categoryUrl Optional: page, limit, details, storeId, postcode, state, contextMode, includeRaw
• item Required: itemId, productId, itemSlug, slug, or url Optional: storeId, postcode, state, contextMode, includeRaw
• specials Required: none Optional: special, page, limit, details, storeId, postcode, state, contextMode, includeRaw
• specials_filters Required: none Optional: storeId, postcode, state, contextMode, includeRaw
• specials_catalogue Required: slug, categorySlug, or url Optional: page, limit, details, storeId, postcode, state, contextMode, includeRaw
• item_by_barcode Required: barcode Optional: storeId, postcode, state, contextMode, includeRaw Status: experimental; prefer item with a full product URL.
• item_by_gtin Required: gtin Optional: storeId, postcode, state, contextMode, includeRaw Status: experimental; prefer item with a full product URL.
• store Required: storeId Optional: includeRaw
• stores_by_postcode Required: postcode Optional: state, radius, limit, includeRaw
• nearby_stores Required: lat, lon Optional: radius, limit, includeRaw Status: best-effort standalone store locator.
• stores_search Required: query Optional: state, radius, limit, includeRaw
• item_store_context Required: itemId, productId, itemSlug, slug, or url Optional: storeId, postcode, state, contextMode, includeRaw
• availability_by_store Required: itemId, productId, itemSlug, slug, or url Optional: storeId, postcode, state, contextMode, includeRaw

Recommended first runs

If you are validating the actor from scratch, use these in order:

1. search
2. specials
3. item using a full product URL
4. category

Then use ids/slugs from those results in the more targeted operations.

Example inputs

{
  "operation": "categories",
  "includeRaw": false
}

{
  "operation": "search",
  "query": "milk",
  "page": 1,
  "limit": 20,
  "includeRaw": false
}

{
  "operation": "item",
  "url": "https://www.coles.com.au/product/coles-full-cream-milk-3l-8150288",
  "includeRaw": false
}

{
  "operation": "category",
  "categoryId": "1300",
  "page": 1,
  "limit": 20,
  "includeRaw": false
}

{
  "operation": "specials",
  "special": "halfprice",
  "page": 1,
  "limit": 20,
  "includeRaw": false
}

Output

• Dataset: normalized products, category rows, filters, or item records
• Key-value store OUTPUT: run summary with source, operation, success, total, errors, proxy, and monetization

Product output can include regular/base price, lower promotional price, comparable unit pricing, stock signals, barcode, images, nutrition, ingredients, allergens, variants, category breadcrumbs, and canonical product URL. For specials, price is the regular/base price and discount_price is the lower current promotional price when available.

Buyer-ready Saved Tasks

• Coles Grocery Search & Unit Price Monitor — compact keyword price and assortment tracking.
• Coles Half-Price Deals & Product Enrichment — half-price products with detail enrichment.
• Coles Weekly Specials & Offers Feed — bounded all-specials feed.
• Coles Nutrition, Barcode & Ingredient Enrichment — one rich item via a reliable full URL.
• Coles Category Shelf & Assortment Monitor — category-level product and price snapshots.
• Coles Sydney Delivery Price Context Monitor — postcode-aware delivery context for product search.

Saved Tasks use bounded inputs and have been cloud-tested. Clone a task and change only the keyword, category, postcode, or product URL relevant to your workflow.

Notes

• Coles is the richest actor in this bundle, so the Apify Console will show a large union of optional fields.
• search, categories, and item are the best smoke tests.
• item and category have validated starter examples: the full milk product URL above and category 1300.
• If Coles cannot resolve the current site build id, the actor now returns a structured blocked error instead of the raw build_id_unavailable note.
• Postcode-aware product context is supported where Coles returns it. Standalone store locator endpoints are best-effort and are not presented as a primary capability.
• The actor uses a private custom proxy pool configured as secret environment variables.