OpenCart Product Reviews Scraper & Monitor

OpenCart Product Reviews Scraper & Monitor collects public OpenCart product reviews with author, star rating, text and displayed date from product pages and review pagination. Enter a public OpenCart storefront URL to discover products, or paste a product URL for one focused lookup. The output is a structured Apify Dataset that can be exported as JSON, CSV or Excel.

No OpenCart admin account or OpenCart API key is required. The Actor reads pages already visible to shoppers through direct HTTP. An Apify proxy is optional for shops that block the default network route.

Why use this product review feed?

• Keep each review tied to the public product URL, product ID and source review page; use scheduled runs to find newly visible feedback.
• Use a stable product ID or review fingerprint so scheduled runs can compare records.
• Get a run summary with requested, successful, failed and incomplete targets, plus exported record counts.
• Run several OpenCart targets in one job. If one target fails, other targets can still succeed.
• Send the dataset to Apify schedules, webhooks or your own API client.

The Actor retries temporary network errors and logs failures per target. It does not invent exact stock counts when a shop only displays “In Stock.” A shop with customized themes may expose fewer fields than the default OpenCart layout.

Pricing

Pay per event: $0.001 per run plus $0.0005 per exported review. The example totals below are Actor event charges for 256 MB runs:

Exported records	Actor event charge
1	$0.00150
100	$0.051
1,000	$0.501
10,000	$5.001

The exact formula is $0.001 + (exported records × $0.0005). Apify platform storage or data transfer charges can be separate. A target that returns no matching records still incurs the run start event; choose a known product for your first test.

How to use this Actor

Paste a homepage such as https://opencart.ridly.io/ to discover product links through OpenCart categories and pagination. A direct product URL such as https://www.opencartextensions.in/modules-extensions/product-options/opencart-custom-option-pro is faster and ideal for a focused check. Hostnames without a scheme are accepted and normalized to HTTPS.

Quick start with the prefilled public product:

{
  "targets": [
    "https://www.opencartextensions.in/modules-extensions/product-options/opencart-custom-option-pro"
  ],
  "maxReviewsPerTarget": 1
}

For a store-wide scan, set the export cap to zero and raise page limits if your shop is large:

{
  "targets": [
    "https://opencart.ridly.io/"
  ],
  "maxReviewsPerTarget": 0,
  "maxListingPages": 0,
  "maxProductPages": 0,
  "maxReviewPages": 0
}

The prefill requests one product and exports one record. For a storefront scan, maxReviewsPerTarget limits the Dataset output, while snapshots compare every record fetched within the listing and product page limits.

Monitor new, updated and removed reviews

Use the same monitorId and target URLs on repeated scheduled runs. The first run labels records “new”; later runs label them “updated,” “unchanged,” or “removed.” changedFields lists fields that changed. A review fingerprint combines product ID, author, displayed date and text; an edited review can appear as one removal and one new review because OpenCart does not publish a stable review ID.

{
  "targets": [
    "https://www.opencartextensions.in/modules-extensions/product-options/opencart-custom-option-pro"
  ],
  "monitorId": "my-opencart-watch",
  "maxReviewsPerTarget": 0,
  "onlyChangesSince": "2026-09-01T00:00:00.000Z"
}

Omit onlyChangesSince to include unchanged rows. A removed event is emitted only when a complete crawl confirms the record disappeared. If a listing, product or review page limit truncates the crawl, the Actor keeps prior records and reports the target as incomplete in SUMMARY to avoid false removal alerts.

API example

curl -X POST "https://api.apify.com/v2/acts/Clintsa~opencart-product-reviews-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"targets":["https://www.opencartextensions.in/modules-extensions/product-options/opencart-custom-option-pro"],"maxReviewsPerTarget":1}'

For larger shops, start the run asynchronously and read its Dataset when it finishes.

Input options

Field	Type	Purpose
targets	URL list	One or more OpenCart shop homepages, category pages or product pages.
maxReviewsPerTarget	integer	Export cap per target; 0 exports all scanned records. The prefill is 1.
maxListingPages	integer	Maximum category and pagination pages per storefront; 0 removes the cap.
maxProductPages	integer	Maximum product detail pages per storefront; 0 removes the cap.
maxReviewPages	integer	Maximum public review pages per product; 0 removes the cap.
monitorId	string	Persistent name for snapshots across scheduled runs.
onlyChangesSince	ISO timestamp	Emit only changes detected since the given time.
requestDelayMillis	integer	Optional pause between requests.
useApifyProxy	boolean	Optional Apify Proxy fallback for blocked storefronts.
proxyConfiguration	object	Proxy settings when the fallback is enabled.

Output

This illustrative Dataset row uses a public review from the heavier test target:

{
  "target": "https://www.opencartextensions.in/modules-extensions/product-page-and-merchandising/opencart-product-reviews-pro",
  "itemId": "f64c6091f9c4a69aaeb6847c",
  "reviewId": "f64c6091f9c4a69aaeb6847c",
  "productId": "259",
  "productName": "Product Reviews Pro",
  "productUrl": "https://www.opencartextensions.in/modules-extensions/product-page-and-merchandising/opencart-product-reviews-pro",
  "author": "vortexsi",
  "rating": 5,
  "text": "great, fast support :)",
  "date": "29/08/2013",
  "sourceUrl": "https://www.opencartextensions.in/index.php?route=product/product/review&product_id=259&page=1",
  "scrapedAt": "2026-09-30T12:00:00.000Z",
  "changeType": "new",
  "changeDetectedAt": "2026-09-30T12:00:00.000Z",
  "firstSeenAt": "2026-09-30T12:00:00.000Z",
  "lastSeenAt": "2026-09-30T12:00:00.000Z"
}

Every run also writes a SUMMARY record in its default key-value store. It includes scan counts, change counts, completion time and whether Apify Proxy was used.

Use cases

• Review extraction supports customer feedback analysis, quality follow-up and competitor sentiment research.
• Create a repeatable feed from several OpenCart shops without logging in to their administration panels.
• Compare public customer feedback between two scheduled observations.
• Export a small focused sample for a spreadsheet or an automated downstream job.

FAQ

Does this need an OpenCart API key?

No. It requests public storefront and product pages. An Apify account is needed to run the Actor itself.

Can it scan a whole OpenCart shop?

Yes, when public category and product links are discoverable. Set page limits to zero for complete coverage and use a modest request delay on large shops.

Why does a product sometimes return no reviews?

Some products have no approved public reviews, and some shops disable reviews entirely. Those targets can succeed with an empty Dataset; choose a known reviewed product for the daily health-check prefill.

What happens when a shop blocks requests?

The target is logged as failed. You can enable Apify Proxy as a network fallback and retry. A shop's own policies still apply.

How are removals decided?

A record must have appeared in a prior snapshot and be absent from a complete later scan using the same monitorId and target scope.

Limitations and responsible use

Only public reviews are returned. Store themes, review extensions, language settings, cookie requirements and site defenses vary, so a customized review widget may need adaptation. OpenCart may not publish a stable review ID; the Actor hashes visible review details, so an edit can appear as removal plus addition. Review dates are preserved as displayed, without inventing a timezone. Follow each shop's robots.txt, terms and applicable law, and avoid excessive request rates.

Support

Use the Issues tab on this Actor's Store page. Include the run ID, the target URL and the fields you expected so a failing theme or route can be reproduced.