Yes, I understand it better now.
So, technically each dates makes a product unique. So, technically you would need to store the date with each product: Chinese on wednesday 10th is different from Chinese on the 11th.
But obviously, you don't want your users to create hundreds of different, but very alike items.
So, instead, I would store the dates in a separate table, like AvailableDate, and create a junction table between this table and the product table, for example: ProductAvailableDate.
Then in the CMS of the shop, a user can select multiple dates (with a Calendar and a GridView for example) that are applicable for a product.
Next, when you query for the relevant products, you can join the Product and the AvailableDate items so you get the relevant product / date combinations. Each product you add to List (Of Poduct) in the GetList method can have an AvailableDate property that you can show on the site.
Does this put you in the right direction? The chapter Appointment Booking Application has something similar. The CMS allows you to make booking objects available for certain days only. Then the bonus walkthrough of that chapter guides you through creating an exception day functionality, which is more or less the reverse of what you're trying to do.
Hope this helps,
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results
and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post