Coles Product Search Scraper — Australia Grocery | PPE avatar

Coles Product Search Scraper — Australia Grocery | PPE

Pricing

from $34.92 / 1,000 product results

Go to Apify Store
Coles Product Search Scraper — Australia Grocery | PPE

Coles Product Search Scraper — Australia Grocery | PPE

Scrape grocery products from Coles.com.au — Australia's leading supermarket chain. Search by keyword and get name, brand, price, size, availability, aisle location and more per product. Pay per product delivered.

Pricing

from $34.92 / 1,000 product results

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

2

Monthly active users

14 days ago

Last modified

Categories

Share

Coles Product Search Scraper — Australia Grocery

Collect grocery products from Coles.com.au, Australia's leading supermarket chain. Paste one or more Coles search-result URLs and get name, brand, price, size, availability, aisle location and more for every product. Pay per result (see the Pricing tab). The residential proxy is built in.

What data you get

One dataset row per product (ads and banners in the results are skipped).

FieldDescription
idColes product ID
name / brand / descriptionProduct name, brand and description
sizePack size (for example 1L)
availabilitytrue / false
availability_typeAvailability channel (for example in-store and online)
available_quantityQuantity reported as available
featuredWhether the product is featured in the results
ad_id / ad_sourceSponsored-listing identifiers (usually empty)
pricingObject with the price data Coles publishes: current price, was price, unit price and unit of measure, comparable price text, online special flag
image_urisList of image objects
locationsList of in-store aisle/location objects
restrictionsObject with purchase limits, age-restriction flags and delivery options
merchandise_heirObject with the category hierarchy used by Coles
online_heirsList of online category/aisle objects
min_guaranteeMinimum shelf-life guarantee text, when present
variationsList of product variations, when present
from_urlThe search-result page URL the row came from
scraped_atISO 8601 timestamp of the run

Nested fields stay as JSON objects/lists, not flattened strings. Missing optional values are null, an empty list or an empty object.

How to use

  1. Search for a product on coles.com.au and copy the address of the results page (for example https://www.coles.com.au/search/products?q=milk).
  2. Paste one or more such URLs into Search result URLs.
  3. Set Max items total to the number of products you want across all URLs.
  4. Leave Proxy configuration on the default (Apify Residential, Australia). It is already set up; you need no extra account.
  5. Click Start, then open the table view or export the dataset as JSON, CSV or Excel.

The actor walks the result pages of each URL until it reaches your item limit or the end of the results.

Input

FieldTypeDefaultDescription
urlsarray of strings (required)https://www.coles.com.au/search/products?q=milk (prefill)Coles search-result URLs
maxItemsinteger100Maximum product records across all URLs (1 to 5000)
proxyConfigurationobjectApify Residential, country AUProxy settings. The default is recommended for reliable access

Example input:

{
"urls": ["https://www.coles.com.au/search/products?q=milk"],
"maxItems": 100,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"],
"apifyProxyCountry": "AU"
}
}

Output example

Values below are illustrative.

{
"id": "1234567",
"ad_id": null,
"ad_source": null,
"featured": false,
"name": "Full Cream Milk",
"brand": "Coles",
"description": "Full cream milk 2L",
"size": "2L",
"availability": true,
"availability_type": "InStoreAndOnline",
"available_quantity": 1200,
"image_uris": [{ "alt_text": "", "type": "default", "uri": "/1/1234567.jpg" }],
"locations": [{ "aisle": "Dairy", "aisle_side": "Front of Store", "description": "Located in Dairy" }],
"restrictions": { "retail_limit": 50, "liquor_age_restriction_flag": false, "delivery": ["REMOTE SERVICE"] },
"merchandise_heir": { "category_group": "DAIRY", "category": "MILK", "sub_category": "FULL CREAM MILK" },
"online_heirs": [{ "aisle": "Milk", "category": "Dairy, Eggs & Fridge" }],
"pricing": { "now": 3.1, "was": 0, "unit": { "price": 1.55, "of_measure_units": "l" }, "comparable": "$1.55 per 1L", "online_special": false },
"min_guarantee": null,
"variations": [],
"from_url": "https://www.coles.com.au/search/products?q=milk&page=1",
"scraped_at": "2026-10-02T09:30:00Z"
}

Use cases

  • Grocery price monitoring: track shelf prices, specials and unit prices over time.
  • Assortment and brand research: see which brands and pack sizes appear for a search term.
  • Availability tracking: monitor stock status and available quantities.
  • Category analysis: use the category hierarchy fields to group products.

FAQ

Do I need an API key or my own proxy? No. The residential proxy (Australia) is built in. You do not need any API keys or external accounts.

How is it priced? Pay per result. See the Pricing tab for the current price per product.

What if I do not paste a search URL? urls is required. The actor works from Coles search-result URLs that you copy from your browser's address bar.

Is there a limit for free-plan runs? Runs on a free Apify plan return a small preview (the first URL, up to 10 products, first page only). Paid plans have no preview limit.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

  • schema version, Actor name and build number;
  • UTC start and finish hour (not a precise timestamp);
  • run duration, number of results and time to the first result, each as a coarse range;
  • whether the result was empty, the end status, and an error type from a fixed list;
  • memory setting and counts of charged events;
  • names of the input fields you set, never their values;
  • the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

  • the result limit you asked for (a range, when the input has one) and what share of it was delivered;
  • results delivered per input item you listed (a range);
  • output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
  • how the run was started (console, API, schedule, webhook, another Actor);
  • how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
  • if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
  • a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.