Hey Product Hunt,
We build price monitoring infrastructure, and the thing that kept biting our
customers wasn't collecting prices. It was comparing the wrong two things.
You check your product against a competitor's. You price off the gap. Except
one page was a 500ml and the other was a 750ml. Or a bundle vs a single. Or
last year's model with the same name. The number was real. The comparison
wasn't.
Every free price checker out there compares whatever two URLs you hand it.
None of them check whether it's the same product first. So we built one that
does — it pulls brand, SKU and title from both pages and returns a High /
Medium / Low confidence score. If it can't confirm it's the same product, it
tells you, instead of handing you a number that means nothing.
The build itself went sideways in a way I didn't expect. It worked perfectly
on my laptop and got blocked constantly in production — same code, same
headers. Turned out the shops weren't rejecting our requests, they were
rejecting our data centre. My first instinct was to make the requests look
more like a browser. That was wasted work: I compared the responses byte for
byte and they were identical, because the filtering was happening on the IP
and the TLS fingerprint, which no header can change.
The fix was routing through residential IPs — and the surprise there was that
the cheapest tier worked and the expensive rendering tiers didn't. The thing
that mattered was forwarding headers correctly, not paying for a browser.
Spent real money learning that.
No signup, no email, no gate. Paste two URLs, get an answer in about 20
seconds.
Would genuinely like to hear where it breaks. Weird marketplace URLs and
regional sites are where I expect it to struggle.