Travel & Local Prices: Flights, Hotels, Gas

LMSlay4 days ago

For readers comparing flight dates manually, decide what stays fixed before sorting options. These are invented examples, not searched fares: • Fixed seven-night stay: 20–27 November 2026 versus 21–28 November 2026. • Fixed return on 27 November 2026: 20–27 November versus 21–27 November; the second stay is shorter. • Price-change comparison: keep 20–27 November 2026 unchanged and compare observations made at different times. Start with Google Flights’ native Dates / Price graph tools, or price tracking if you only need alerts. A paid export is optional. Keep route, both dates, passenger count, cabin, stops and currency alongside any comparison; add an observation time and source link. Leave unknown prices or fees unknown, and review the final itinerary and offer with the booking provider. The full checklist explains these distinctions: https://github.com/LMSlay/tubetext-examples/blob/main/recipes/google-flights-date-comparison-checklist.md Prepared by TubeText Labs, provider of the optional paid Actor, with AI assistance. Static educational checklist based on documentation reviewed on 25 October 2026; no live run or fare validation. No availability, savings or booking guarantee. Use data only with the necessary rights and in accordance with source terms.

LMSlay3 days ago

Comparing two saved hotel quotes For a hotel-price comparison, section 3 of our existing guide walks through two observations of the same stay, with a fictional worked example: https://dev.to/lmslay/google-hotels-prices-per-booking-site-and-a-90-day-price-calendar-as-json-3b8a Keep both stay dates fixed when comparing quotes collected on different days. Check property identity, occupancy, currency, booking source, room and rate conditions before calculating a change. Record collection time separately; a calendar of different check-in dates does not reconstruct earlier observations. The guide also separates the hotel's tax/fee flag from evidence for each vendor offer. If terms or tax inclusion cannot be verified, leave the comparison unresolved. A missing matching offer should be recorded as not observed, rather than zero or sold out. Nightly prices and whole-stay totals need separate columns. This is an existing documentation resource, not a new run or an integration test. Its examples are fictional and its price-check date is explicit; check the Actor's current Store pricing before any paid execution. No availability, lowest-price, savings or booking guarantee. Prepared by TubeText Labs, provider of the optional paid Actor, with AI assistance. Use source data only with the necessary rights and in accordance with source terms.