Selling your products wholesale — at a reduced bulk price to retailers — can be…
Some of you might have spotted a change to WooCommerce.com made last week, on Thursday to be precise. WooCommerce.com now requires a WordPress.com account to manage your purchases, tickets and subscriptions.
We believe this change brings many benefits, and are dedicated to improving the account management experience for developers.
The immediate benefits for you
WordPress.com logins already have many of the characteristics that we were planning to add. In short, security and convenience.
We’re always looking for ways of improving the security and protection of WooCommerce accounts because eCommerce has to be rock solid on that front (2FA authentication, for example).
We found that a lot of customers were using two accounts to access services from one company. To simplify that, we are centralizing on the WordPress.com login. Automattic has done this with previous acquisitions, like Polldaddy, for the same reasons. Now you can use only one login to access all Automattic services, including WooCommerce, Jetpack, VaultPress and more.
What’s the response been like?
So far, mostly good. We’ve had over 10,000 successful logins in the new system so far, and are tracking a total of ~150 conversations, pings and feedback from customers across Facebook, Twitter, and tickets. Over half of the 1% of users who opened tickets were confused between having a WordPress.com login vs. the login they use for their self-hosted WordPress install (the old .com vs. .org confusion that crops up sometimes).
We haven’t had a chance to talk to everyone so far, but a common theme was questions from people managing sites for several clients.
What if I’m one of the people managing multiple accounts?
This change has emphasized that the current WooCommerce system is not friendly to those with multi-client management in mind.
People have found workarounds for this, but none of these strategies are really ideal. Long-term, any changes we made to the login flow were always going to cause issues.
We had already re-prioritized a number of features on our roadmap to make life for developers managing dozens of client accounts much smoother, and hope to have something to be able to announce there soon.
If you’ve been particularly affected here, the specific tactics you should take will depend entirely on your approach to date. We encourage you to open a ticket for advice. And we encourage you to point out all of the advantages of WordPress.com accounts to your clients.
Share your experience with us
Have you made the switch over to WordPress.com log in? Here’s what Brad had to say.
Read original article at Source link >[wpseo_map width=”100%” height=”300″ zoom=”-1″ map_style=”roadmap” scrollable=”0″ draggable=”1″ show_route=”0″ show_state=”1″ show_url=”0″] [wpseo_address hide_address=”1″ show_state=”1″ show_country=”1″ show_phone=”1″ show_phone_2=”0″ show_fax=”0″ show_email=”1″ show_url=”1″ show_logo=”0″ show_opening_hours=”1″]