this post could have also been titled:
How to lose a customer ~or~
How to screw up an ecommerce checkout page …on a site about ecommerce! 😉
Irony is when…
- A site built in WordPress doesn’t use WooCommerce to sell tickets. (or any other WordPress based platform for that matter)
- A site about ecommerce built in WordPress doesn’t have an SSL
- A site about ecommerce, built in WordPress, that doesn’t have an SSL wants me to put in my credit card information
- A site about ecommerce, built in WordPress, that doesn’t have an SSL, that wants me to put in my credit card information, loads in an iFrame that can’t even be centered.
…..did I miss anything else?
That screenshot was from a conference I was almost going to register for… http://www.practicalecommerce.com/ignite-register
I’m still a bit perplexed as to why the schedule doesn’t appear to have anything related to WooCommerce
Yes. I do see that the iFrame does indeed have an SSL running on it, but…
Why not simply keep things under “one umbrella” (if you will) and use WooCommerce? Add some Stripe love and you’re good-to-go! (given the dollar amount that they are going to process, if they’d email Stripe, they’d get a lower-than-3% rate, but …. shh, don’t tell anyone I told you that) ;-o
Why not simply snag an SSL from AlphaSSL.com for around $50? That’s just good practice!
Why not give the iFrame the width it needs? Someone obviously didn’t take the time to go through EventBee’s complete checkout process when they made the site. Your iFrame width needs to be at least 532px wide.
Oh DAAAAYUMMMM. I just looked at the checkout process on a mobile site: #fail
So, let’s run over some real numbers here based on 250 ticket sales:
- If they were to ditch EventBee, they’d be ditching EventBee’s Pricing as well. So that’s an immediate savings of $250 if they were on EventBee’s “Basic Plan” and a savings of $500 if they were on EventBee’s “Advanced Plan”
- Let’s assume half of all visitors are from mobile devices. The numbers aren’t exact, but… If they ditched EventBee, the checkout page would be responsive and look phenomenal on phones and tablets. Which of course, we all know would add to the ticket sales!!
- If they used WooCommerce, there would be all types of extensions and have much more control over tracking an analytic data! (I do NOT see any type of visitor analytics options on EventBee’s website)
- With a bit of history with Stripe, I’d ponder a guess to say that they could probably get Stripe down from 2.9% + .30 down to about 2.2% +.20 cents. (Yes, Stripe does indeed negotiate their prices! <—REMEMBER THAT!)
- So, if they are expecting ~250 people w/ an average ticket price of $500, their current fees would be:
- ($500 x 250 people x .029) + (250 people x .30) ~or~ $3,625 + $75 = $3,700
- Oh wait, we still need to add EventBee’s fee on top of that!! So, let’s say their EventBee’s fee is $1.50/ticket. That’s another $375 that we’ve got to add. Which brings the grand total to…..
So, had they simply used WooCommerce (free) and a Stripe Plugin (again, free) they would have saved at least $1,000 right off the top. The site would have had better tracking, and it’d be mobile friendly, and they’d convert more from a responsive checkout page.
Seriously folks… Who on earth makes $1000 an hour? Do you realize that, in a matter of one (maybe two) hours, I could put at least $1,000 back into their pocket?!?!? And who knows how much more they’d make if there was better tracking and conversions!
Folks, lemme help ‘ya here. If you’re wanting to sell tickets to an event and you’re running a WordPress site, it’s really simple and easy to not make these same mistakes. Ready?
There’s a lot more platforms that will help you sell tickets in your WordPress site.
What’s your favorite, and why?
[product_hero layout=”center” background_img=”https://bradgriffin.me/wp-content/uploads/2015/10/pillow-fight-cropped.png” width=”full” full_height=”0″ background_size=”cover” overlay_opacity=”0.25″ product_id=”3452″ parallax=”1″ description_text_color=”#eeeeee”]