[Udo]

I feel that maybe I didn't express myself clearly, apologies. The main point from a user experience design perspective here isn't that Yield Management is happening (which is perfectly OK, the article just didn't recognize it). Instead it's this:

> We wanted to our users to be able see how long a price point is going to remain available.

On a flight where every single seat represents a discrete price point, this information becomes dubious at best. What's more, the UI on your website makes the semantics of this very murky, culminating in unnecessary misunderstandings like this article.

To make it perfectly clear: I'm not suggesting there is anything wrong with your business practices. Instead, the fault lies with your user interface for not making the distinction clear between the number of seats available on the flight in general and the number of seats left at the current price point (which is almost ALWAYS equal to the number of seats the user has requested).