Flexible dates should create better choices, not more tabs.
Tell Apricot which departure and return dates can move, how far they can move and what must stay fixed. It can compare specific date combinations without forgetting why the trip works.
Tell Apricot about your tripStart with the decision, not the filter
Date flexibility is useful only when the alternatives still produce the trip you intended. Leaving one day earlier may cut the fare, but it may also add a hotel night, create an impossible arrival or turn a ten-day holiday into eight useful days.
Apricot treats a date window as part of a complete request. The goal is not to display every combination. It is to compare the combinations that respect the route, trip length, schedule preferences, baggage needs and connection tolerance you described.
What changes the answer
Protect the shape of the trip
Outbound and return flexibility are different decisions. Apricot keeps each side of a round trip separate so moving the departure does not silently move the return in a way you did not request.
Compare savings with consequences
A lower fare matters, but so do an extra hotel night, a lost workday, a worse arrival and a longer connection. The useful comparison explains what changed alongside the price.
Keep hard constraints hard
If you must arrive before an event, need a checked bag or refuse an overnight connection, say so. Flexible dates should widen the market without weakening the conditions that make the trip possible.
Use a bounded window
A precise window such as plus or minus two days gives Apricot candidate dates it can search and compare. Very broad or vague periods may need clarification or a narrower first pass.
How Apricot handles this request
Apricot converts natural date language into concrete outbound and return candidates, searches the viable combinations and ranks the returned flights with the rest of your preferences. The shortlist can therefore show a best-fitting date pair, a meaningful saving on nearby dates and an alternative that protects time or comfort.
The Why attached to each recommendation should name the date trade-off directly. A flight is not better merely because it is cheaper on Tuesday. It is better only if Tuesday is genuinely available and the revised schedule still fits the trip.
A better brief in four checks
- Give separate outbound and return windows.
- State any arrival deadline that cannot move.
- Say how many stops or overnight connections are acceptable.
- Include baggage and airline requirements before comparing prices.
The output should make the compromise visible
Apricot returns three options with a clear Why, route context, current prices and seller choices. One can protect the strongest fit, another can show a sensible saving, and a third can make a time or comfort improvement explicit. The goal is not more results. It is a decision you can inspect.
Start with this request