August 11, 2015 at 4:30 pm 66515
|Nayem||Is it possible to assign additional shippings costs for variations of a product? For example I have a painting, framed and unframed. Obviously there is a huge difference in cost of shipping those items but from what I can see I can't assign additional cost to the framed option. In the actual woo commerce per product shipping plugin there seems to be an option for this but not in the dokan version. Is this correct or am I missing something?|
August 12, 2015 at 6:32 pm 66754
In the variation product you can add shipping class. You have to create shipping class and then you can assign that in the variation. But in the variation option you can not add additional cost.
August 13, 2015 at 10:24 pm 66982
This is a massive limitation for me. My sellers can’t charge more for shipping a framed painting than they do shipping a rolled up print, seems ridiculous.
Is this on the development list at all? It seems strange that woo commerce per product shipping offers it but Dokans version does not.
August 16, 2015 at 10:30 am 67229
If you want to set a different rate for a single product or any specific product then you can override the default shipping rate from product edit->shipping->override default shipping. But in the variation you can not set extra shipping rate. You have to use the parent shipping rate for the product or shipping class.
August 17, 2015 at 5:39 pm 67644
Is there any plan by you guys to change this in the near future so that the seller will have the ability to change the shipping rate for each variation (either charge additional or a per product amount) like there is in the actual Woo Commerce plugin?
Overriding the default shipping rate per product is useless when the variations of that product have significantly different shipping costs (again think of a painting being offered for sale as framed or unframed – they are completely different weights).
I’m not sure about other people but for me this is nearly a deal breaker in terms of using Dokan for my site which is incredibly disappointing because by and large its an awesome plugin and this seems like a reasonably easy change.
August 17, 2015 at 7:08 pm 67683
We will think about it and also I will forward this feature request to our team.
August 18, 2015 at 9:25 pm 67867
Thanks Nayem, really appreciate it. Can you please let me know what the developers says in terms of if / when this can be updated?
August 19, 2015 at 11:00 am 67957
We will think about it. We can not implement any feature which is not requested by so many clients. If this feature is possible or if there is any way to implement similar feature then we will try to do that.