Not every price difference spotted while checking a hotel is worth an alert. A lower number attached to a smaller room, a different cancellation policy, or a rate that excludes breakfast when the original booking included it isn't a real match — it's a different product that happens to share a hotel name, and surfacing it as a "lower price" would be misleading.
A confirmed match means the room type, occupancy, and — where possible — the specific rate terms line up closely enough with the original booking that comparing the two prices is genuinely fair. When that bar isn't cleared confidently, no alert goes out, rather than sending a lower-confidence "maybe" that risks sending someone into a rebooking that doesn't actually make sense.
This is a deliberate tradeoff: fewer alerts, but every alert that does arrive is one worth acting on. It's the same logic as any good filter — the value isn't in catching every possible signal, it's in not wasting attention on the ones that don't hold up under a closer look.
If a room can't be confidently matched at all — because a hotel changed its room categories, or a rate plan genuinely disappeared from availability — tracking continues quietly rather than sending a false alert, waiting for a day when a confident match becomes possible again.
