As a compliment to my other blog post on using WooCommerce with Thrive Themes, I made a 10 minute screen casted video tutorial about how to setup WooCommerce and what the end result looks like.
This was made as a reply to a comment question on my previous blog post by Linda. Thank you Linda for posting your comment. I thank my readers for making my blog more useful for everybody by leaving valuable comments.
Important Timestamps
00:00 – Short intro
00:21 – Installing and setup WooCommerce
00:43 – Setup Wizard: Store Setup
01:39 – Setup Wizard: Shipping
01:39 – Setup Wizard: Shipping
02:25 – Setup Wizard: Jetpack
03:44 – Creating the first (digital) product
04:19 – Adding downloadable files for the first digital product
06:14 – Adding first physical product
08:02 – Look at the shop with 2 products
08:17 – Don’t use WooCommerce product gallery with Thrive Themes (example of how its broken)
09:11 – Pages auto-generated by WooCommerce on setup
09:29 – Setup your new shop as your website home page
Important Note
While WooCommerce is clearly the major market share holder for all e-commerce sites on the internet, they can be “too much” for smaller use cases.
If you can use hosted platforms like Gumroad, Sendowl or WooCommerce alternative plugins like ‘Easy digital downloads’, please do that. They are often way easier to setup, configure and use.
There are plenty of use cases where people make 5 to 6 figure sales just using Gumroad for example.
Drop your comments below if you have questions or thoughts.
I write this so that it can help another person save hours of time, money and sleep before considering AccessAlly with WooCommerce and Drip combo for their membership site. I do this as a last resort after spending months of development time plus precious money buying all the plugins needed for this project and getting no support from these platforms.
[Update 1: AccessAlly’s founder Nathalie Lussier replied positively to my share of this article on Membership Mastermind facebook group. I am thankful to TheMembershipGuys for helping me use their group to voice my concerns. I have included further updates below.]
For a membership site development project recently, my team was moving a “custom-made non WordPress membership site” to “WordPress membership site using AccessAlly”
The client was already using WorldPay for their existing membership site subscriptions – one of the worst outdated payment processors in the world in my opinion.
We had built a lead-generation site for the same client that integrated with Drip and were very happy with the Drip platform. So we wanted a membership platform that would work with Drip as well.
So finally we wanted a membership software platform that can work with Drip and work with WorldPay’s FuturePay platform. There is literally no membership plugin software that supports WorldPay’s FuturePay out of the box.
[Update 2: Apparently aMember supports WorldPay out of the box according to a comment I received from the facebook group post. I verified on their website that they do. But we would have not chosen aMember because we really needed a tag based system like AccessAlly or Memberium as we wanted some custom features designed using tag automations]
And we found that WooCommerce had a plugin to accept payments from WorldPay’s FuturePay subscription system.
While we were considering various options for the membership website, the marketing head of the client’s company had heard of AccessAlly and was impressed. She wanted us to consider using it, as it seemed like the best option out there for their needs.
Extension – WooCommerce Subscriptions (199$ a year)
WooCommerce For Drip Extension (79$ a year)
WorldPay/FuturePay payment gateway for WooCommerce extension (79$ a year)
Smooth Start In the Beginning
At first things were reasonably smooth. AccessAlly’s setup was straight forward, and everything in AccessAlly was controlled through tags on Drip.
In the beginning of the purchase of their plugin, we had direct content with Robin, AccessAlly’s lead developer. She would answer our questions diligently and we felt great receiving support and strategic advice.
(You can click on images below to see full screenshots)
First reply from Robin, lead developer of AccessAlly
We start building the new membership site. Our plan was to finish the content, membership levels, individual products and then finally work on payment systems. The last step was to import their subscribers from their existing custom made membership site built on Django.
When we started to work on payments things started going bad.
How AccessAlly’s Support Didn’t Care After Onboarding Us
Now apparently “WooCommerce For Drip” plugin does not create a user in the Drip backend, unless they exclusively check a box on the final payment page which adds them to a drip campaign as well.
So if a user makes a WooCommerce Subscription purchase for a membership and accidentally forgets to check a box (which cannot be made mandatory), then even after purchase they simply cannot login to AccessAlly. Simply because everything in AccessAlly is controlled through Drip and its tags. There was no record of the purchase on Drip, not even their email was added.
Disappointed after spending more than a month to build everything, we reached out to AccessAlly’s support. Only now, someone else answered when we reached out to Robin. To us it seemed it AccessAlly’s onboarding was great, and then they simply automated our support requests to some other developer (Erika) who said I needed to contact WooCommerce and they would help us out.
1st Email reply from Erika – AccessAlly Support Developer
WooCommerce Let Down and AccessAlly’s Unprofessional Support
I had to reach out to WooCommerce again, and the reply was a simple one line – “Users will not be added to Drip unless they check the box”. I explained them how we don’t need them added to any campaign, but they simply repeated the same answer.
Disappointed I went back to AccessAlly’s support. And this is what I received.
Erika’s second reply
Needless to say I felt abandoned. I persistently followed up. Simply because now they were simply playing blame games now.
Erika’s 3rd reply
My final email to Erika
What really bothered me is this – Erika’s reply says, “we can only make promises on what AccessAlly can do”. How is an article on their own website which clearly says it works with WooCommerce and Drip “not a promise”?
This was simply, for a lack of better word – STUPID and seems like their AVOIDANCE FROM TAKING RESPONSIBILITY.
Gets Even Worse
After all the let down, we had to hire a WordPress plugin developer to create a custom plugin patch to fill the gap of adding users to Drip after a purchase. This was never part of the budget and we had to take hit on the expenses after all the headache.
After a week or two passes by, we are almost near the completion of all contents and payments. We finally test the cancellation flow of WooCommerce Subscriptions.
Then we realized, there is no mention of this anywhere. If a customer cancels their subscription, while they stop paying, they will still be able to access everything on AccessAlly.
This is because none of the plugins AccessAlly’s article recommended even deal with cancellation flow. So no tags on Drip are removed, and hence AccessAlly lets users access membership content even after they stop paying.
THEN IT HIT ME, none of their knowledge base recommendations were tested by AccessAlly’s team, EVER or considered for real world usage. Because how can something as trivial as cancellation be not even thought of?
It was simply a way to sell. Because that seems like the only focus at least from where I stand.
How Do We Move Forward?
At the time of writing this, the only way to move forward seems to be hiring another developer again for the cancellation flow. Its going to cost a lot for custom development and we had never quoted this to the client because all these companies promise us out of the box behaviour.
It sucks that no one wants to take responsibility for the functionality and are simply keen to sell.
For instance, even after all of this, AccessAlly has not changed a word on their KB Article. (Update: Feb 6, 2021 – I noticed some traffic to this article. I went back to their KB article and happy that they are finally transparent about the limitations. I do feel good about pushing them to do that *wink*) This means more customers will be affected by their false article. Also I left an objective review on the specified WooCommerce Extension about its shortcomings and it was never approved by WooCommerce as they control the reviews on site.
[Update 3: Nathalie Lussier, AccessAlly’s founder promised to update their KB article about the reality of using it with WooCommerce and Drip, it was comforting to feel heard and getting assurance from their founder that they care]
Reply on Facebook group by Nathalie Lussier
Concluding thoughts: While I am a user/developer of WordPress and its ecosystem, I am kinda starting to see why there are platforms like Shopify, Kajabi, Teachable, Squarespace etc which some people prefer to avoid a lot of headache with “plugins hell”. At least with these platform, while they do make you dependent on them, they take responsibility.
Update (28th Oct 2020): This article is outdated and Thrive Themes apparently supports Woo-commerce way more than it used to. Check the video by Doug at convology.com below for the full-integration. I’ve stopped focusing on Thrive theme builder and Thrive Architect and switched to Elementor for theme building + page builder for various reasons. I still recommend Thrive leads, Thrive Ultimatum.
You can. But I don’t recommend it. Not if, the main purpose of your site is to be an e-commerce website.
I will explain you the details.
Over the years, I have served a huge array of clients with a variety of requests related to Thrive themes. They ask for customisation, mobile optimisation, making child themes, and also integrating woocommerce with thrive themes.
After working on two such woocommerce related projects, I started to pass on tasks like that. Even though it is possible, its a HUGE amount of work to get even of basics of it looking good, usable and right.
It needs a huge amount of customisation in terms of CSS. And then you might also need to child theme and modify the woocommerce PHP files.
So what do I recommend?
First, ask yourself
Are you trying to setup a full fledged ecommerce site?
Are your products going to have multiple screenshots, a full page description with images and sections?
Do you need an extensive cart modification functionality?
Do you expect simple basic UI elements of every ecommerce store to make the user experience easy? E.g. Like wanting a + and – button on your # of items box. (See this demo woocommerce store by thrive themes, and notice how the product page doesn’t have a button to increase count of the product)
If you answered yes to questions above, then don’t use thrive themes for an ecommerce store. Simple.
But if you want to sell a courses, informational products etc which don’t require extensive cart modification functionality, you will do just fine with Thrive Themes.
Thrive themes wasn’t built specially for running an ecommerce store using woocommerce. Its built for lead generation, conversion, content, courses etc.
So I suggest setup a subdomain. If your domain is skreechers.com, then setup a store.skreechers.com. Make it a separate wordpress install, get a flexible super-fast WooCommerce theme that supports WooCommerce out of the box. (As of updating this article, Its got 73000+ sales with 4.8 stars avg. Flatsome theme is so good and popular that there are 3rd party WooCommerce plugin developers who support it)
The theme is 59$, but trust me you will save loads of time and banging your head against wall compared to trying to punch thrive themes to look good with WooCommerce. Also I have used Flatsome theme personally for a client’s website which continues to run fast and reliably long term over years.
Use the exact same fonts, logo and colours that you use on your thrive themes site, so that when the user switches between the store site and content/membership site, they get a seamless experience. This is important to not scare your users and provide a seamless brand experience.
But again…let me repeat this, *if* you are selling just few products, and you don’t really need a special product page, special cart experience etc. And all you need is for the user to click on “add to cart” from your sales page, see a checkout page and finish payment, then don’t bother to setup this special store subdomain.
I am a thrive themes consultant myself and been following the forums and company closely. Their roadmap doesn’t have any new WooCommerce features in the near future as of writing this post. Their support for WooCommerce was just to clear an objection that many users might have before buying their themes.
Leave a comment below if you have specific questions.
I made a 10 minute video tutorial on how to setup WooCommerce on Thrive Themes. You can see how the result looks along with my recommendations on who should and shouldn’t use it.