I would also be in favor of being able to define the delivery areas per vendor and not generally for the entire marketplace with all vendors.
I have the challenge that one vendor only needs delivery areas within one country, but another vendor needs delivery areas on zip code level.
Currently, it is not possible to implement both scenarios independently. As soon as a vendor requires areas with postal codes, other vendors must also implement this delivery, otherwise delivery is no longer possible.
I had already opened a ticket for this, where this was also confirmed to me.
This is something that we considered before. The main problems with “different rate areas for different vendors” are as follows:
It is a big technical change.
It will have a very negative effect on performance at checkout.
But there might be another way to solve the problem. If there were “parent” and “child” rate areas, than one vendor would be able to set different rates for country regions, while others would be able to set rates for the entire country.
The second approach may be included in the roadmap of 4.17.1 or another future version.
Ya, but most sellers on other platforms now use shipping services like Ship Station, Shippo, and ShippingEasy instead of rate areas. I really don’t see the majority of vendors really wanting to setup rate areas anymore. Vendors that join a marketplace often wish to use their shipping platform of choice. How about integrating Shipping platforms? CS-Cart still hasn’t worked closely with Ship Station to fix their plugin’s problems. CS-Cart’s Multi-vendor owners want to be able to have the features of Shopify in my opinion, or we can keep losing vendors to them.
Very excited for this. One issue for me as marketplace owner was that for new vendors it may be a little overwhelming if they were not familiar with CS-Cart. Having a custom to-do list (like most modern sites now have) is a great way of getting the vendor to update the most important information and to give them a helping hand when they first login.
In the coming weeks, we’ll also release a public beta of 4.16.1, which anyone will be able to try on a test installation. It is mainly intended for our partners and third-party developers, to give them time to adapt their add-ons. But it’ll also be available to anyone curious enough to spend time on fiddling with a temporary test instance of the store or marketplace.
We’d love to release 4.16.1 as soon as possible. But Christmas isn’t the best time to upgrade — our clients focus on sales in that period. The extra time also allows us to make the most of the upcoming features, like editable onboarding and menus in the vendor panel.
How will Stripe Checkout work for multi-vendor checkouts? Will there still be the availability to have in-store pickup? Will the shopper be able to select a shipping method for each vendor?
On the CS-Cart side, your customer enters the data relevant to the shipping: contact info and address. This is necessary because shipping rates are still calculated through CS-Cart.
On the Stripe Checkout page, customer would enter the payment data (either credit card info, or something else, depending on their preferred payment option).
Hello! I’m expecting end of January, with a few weeks as we make the upgrades available to everyone. Initially after release, upgrades are available in limited batches.
We expect the first upgrades to hit the Upgrade Center before the end of January (on the “first downloaded, first upgraded” basis). After that, it usually takes up to a few weeks before we lift the restrictions and make the upgrades available to everyone.
So, although I don’t have an exact date for “completely available”, a safe bet would be “some time in February”. Please note that to see the upgrade to 4.16.1, your store will need to be at version 4.15.2 already.
I will contact my developers to get in touch with you.
We want to upgrade as soon as possible.
We had been waiting for V5, but this will to be to complicated for our shop and we have a lot of made plugins. So we decided to keep on this version. But now because of the waiting we are a bit out of date.
This is in relation to the use of Stripes OWN checkout PAGE (user gets rerouted to that page and puts in details)
I understand stripe checkout will work for MV users but its specifically around the user interface and user experience that I’m asking about.
Ideally, we would like to use Stripes OWN checkout page as they have done a lot of work to optimise for conversion whereas cs-cart’s native checkout page is generally not an ideal user experience
That won’t be covered in CS-Cart 4.16.1. Our main goal with Stripe Checkout for 4.16.1 was to increase the number of local payment methods, and the feeling of added safety when you see a familiar payment option and their interface.
I’m thinking January 31st. That’s when you can expect a release announcement here at the forum, and a usual blog post covering most important changes. Right now, we’re doing some final pre-release testing and prepping that post
