NarrowToolsBrowse tools
Start here
Use a monitor to discover that a supplier document changed, then compare normalized product data to understand the business impact. A changed PDF, a visually different page, and a changed SKU price are three different signals.
Choose the event you actually need to know about
A supplier can replace a PDF at the same address, publish a new link on a download page, or revise only a date on the cover. Decide whether you need an alert for any file change, a new edition, or an actual commercial change. That decision determines the amount of interpretation required.
Create a small register of suppliers, official download pages, document URLs, expected update frequency, and the person responsible for reviewing each alert. Do not start by monitoring every page on a supplier website. Start with the documents that influence a recurring purchasing decision.
Use existing monitoring capabilities first
changedetection.io already supports PDF monitoring and offers browser workflows and AI-assisted filtering. Evaluate those capabilities before designing a new monitor. If a supplier moves the download link, monitoring the listing page as well as the current file can help you notice the new location.
Keep a dated copy of each version you review. A useful alert should point to both the previous and current documents. If access requires a login, confirm that your monitoring method is permitted and that it can handle the normal authentication flow without sharing credentials unnecessarily.
Separate visual differences from price differences
A visual PDF comparison can reveal changed pages, shifted tables, or missing content. It is helpful for triage. It does not, by itself, tell you that a specific product is now sold in a different pack or that its net price increased.
For commercial comparisons, extract a stable product identifier, price, currency, and unit. Normalize those fields and join old and new rows by identifier. Treat new products, removed products, unit changes, and price changes as separate categories. A case of twenty becoming a case of ten should not appear as an ordinary price reduction.
Design alerts around a decision
An actionable report might say which supplier changed, which effective date applies, how many matched products changed price, and which rows need human review. Include a source page for every unusual change. Route the report to an owner who can confirm it before anyone updates a live price list.
Agree on thresholds for review, but avoid assuming that a small change is automatically safe. A decimal extraction error can look like a dramatic change; a changed tax or shipping condition can affect costs without changing the unit-price column. Keep the original document available.
Measure noise and maintenance
Count meaningful alerts, harmless revisions, failed fetches, and rows that need correction. If most alerts are cover dates or formatting, refine the monitored area or the comparison rules. If fetching often fails, address that reliability problem before trusting an apparently quiet monitor.
Begin with two suppliers for a complete update cycle. Only add more when someone can explain each alert and reproduce the result. The goal is a dependable purchasing workflow, not the largest possible monitoring list.
Sources
Updated October 30, 2026. Based on the linked documentation; the tools have not been benchmarked by NarrowTools. Editorial policy