Coles Daily Grocery Pricing, Specials & Availability Dataset
The same 19-column Coles catalogue as the weekly file, captured every morning — price, promotion, pack, origin, brand, category and dietary information, each as structured JSON.
Grocery specials run on short cycles, so daily is where they are actually visible: in the sample 12 of 50 SKUs carried a SPECIAL, alongside 11 lines unavailable and shelf prices from A$0.46 to A$36.00.
The file already exists, because this pipeline runs every day whether you buy it or not. Most vendors start collecting after you order — which is why they quote a lead time. Here the most recent file is in your account within minutes of payment, with an API key issued at the same time.
What you get, in plain terms
Four things. Supermarket pricing at the speed specials actually move.
A dated row every morning
Australian grocery specials turn weekly and availability moves daily. Each morning's capture dates the change rather than leaving it somewhere inside a week.
Structured fields, not flat text
price, promotion, pack, origin, brand, category and dietary_info each arrive as structured JSON — shelf price, price per unit, pack weight, category tree, Australian-grown status and dietary flags, ready to parse.
Price per unit as published
price carries price_per_unit_display and price_per_unit_aud — “$19.90/ 1kg” — so comparable pricing needs no arithmetic and no assumptions about pack size.
However you want it
Direct download, REST API, Amazon S3, Google Cloud, Snowflake or SFTP. The API key comes with the dataset.
Fields included in this dataset
All 19 columns, in the exact order they appear in the file — taken straight from the sample, not from a brochure. The free sample ships with a data dictionary giving an example value for each one.
Sample rows from the real file
Real rows from the sample file, not an illustration. The supplied sample has 50 SKUs with all 19 columns.
Coverage
Captured every day across coles.com.au. One row is one SKU, identified by product_id and timestamped in scrape_date.
| Metric | In the supplied sample | What it tells you |
|---|---|---|
| Rows | 50 SKUs | Fruit & vegetables in this sample |
| Specials | 12 of 50 SKUs flagged SPECIAL | Flag only — see the note |
| Shelf price | A$0.46 – A$36.00 | Median A$4.90 |
| Available | 39 of 50 | 11 unavailable online |
| Origin | Australian Grown on 30 of 50 | Plus mixed-origin lines |
| Own brand | Coles-branded on 38 of 50 | Own label vs supplier brands |
Only tracking a category, a brand or your own SKU list? Send the list and we will price a narrower file.
Historical data
The last 30 days come with the dataset. Beyond that we hold Coles records from February 2025 onwards.
Ask about historical dataNeed more data points?
We can extend this dataset beyond the standard 19 columns — the nested fields pre-flattened and the pre-promotion price added are the most requested changes.
Request custom fields“Specials here change on a weekly cycle but availability changes daily. We needed the daily file to tell those two apart.”
What people use this dataset for
FMCG brands and suppliers
See a special the day it starts and the day it ends, rather than inferring it from a weekly snapshot.
Pricing teams
Track shelf price and price per unit daily across your lines and your competitors'.
Supply and availability teams
Catch out-of-stock lines the day they go, category by category.
Retail analysts
Build a dated price and availability series for the Australian grocery market.
About Coles daily grocery data
Coles runs more than 800 supermarkets across Australia and sells the same catalogue online. At daily cadence the file becomes a record of when prices and availability changed, not just what they were.
Why daily for grocery
Specials run on short cycles and availability moves within a day. A daily capture dates the start and end of a promotion and catches a line going out of stock before it costs a week of sales.
Everything nested, deliberately
Coles publishes a rich product record and this feed keeps its shape rather than flattening it: pack size in grams alongside the display text, the full category tree, manufacturer and sub-brand, and five dietary booleans. One json_normalize and it is a wide table.
Two things to plan for
promo_price_aud matched the shelf price on every sampled row and price_was_aud was never populated, so this file flags that a SPECIAL exists but not how deep it is — we can add the pre-promotion price on a custom feed. gtin and extended_attributes came through empty, and nutritional information appeared on 8 rows, allergens on 3.
Is collecting this data legal?
Collecting publicly visible product and price information is generally lawful in most jurisdictions. Actowiz collects only public pages, respects robots.txt and platform terms, holds no personal data, and aligns with GDPR and CCPA. We are ISO 9001 and ISO 27001 certified, and this dataset carries documented provenance so your legal team can review the source before you buy.
Frequently asked questions
promo_type flags a SPECIAL but promo_price_aud equalled the shelf price on every sampled row and price_was_aud was empty. We can add the pre-promotion price on a custom feed.
json_normalize expands them in one step, or we can deliver the file pre-flattened.
