Coles AU Product Search Scraper avatar

Coles AU Product Search Scraper

Pricing

from $0.04 / 1,000 results

Go to Apify Store
Coles AU Product Search Scraper

Coles AU Product Search Scraper

Scrape Coles Australia product search results, prices, specials, categories, store context, barcode lookups, and normalized item data for grocery monitoring workflows.

Pricing

from $0.04 / 1,000 results

Rating

0.0

(0)

Developer

Dmitriy Gyrbu

Dmitriy Gyrbu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

an hour ago

Last modified

Share

Coles AU Product Search & Catalog (Unofficial)

Search Coles Australia products and fetch categories, specials, and normalized item data.

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

Supported operations

  • categories
  • search
  • search_filters
  • item
  • category
  • specials
  • specials_filters
  • specials_catalogue
  • item_by_barcode
  • item_by_gtin
  • store
  • stores_by_postcode
  • nearby_stores
  • stores_search
  • item_store_context
  • availability_by_store

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
  • item_by_gtin Required: gtin Optional: storeId, postcode, state, contextMode, includeRaw
  • store Required: storeId Optional: includeRaw
  • stores_by_postcode Required: postcode Optional: state, radius, limit, includeRaw
  • nearby_stores Required: lat, lon Optional: radius, limit, includeRaw
  • 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

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

  1. categories
  2. search
  3. item
  4. specials

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",
"itemId": "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

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 now have validated starter examples: 8150288 and 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.
  • Store-aware fields are supported where Coles returns them, but standalone store locator endpoints should be treated as best-effort.
  • The actor uses a private custom proxy pool configured as secret environment variables.