[mitchkramez]

Have a potential new client and they have a question...

They want to sell tickets to conferences, so the conference would be listed as a product, but they want to be able to buy multiple tickets for different people in the office. They would add the 'conference' to the cart and specify who that ticket is for.

This works fine if they add different products, but is there a way that they could add, say, 4 of the same conference tickets to the cart, and have them not be grouped in the same cart line item so they could specify a different name for each one?

Does that make any sense? I'm not sure how best to explain that, but hopefully that's clear enough to get the gist.

[Aleksey]

Hi, Mitch!

You can extend products (and cart items and order items) with a new field - x_holder_name (for example). On the Product page you can add a field Holder Name and require customers to populate it before adding the product to the cart. LemonStand does not merge cart items with different custom field values. This case is much simpler than your newspapers store ;-)

Thanks

[mitchkramez]

Great thanks! Would they have to order one at a time from the product detail page I assume then? I think that's fine, and really isn't a big deal.

Quote

Hi, Mitch!

You can extend products (and cart items and order items) with a new field - x_holder_name (for example). On the Product page you can add a field Holder Name and require customers to populate it before adding the product to the cart. LemonStand does not merge cart items with different custom field values. This case is much simpler than your newspapers store ;-)

Thanks

[Aleksey]

Quote

Great thanks! Would they have to order one at a time from the product detail page I assume then? I think that's fine, and really isn't a big deal.

I thought that is what you wanted to achieve. Another option is to extend the order item (and other) models with a large tex field and allow visitors to specify multiple people at a time. And then use this information for calculating the cart item cost. This task is very similar to the newspapers task, but in this case you use the number of people on the ticket as a price factor.

Thanks

[mitchkramez]

That's true, I hadn't thought of that - I think either would be a good solution - thanks for the input, I'm starting to wrap my head around the "Lemonstand Way" :)

Quote

Quote

Great thanks! Would they have to order one at a time from the product detail page I assume then? I think that's fine, and really isn't a big deal.

I thought that is what you wanted to achieve. Another option is to extend the order item (and other) models with a large tex field and allow visitors to specify multiple people at a time. And then use this information for calculating the cart item cost. This task is very similar to the newspapers task, but in this case you use the number of people on the ticket as a price factor.

Thanks