FoodWorks AU Grocery Product Scraper avatar

FoodWorks AU Grocery Product Scraper

Pricing

from $0.10 / 1,000 results

Go to Apify Store
FoodWorks AU Grocery Product Scraper

FoodWorks AU Grocery Product Scraper

Scrape FoodWorks Australia grocery product search results, category listings, prices, specials, and normalized item data for grocery research and monitoring.

Pricing

from $0.10 / 1,000 results

Rating

0.0

(0)

Developer

Dmitriy Gyrbu

Dmitriy Gyrbu

Maintained by Community

Actor stats

1

Bookmarked

3

Total users

1

Monthly active users

41 minutes ago

Last modified

Share

FoodWorks AU Product Search, Catalog & Store Discovery (Unofficial)

Search products from FoodWorks Australia, fetch normalized catalog data, and discover real shop values from the live store chooser.

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

Supported operations

  • stores
  • search
  • item
  • categories
  • category

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.

  • stores Required: none Optional: query, limit, includeRaw
  • search Required: query Optional: shop, page, includeRaw
  • item Required: itemSlug or itemId Optional: shop, includeRaw
  • categories Required: none Optional: shop, topOnly, includeRaw
  • category Required: categorySlug or categoryId Optional: shop, page, includeRaw

How shop values work

Do not rely on old examples like eastivanhoe unless you verified that store is still online.

Use the stores operation first. It parses https://shop.foodworks.com.au/change and returns the current live store list, including:

  • shop: canonical host prefix, for example griffithreddrop-shop
  • catalogue_url
  • shop_url
  • store_info_url
  • address, phone, and store attributes

The current verified working examples in this actor use griffithreddrop-shop.

Example inputs

{
"operation": "stores",
"query": "griffith",
"limit": 5,
"includeRaw": false
}
{
"operation": "search",
"shop": "griffithreddrop-shop",
"query": "bananas",
"page": 1,
"includeRaw": false
}
{
"operation": "categories",
"shop": "griffithreddrop-shop",
"topOnly": true,
"includeRaw": false
}
{
"operation": "category",
"shop": "griffithreddrop-shop",
"categorySlug": "fruit-vegetables",
"page": 1,
"includeRaw": false
}
{
"operation": "item",
"shop": "griffithreddrop-shop",
"itemSlug": "bananas-kg",
"includeRaw": false
}

Output

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

Notes

  • search uses the upstream Myfoodlink q parameter, not the older broken query parameter.
  • shop accepts a host prefix like griffithreddrop-shop, a store name like Griffith, or a full shop URL.
  • item payloads now include richer metadata such as category path, availability, currency, and store context.
  • topOnly=true limits categories output to top-level categories.
  • Default proxy strategy is direct.
  • The runtime is prepared for future pay-per-event monetization.