Re: Setting Up Table/s Question

There are several ways to solve this problem, I have written about a couple.

In your specific situation, I recommend sticking with one table. The custom attributes seem similar enough. If a product only has one state at a time and you need it to behave differently when in this state, I recommend using Single Table Inheritance.

This approach is pretty flexible as it allows you to fairly easily move into a more complex schema (like one mentioned in my other post) if you find it necessary.