Pharmacy Online AU Product Scraper

Turn Pharmacy Online Australia's public catalog into clean datasets for price monitoring, product research, pharmacy comparison, and ecommerce automation.

The Actor searches more than 14,000 catalog records without a browser. It can return lightweight listings or rich product records with ingredients, directions, warnings, prices, availability, categories, SKU, and barcode.

This is an unofficial Actor and is not affiliated with Pharmacy Online. Product information is not medical advice; always verify important information against the retailer or product label.

What you can collect

• search — search products by phrase
• item — retrieve one exact product by product ID, SKU, barcode, or URL
• categories — list live top-level categories and product counts
• category — browse products in a category
• brand — browse products from one brand
• search_filters — export live category, brand, and price filters

Product rows use a consistent ecommerce shape:

• identity: id, sku, barcode, name, brand
• pricing: price, discount_price, currency
• catalog: category, categories, source_url, images
• availability: in_stock, stock_status
• optional rich fields: description, ingredients, usage_instructions, warnings, variants

The default Dataset contains the collected rows. The default key-value store record OUTPUT contains run status, totals, errors, proxy diagnostics, and monetization metadata.

Quick start

Search three products:

{
  "operation": "search",
  "query": "vitamin c",
  "limit": 3,
  "proxyConfiguration": "direct"
}

Get one rich product by barcode:

{
  "operation": "item",
  "barcode": "9313923120054",
  "proxyConfiguration": "direct"
}

Browse a brand:

{
  "operation": "brand",
  "brand": "Blackmores",
  "limit": 20,
  "details": false,
  "proxyConfiguration": "direct"
}

Pricing semantics

When a product is discounted:

• price is the regular/catalog price
• discount_price is the current lower price

When no verified discount exists, only price is returned. Currency is AUD.

Rich details

The item operation always returns rich fields when the source provides them. For search, category, and brand, enable details to include those fields.

Rich listing mode does not open every product page or create one request per item. The fields are already available in the same storefront search response, so this remains much cheaper than browser-based enrichment.

Proxy strategy

direct is the cheapest verified route and the recommended default. The Actor also exposes datacenter, Australian residential, and special Apify proxy modes for diagnostics or future access changes. A browser is not required.

Use with n8n / Make

A practical workflow is:

Schedule → run Actor → wait for completion → read Dataset → Google Sheets / Telegram / CRM

An importable n8n starter is included in examples/n8n-pharmacy-online-to-google-sheets.json. Set APIFY_TOKEN, select your Google Sheets credentials, and replace the placeholder spreadsheet ID.

In Make:

1. Schedule the scenario.
2. Use an HTTP module to POST /v2/acts/T9uXyvuOEq8AXepW4/runs?waitForFinish=120.
3. Send the desired Actor input as JSON.
4. Read data.defaultDatasetId from the response.
5. Request /v2/datasets/{datasetId}/items?clean=true.
6. Route rows to Google Sheets, Telegram, or your CRM.

Run through the API:

curl -X POST \
  "https://api.apify.com/v2/acts/T9uXyvuOEq8AXepW4/runs?token=$APIFY_TOKEN&waitForFinish=120" \
  -H "Content-Type: application/json" \
  -d '{"operation":"search","query":"sunscreen","limit":20,"proxyConfiguration":"direct"}'

Then fetch the Dataset:

$curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json"

Keep API tokens in credentials or environment variables, never directly in a shared workflow.

Operational notes

• page is zero-based.
• limit accepts 1–100 items per listing request.
• includeRaw is intended only for debugging and can make OUTPUT large.
• An exact item miss produces an empty Dataset and a structured ItemNotFound error.
• Source text is cleaned and repaired where possible, but retailer data can still contain spelling or labeling issues.