
Amazon Product Scraper
Pricing
$40.00/month + usage

Amazon Product Scraper
Use this Amazon scraper to collect data based on URL and country from the Amazon website. Extract product information without using the Amazon API, including reviews, prices, descriptions, and Amazon Standard Identification Numbers (ASINs). Download data in various structured formats.
4.5 (12)
Pricing
$40.00/month + usage
133
Total users
8.9K
Monthly users
451
Runs succeeded
98%
Issues response
22 hours
Last modified
a day ago
A-Plus Content Extractor fails with "Cannot set properties of undefined" error when processing Key benefits
Closed
The Actor is consistently failing when trying to extract A-Plus content from Amazon product pages. Here are the key details:
Issue: TypeError in GenericTableModule_extractor when attempting to set 'Key benefits'
Error message: "Cannot set properties of undefined (setting 'Key benefits')" Location: generic-table-module-extractor.js:51:40
Reproduction:
URL tested: https://www.amazon.ca/dp/B08QTT1QBX The error occurs consistently across multiple retry attempts (21 retries) Initial error appears with "Images and items length mismatch" before the TypeError
Technical Details:
Actor Version: 3.2.4 Apify Client Version: 2.9.4 Crawlee Version: 3.10.5 Node Version: v20.18.2 OS: Linux
Behavior:
The Actor attempts to retry the request multiple times but encounters the same error All requests fail with the same error pattern No successful extractions were completed
Stack Trace Points to:
Primary issue in generic-table-module-extractor.js Error propagates through the A-Plus content extraction chain Affects the ProductDetailExtractor functionality
Would you be able to:
Check the handling of undefined cases in the GenericTableModule_extractor Verify the data structure assumptions in the A-Plus content extraction logic Add additional error handling for cases where the expected data structure is not present
Let me know if you need any additional information or logs to investigate this issue.

Hello, thank you for opening this issue and for the detailed information.
I've opened an internal ticket and will be come back to you when the issue will be fixed. Thank you for your patience.

Hello again, thank you for your patience.
The problem you were having was caused by a bad formatting on an HTML element created in the A+ section. This was created by an Amazon user and it is impossible for us to account every possible mistake and ensure the success of the scrape. Also, the user corrected their mistake right after this issue was opened and we couldn't find ay other similar occurrence.
We are however monitoring this and try to catch one of this failing Amazon product to learn how to implement a safe error handling before any of your runs could be affected.
We appreciate your feedback and please if any of this behavior happens again, let us know, it will help us a lot.
I'll close this issue to avoid cluttering, but please feel free to reach out if you have any question.