cck fields available to Global replacement patterns

There aren't any product CCK fields... I think you might be confused. Are you wanting CCK fields to come into the order product attribute display?

That is right - I have created an event product (theatre performance) with a cck date field. Their are five products all called say "Romeo and Juliet" with different dates so you can choose Wed 1st or Thu 2nd or.... But if you buy one the title "Romeo and Juliet" will be in the order invoice but no mention of the performance date /time.

try buying a couple of seats at http://venturacottage.com/uber11/rocky-horror-show-13 with test creditcard details

4111111111111
valid date
CVV 123

Thanks

I see what you mean. I really don't think this should be a core feature, but a contrib module can do the work of bridging CCK field data into the cart/order product descriptive text using the same mechanism that attributes use. In fact, other sites I've seen would use an attribute for letting people specify a showing instead of separate products, so the date would come through the system like that.

Good points - but my thinking is that most performances, have a limited number of seats per performance so (I think) it is important to use the stock option to stop selling Saturday's dress circle seats once 15 have gone. I cant think how you could do that without treating each performance as a seperate product. I do think if we could get this right then it has major implications for ubercart - for instance the same model could be applied to Camping/Caravaning pitches, Tanning Salons, Counselling Sessions. I feel I am 90% there, but it depends how valuable others consider this. Thanks for your feedback

Well, if you make the date an attribute and give each option a unique SKU, you should be able to set the stock level by SKU instead of just by the product node.

I am using unique sku s the set stock for each type of seating eg stalls, dress circle, gallery etc and it works well and I can do everything as long as I do it manually. But I hit on what I thought would be a good idea I combined the event product with http://drupal.org/project/date_repeat_nodegen - if done at the time of creating the product - say it was everyday for the next 3 months except Sundays, it has an option to create ALL 90 performance nodes at once, the seat types and tiered pricing is all passed automatically by using classes.

This becomes impractical if you had to manually create each node.

I like your idea of using date as an attribute - but my understanding is that you cant combine two (or more) attributes to create stock eg
red small tshirts - 20
red small tshirts - 19
friday 19th stalls seats -5
friday 19th gallery seats - 9