Prices are competitive information, at least competitive enough to warrant obfuscation and preventing scraping.
And, the more sources you have, the more likely things will constantly fail. Scraping is always fragile.
One of the first web-scraping projects I ever built was to find the lowest price for Clif bars. I ate about 365 per year, and in only 45 minutes of programming a cron job and push notifications, I easily saved $100 that year.
Services like Crawlera act as a proxy that also forces you to be nice. If anyone is getting into this, I would recommend they use a service like that to scrape at scale.
Let me just supply the URL and the price string... and let it automatically figure out the right <div> or class or id or surrounding text it can be extracted from. And if it ever breaks (can't be found, or returns something in a different numeric format) then just notify me to visit it and see what's up.
Command-line is one way to do it (can be the canonical version), but then a browser extension makes it even easier. You'll need a headless browser even from the command-line in any case, since the product info isn't always in the HTML at all.
I've actually been toying with this concept for a weekend project, essentially a quick 'n dirty node daemon process that checks prices periodically, for sites it knows how to. More often than not the data is just sitting there in JSON in the <head>, so you wouldn't necessarily have to scrape it either. (e.g. fossil)
Open source the project to let others send PRs for other sites...
Toss in a sendgrid key for emails and you're all set...