Theater and Event Ticketing
I originally posted this over on Ryan's Blog, but figured I should repost it over here for a wider audience and posterity.
There are three theater scenarios that I can think of:
1. Theaters that are 100% general admission
2. Theaters that sell tickets by section, and are general admission within each section
3. Theaters that sell individual seats.
Scenario 1 and 2 seem like they may be easier to implement, as described in the comment above, you could set stock for the product variants (tickets by section).
Scenario 3 seems like the trickiest, and most specialized. Each theater would need to have a set of product variants, there could be literally thousands of variants (one for each seat), and when ordering, a customer would likely want to sort by section or price and then buy contiguous tickets.
I wonder if the Theater Ticket use case requires its own contributed module for managing seating arrangements and presenting a purchase interface that caters to the task, allowing a user to select by section, or by price and then pick contiguous tickets, perhaps even limiting results to only those where there are n# of contiguous tickets (where n# is the the number of tickets the customer has indicated they wish to buy).
The larger issue though is that the ubercart product infrastructure should be able to support this specialized use case.