Get flight price alerts

Why travellers get flight price alerts in the first place

Most people who go looking to get flight price alerts aren't trying to find one perfect fare on one exact date. They're trying to reduce the time they spend manually refreshing search results across airlines and booking sites. An alert system does that watching for you, but it's worth being clear about what it actually delivers: a notification that a price or route condition changed, not a booking, and not a guarantee that the fare will still exist when you click through.

Flare fits into this picture as a publisher of flight-deal discovery pages organized by a traveller's departure city. Rather than acting as a booking engine, Flare's pages are built to surface routes and fares that its monitoring has flagged as notably below what it calls the route reference price. That framing matters for expectations: you're being pointed toward a deal worth a closer look, not handed a locked-in price.

Understanding this distinction early helps you use alerts as a discovery tool rather than a source of certainty. The rest of this article treats alerts as one input into a broader trip-planning process, alongside your own flexibility, total trip cost, and the entry requirements that apply to you specifically.

How fare alert systems typically work, and where Flare fits

Generally, a fare alert service tracks prices for a route or set of routes over time and pushes a notification when something changes: a price drop, a return to a baseline, or a fare that falls outside a normal range. Google Travel documents a version of this for individual searches, letting you track flights and prices for routes you specify so you get notified as fares shift (support.google.com/travel/answer/6235879). That's a useful, narrowly-scoped way to watch a route you already know you want.

Flare's approach is oriented differently: instead of you specifying a route to watch, Flare publishes discovery pages by departure city, surfacing fares its methodology has already identified as meeting a specific threshold. According to Flare's published methodology, surfaced deals are detected at least 30% below the route reference price used by its monitoring (flareflights.com/methodology.html). That threshold is a description of how the underlying monitoring flags candidates for publication, not a promise about any specific fare you'll see on a given day.

Both approaches are complementary rather than competing. A route-specific alert is good when you have a fixed destination in mind. A departure-city discovery page is more useful when you're flexible about where you go and want ideas to already be pre-filtered by the reference-price comparison Flare's methodology describes.

Reading a fare alert without over-trusting it

The single most important habit for anyone using flight price alerts is treating every displayed number as provisional. Flare's public pages, like most fare-discovery tools, describe fares and availability that can change, and that must be confirmed with the actual booking provider before you commit. An alert or a discovery page is a starting point for a search, not the final word on what you'll pay.

This matters practically because fare inventory can shift within minutes, seat classes at a given price point can sell out, and taxes or fees can appear only once you reach the airline's own checkout. None of that means alerts are unreliable as a category, it just means the gap between 'flagged as a deal' and 'confirmed bookable at that price' needs to be closed by you, at the source, before you rely on it for trip planning.

A useful mental model is to treat any alert or discovery listing as a lead worth investigating within a short window, rather than a locked reservation. If you can act on a flagged fare within a day or two of seeing it, your odds of the price still holding are generally better than if you sit on it for a week and hope it remains available.

Total-trip context: why the fare alone isn't the decision

A fare that clears a discount threshold is only one variable in whether a trip is actually a good deal for you. Baggage policies, layover length, the airport you'd actually depart from versus the cheapest nearby alternative, and the total cost of getting to and from airports can all shift the real value of a fare that looked attractive in isolation.

This is where flexible comparison earns its keep. If you're not committed to one destination, it's worth comparing several flagged fares side by side on total trip cost and convenience rather than picking whichever number is lowest. A slightly higher fare with a direct flight and reasonable arrival time can be a better outcome than the cheapest fare with two layovers and an overnight arrival that forces you to book an extra night of accommodation.

Building this comparison habit turns a stream of price alerts into an actual decision process, rather than a source of pressure to book quickly whenever a notification arrives.

Worked example: comparing three alerts before booking

To make this concrete, imagine a flexible traveller receives three separate notifications in the same week, all departing from their home city and all flagged as meeting a discount threshold on their respective routes.

In this hypothetical, Fare A is the cheapest on paper but includes a long overnight layover and a budget carrier with strict baggage limits. Fare B costs a bit more but is a direct flight with a normal daytime arrival. Fare C is similar in price to Fare B but goes to a destination with more involved entry requirements for this traveller's passport.

Working through this example, the traveller would need to price out Fare A's likely extra baggage fees and the cost of losing a travel day to the layover, check Fare B's total cost against Fare A once those adjustments are made, and separately confirm Fare C's current entry requirements with the relevant official source before treating it as a live option at all. None of the three alerts, on their own, tells the traveller which is genuinely the best choice; that judgment only comes from adding trip context and verifying the details a price alert can't show.

• List each flagged fare with base price, baggage/fees, and arrival time before comparing
• Discount total trip cost, not just the headline fare, for any option with layovers or budget-carrier restrictions
• Set aside destinations with unresolved entry or visa questions until you've checked official current requirements
• Act within a short window on any fare you decide to pursue, since availability can change quickly

Checking official requirements before you commit

No fare alert, from Flare or otherwise, can tell you what entry, passport, visa, or health requirements apply to your trip. Those requirements depend on your nationality, your destination, and sometimes your specific itinerary, and they can change independently of anything happening with airfares. This is not something a discount threshold or a price-tracking notification is designed to capture.

Before booking, and again before departure, it's worth checking current official sources for the destination in question rather than relying on secondhand or outdated summaries. This is a step that applies regardless of which alert service or discovery page pointed you toward a fare in the first place, and it sits outside anything a fare-monitoring methodology can account for.

Treating this as a separate, non-negotiable checklist item, distinct from price comparison, helps avoid the common mistake of booking a compelling fare first and only checking entry requirements afterward.