In the comments of Chasing The Points milemadness Secret Revealed, I mentioned a vendor and said there was too much data and tough to work with.
During the review process, I discovered that listed rebates and how the product is displayed is fairly easy to retrieve. I am not a programmer, but I am learning to code, so progress will be slow on this one. What I need to do is grasp the understanding of how to grab the data and pass it to the developer as a functional specification. A functional specification, basically, is what you want as an end result without too much technical details.
The biggest hurdle I see are plenty of SKUs (Stock Keeping Units) per rebate offer and all the text to describe the offer. For successful data grabs, we need to find a consistent pattern to tell the program what to expect and then handle the specific conditions.
As soon as I can land some code, I’ll be sure to pass it to Big Habitat and have him test it for reselling opportunties.
Stay tuned!
What kind of code is this? Not a formally trained programmer either but I’ve written and work with code that retrieves and parses thousands of pages daily. Maybe I can contribute or give some pointers? Can’t see the comments on the other page since it seems to be password-protected.
Just sent you an email with the password
What’s the criteria to get the password for the other page, please 😀 Would definitely like to see if possible 🙂 Thank you.
Just emailed you the password
The end game is to determine the lowest final price automatically when a rebate is posted so items can be resold or free after rebate type items for free points with a little bit of work