Troubleshooting PRICE_NOT_FOUND Errors

PRICE_NOT_FOUND means PriceFetch successfully loaded the page but couldn't find a price element. This is different from PAGE_LOAD_FAILED (page didn't load at all). Here are the causes, ranked by frequency:

**1. Out-of-stock product** — many retailers remove the price display entirely when a product is out of stock. The page loads fine, but there's no price to extract. Check the `in_stock` field if available, or visit the URL in a browser to confirm.

**2. Wrong URL type** — you're passing a category page, search results page, or storefront URL instead of a specific product page. PriceFetch expects individual product URLs (e.g., `amazon.com/dp/B0EXAMPLE`).

**3. Regional restriction** — the product isn't available in the region PriceFetch is accessing from. Some Amazon products are only visible to users in specific countries.

**4. Page structure change** — the retailer updated their HTML and PriceFetch's selectors haven't been updated yet. This is uncommon but does happen. Report it to support with the URL and we'll update the scraper.

**5. Adult/restricted content** — some retailers gate certain products behind age verification or login walls, preventing price extraction.

When you get PRICE_NOT_FOUND:

1. **Open the URL in a browser** — can you see a price? If not, the product is likely out of stock or restricted.

2. **Check the URL format** — ensure it's a direct product URL. Amazon URLs should contain `/dp/` or `/gp/product/`. Walmart URLs should contain `/ip/`.

3. **Try a different product from the same retailer** — if it works, the issue is specific to that product (stock, restrictions). If it fails too, it might be a scraper issue.

4. **Check the URL in an incognito window** — if the price only shows when you're logged in, PriceFetch can't see it either.

5. **Report persistent issues** — include the URL and the `request_id` from the error response. PriceFetch's scraper selectors are updated when retailers change their page structure.