Skip to content
This repository has been archived by the owner on Dec 3, 2020. It is now read-only.

Wrong Price after product configuration - #268

Open
rick9004 opened this issue Nov 14, 2018 · 3 comments
Open

Wrong Price after product configuration - #268

rick9004 opened this issue Nov 14, 2018 · 3 comments
Labels
[ENG]: Extraction Issues related to product extraction, including Fathom

Comments

@rick9004
Copy link

While on Walmart product page with multiple choices the price I configured was 979.00 Price-wise displays 79.99 . See screenshot
2018-11-14 10_06_47-microsoft surface book 13 5_ 8gb_ 256gb intel core i5 windows 10 pro - walmart c

@biancadanforth
Copy link
Collaborator

Well that's quite a steal!

In all seriousness, thank you for taking the time to file this issue. Could you share the URL for the product page you saw this issue on?

I found what I think is a similar page, but Price Wise is not demonstrating exactly the same behavior.

So you chose an option, the price changed to reflect that option, then you added the product to your list. Is that the correct series of events?

This smells similarly to #86 , but I am curious where the "$79.99" came from, as I can't imagine any option for the computer would be that low, so I wonder if there is more than one issue on this page at once.

@pdehaan
Copy link
Contributor

pdehaan commented Nov 14, 2018

@pdehaan
Copy link
Contributor

pdehaan commented Nov 14, 2018

Although, as I went to close this tab I clicked the "Not available" 512 GB hard drive option and Price Wise detected the non-available item as a price drop down to "$512.00" (which I believe is scraping the 512.00 GB hard drive size.

help_and_microsoft_surface_book13_5__8gb__128gb_intel_core_i5_processor_windows_10_pro_-_walmart_com_and_downloads

@muccimoz muccimoz added the [ENG]: Triage Work the team needs to review to determine if it will be included as part of the next milestone. label Nov 15, 2018
@biancadanforth biancadanforth added [ENG]: Extraction Issues related to product extraction, including Fathom and removed [ENG]: Triage Work the team needs to review to determine if it will be included as part of the next milestone. labels Nov 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
[ENG]: Extraction Issues related to product extraction, including Fathom
Projects
None yet
Development

No branches or pull requests

4 participants