I am new to both umbraco and Tea Commerce. I am trying to do something specific for a webshop but I am stuck. I really hope someone can help me in the right direction.
I am trying to setup a webshop for a tailor business. I need to make it possible for the customers to tailor make their own shirts. The custom shirt will be based on a lot of choices the customer will have to make. For example the customer will have to choose a fabric, a colour, a size, number of pockets, style of collar, long sleeves, short sleeves and so on. All these subproducts have to be shown with a picture so the customers can see what they are choosing.
What is the best way to attack this problem? Shall I create all these subproducts as variants to a product called custom-shirt? If I do that how can I show pictures for variant products? I have also thought of a solution where the procedure of creating a shirt is split in several steps like the cart steps. The first step could be choosing a fabric and then continue to next step where you choose size and so on. I am not sure though how to get this done.
I hope someone can help because I am stuck on this one.
Sounds like an exiting task you have there and it could be solved in several ways with Tea Commerce. I would go for a simple but effective and dynamic solution. If I should try and describe how you could do it:
1. The shirt product would just be one node in the Umbraco content. 2. You will use Tea Commerce's addUniqueOrderLine JavaScript method. This way the shirt can be added many times, with a different setup and quantity each time. 3. The settings of the product (Size, fabric, color etc.) could be created in any number of ways. All that is needed is to add the value of the customers choices to the orderline using updateUniqueOrderLineProperty JavaScript method. E.g. color = "red" or fabric = "wool". All you would have to do then is to write the choices on the order confirmation and the email. 3.a. One option would be to make the choices as subnodes to the "shirt" product node. This way you could easily xslt yourself out of presenting the choises in the order they are sorted in, in the content tree.Would look something like this:
Shirt Colors Red Blue Fabric Wool Cotton
The "Shirt" node would be the product page. When the user then adds the product to the cart he would be taken to the "Colors" page where he would choose from the choices under that "Red" and "Blue". After choosing that he would be sent to the "Fabric" page and so on if there's more choices. The "Red", "Blue", "Wool" and so on can contain the small picture of the choice.
It will take a bit of xslt to do it. But all of it is pretty standard Umbraco setup. The Tea Commerce part will be very small and be centeret on the few updateUniqueOrderLineProperty calls on each step.
Thank you very much. I Will try to implement the ideas you have given. This is roughly how I have thought to do it:
I will create "Custom shirt" as node with 'page' as document type.
I will create a new property called "Category" for the document type product. This way i can list only some categories on a page, for example fabrics only.
I will create all the subitems(fabric, color, size..) as products under the "Custom shirt".
I will create a new xslt file called "CustomProductList". I will probably reuse some of the code in "productList.xslt".
I will split the task of creating a shirt into several steps just like in cartstep01, cartstep02 and so on. In the first step the customer will choose a fabric, in the next a color and so on.
When the cutomer completes the shirt creating process and goes to the cart. He will be presented by 1 shirt with all the customers choices.
The customer can after this create another shirt if he wants to.
Please let me know if this would be a good way to accomplish my task. Can you also please tell me in more details how I can use addUniqueOrderLine and updateUniqueOrderLineProperty. I am not sure at this point how to exactly use these two methods. I understand what they do, but I am not sure when and where I should use these methods.
Sounds good, will be fun for you i recon. A few small advices:
1. "Custom shirt" should have it's own "Product" Document type. This way you will be able to give it some extra properties, without interfering with the "Page" doc type.
2. You might also want to create a specific doc type (e.g. Variant) for the fabric, color, size. Just one that can be used by all. This way you will also be able to give them some special properties AND you can let the user only create "Variant" nodes under "Product" nodes. Makes it much easier for your customer to create products.
3. addUniqueOrderLine is just used instead of addOrderLine. In your case you should use it when the user starts creating his/her product.
4. updateUniqueOrderLineProperty will be used on each step of the product creation process. When the user selects "green" you will update the "color" property on the orderline. like this TeaCommerce.updateUniqueOrderLineProperty([orderLineId], "color", "green")
I hope that helps. Remember that when you are using updateUniqueOrderLineProperty you supply the orderLine id, which you will have to fetch from the order somehow. You will need a bit of JavaScripting for that part I think, as you will have to let the product creation steps know which orderline is currently being edited.
Yes, Its an exciting task and I am sure it will be fun. I now have some ideas of how to get it done. I will be working on this for some time now. Thank you very much for your help and advices. I really appreciate it. If or when I need further help, I will get back to this topic. I hope thats okay.
You are allways welcome to write more questions here, we're just glad to help. :)
Would you mark the correct answer in this topic for future reference. Makes it much easier for others, with the same problem to find a solution. Then you can create a new topic for your next question.
The best way to create custom product?
Hi,
I am new to both umbraco and Tea Commerce. I am trying to do something specific for a webshop but I am stuck. I really hope someone can help me in the right direction.
I am trying to setup a webshop for a tailor business. I need to make it possible for the customers to tailor make their own shirts. The custom shirt will be based on a lot of choices the customer will have to make. For example the customer will have to choose a fabric, a colour, a size, number of pockets, style of collar, long sleeves, short sleeves and so on. All these subproducts have to be shown with a picture so the customers can see what they are choosing.
What is the best way to attack this problem? Shall I create all these subproducts as variants to a product called custom-shirt? If I do that how can I show pictures for variant products? I have also thought of a solution where the procedure of creating a shirt is split in several steps like the cart steps. The first step could be choosing a fabric and then continue to next step where you choose size and so on. I am not sure though how to get this done.
I hope someone can help because I am stuck on this one.
Thanks in advance.
Mudasar
Hi Mudasar,
Sounds like an exiting task you have there and it could be solved in several ways with Tea Commerce. I would go for a simple but effective and dynamic solution. If I should try and describe how you could do it:
1. The shirt product would just be one node in the Umbraco content.
2. You will use Tea Commerce's addUniqueOrderLine JavaScript method. This way the shirt can be added many times, with a different setup and quantity each time.
3. The settings of the product (Size, fabric, color etc.) could be created in any number of ways. All that is needed is to add the value of the customers choices to the orderline using updateUniqueOrderLineProperty JavaScript method. E.g. color = "red" or fabric = "wool". All you would have to do then is to write the choices on the order confirmation and the email.
3.a. One option would be to make the choices as subnodes to the "shirt" product node. This way you could easily xslt yourself out of presenting the choises in the order they are sorted in, in the content tree.Would look something like this:
Shirt
Colors
Red
Blue
Fabric
Wool
Cotton
The "Shirt" node would be the product page. When the user then adds the product to the cart he would be taken to the "Colors" page where he would choose from the choices under that "Red" and "Blue". After choosing that he would be sent to the "Fabric" page and so on if there's more choices. The "Red", "Blue", "Wool" and so on can contain the small picture of the choice.
It will take a bit of xslt to do it. But all of it is pretty standard Umbraco setup. The Tea Commerce part will be very small and be centeret on the few updateUniqueOrderLineProperty calls on each step.
/Rune
Hi Rune,
Thank you very much. I Will try to implement the ideas you have given. This is roughly how I have thought to do it:
Please let me know if this would be a good way to accomplish my task. Can you also please tell me in more details how I can use addUniqueOrderLine and updateUniqueOrderLineProperty. I am not sure at this point how to exactly use these two methods. I understand what they do, but I am not sure when and where I should use these methods.
Mudasar
Hi Mudasar,
Sounds good, will be fun for you i recon. A few small advices:
1. "Custom shirt" should have it's own "Product" Document type. This way you will be able to give it some extra properties, without interfering with the "Page" doc type.
2. You might also want to create a specific doc type (e.g. Variant) for the fabric, color, size. Just one that can be used by all. This way you will also be able to give them some special properties AND you can let the user only create "Variant" nodes under "Product" nodes. Makes it much easier for your customer to create products.
3. addUniqueOrderLine is just used instead of addOrderLine. In your case you should use it when the user starts creating his/her product.
4. updateUniqueOrderLineProperty will be used on each step of the product creation process. When the user selects "green" you will update the "color" property on the orderline. like this TeaCommerce.updateUniqueOrderLineProperty([orderLineId], "color", "green")
I hope that helps. Remember that when you are using updateUniqueOrderLineProperty you supply the orderLine id, which you will have to fetch from the order somehow. You will need a bit of JavaScripting for that part I think, as you will have to let the product creation steps know which orderline is currently being edited.
/Rune
Hi again Rune,
Yes, Its an exciting task and I am sure it will be fun. I now have some ideas of how to get it done. I will be working on this for some time now. Thank you very much for your help and advices. I really appreciate it. If or when I need further help, I will get back to this topic. I hope thats okay.
Mudasar
You are allways welcome to write more questions here, we're just glad to help. :)
Would you mark the correct answer in this topic for future reference. Makes it much easier for others, with the same problem to find a solution. Then you can create a new topic for your next question.
/Rune
is working on a reply...