What actually changed
The start of ETIAS has moved for the fourth time. The short version: applications open later than the last published plan, and the period where a missing authorisation does not stop anyone at the gate runs longer than most teams have budgeted for.
That grace period is the part worth reading twice. It is not a delay of the rule: the requirement exists from day one. It is a delay of enforcement, and it ends on a date that is already published.
Who needs one
Anyone traveling to a Schengen country on a passport that does not already require a visa. In practice, for most sellers, that is a large slice of the long-haul book:
Dual nationals traveling on an EU passport are out of scope. Residence permit holders are out of scope. Both of those are frequent support tickets, so it is worth saying so on the confirmation page rather than in a help centre article.
The rule is not the hard part. Telling the right traveler, at the right moment in the booking, is the hard part.
What to change in your flow
Ask for nationality before the payment page. Requirements depend on the passport, not the billing country. If you only collect it at check-in, you cannot tell anyone anything useful.
Show the requirement on the itinerary. Confirmation emails are opened once. The itinerary is opened the week of travel, which is when people act.
Do not hard-code the fee. It is set in euros and will be re-set. Read it from the requirements response and render whatever comes back.
GET /v1/requirements starts returning ETIAS for affected routes on the day it applies, with the live fee and processing time. No version bump, no deploy.
What we're watching
Two things could still move. The first is whether carriers are asked to verify authorisation at boarding from day one or from the end of the grace period. The difference decides how loud your pre-departure messaging has to be. The second is the approval time under load. The published expectation is minutes for most applicants; the first week of any scheme of this size is the exception.
We will update this note when either lands, and the changelog on the same day.