I will use this for the future and will debate how to use this for our site in the long term plans should we see the need for sub categories/et.
The problem is, with the cart working as it does, it'd be a shame to have to re-write it entirely (as well as the db structure) just to add a few non music items. I was wondering if the following idea might work, as the company wants to re-launch quickly.
Step 1: Add New 'merchandise table'
Step 2: Add new product_type table (music = id #1, poster = id #2, book = id #3 etc)
Step 3: Transfer all product ID's of music table to merchandise table before adding merchandise such as posters/non music/etc. (there are 0 non-music items for sale now)
Step 4: Then, change the admin panel to allow both music and non music to go into merchandise while saving the 'product id' type.
This way, we have one table that holds all products while knowing which type.
After this, I re-write the cart to sniff out product id, which it does, but this time it will do it for the merchandise table and not the music table.
This way, all pages programmed to add a product to the cart, by product id, can still do it, but this time I can also have the power, should I need it, to recognize product TYPE.
It's less radical than a new database schema and won't require a ton of re-working of the cart. Does this sound like a logical plan to add merchandise and save time in the re-launch for this company? Am I overlooking anything?