Hosting capable of managing Magento’s resources is important, but it only goes so far.
A badly written frontend can completely train-wreck site performance. There is plenty that an inexperienced (or uncaring) developer can do to make a site look pretty but load like a tortoise. The only fix is doing your homework before choosing a theme, or hiring someone to fix the poor decisions.
If Magento runs smoothly when you remove the theme, then that’s probably what you’ll need to do.
You guys forget that a lot of stock sites work this way (especially Photo sites).. Take any site (iStock, Dreamstime, Photobucket, etc..) – they use credits. So if i want to buy a picture i need 5 credits, but i can’t buy it with $5, because the minimum credit package that i can get is of 10 credits. So i have to pay $10 for a $5 image, but then, i’ll be left with 5 credits in my account to purchase more afterwards..
This business model is in place for absolutely almost all microstock sites in the world so i still don’t get it why you complain that much about it.. It’s normal to be this way because everyone does it and we are used to this pricing model!So GravityDept – your statement that this is not how commerce sites work is totally false, since this is how it works on stock sites!
I could argue that “credits” are equally stupid and confusing for customers. Pricing this way because “everyone does it in micro-stock” is downright foolish. It’s always simpler to charge one price. I said that’s how 99% of commerce works, and that’s true.
ThemeForest buyers are not the same as stock photo buyers. Nobody pops in and buys 15 different Magento themes for $90 each. They explore, make decisions, and pick one. I’d bet that the majority of ThemeForest buyers never make another purchase. Credits are an ill-fitted system for that type of interaction.
The ”$2 extra” or ”$2 off” is irrelevant. This is about understanding consumer behavior and pricing psychology. The pricing confusion probably costs more sales than Envato makes by earning an extra $0.66 on direct-purchases.
It doesn’t make any difference to me whether Envato charges $90 or $92. Just charge $91 flat. If the sale doesn’t happen because the credit pricing model is confusing, we both get $0.
Just because credits are normal for micro-stock doesn’t mean it’s at all suitable for other digital products. Don’t forget PhotoDune is still a new marketplace at Envato. I imagine the only reason credits were implemented before its time was because Envato knew requiring users to complete a payment transaction for every individual purpose would be murder.
What I’m saying is that having two prices based on credits or direct-buying is a poor, conversion-killing system for infrequent purchases (i.e. the majority of Envato’s marketplaces). A shopping cart with no-BS pricing would be faster and meet buyer expectations better.
It is BS, because it wastes the customer’s time.
In a different scenario you’ll see how ridiculous it is. You walk into a gas station:
- A pack of gum is $0.80.
- If you just want to buy the gum, it’s $0.80 + $0.20 fee.
- But if you deposit $1.00, the gum is actually $0.80 and we’ll hold the $0.20.
- No matter what, you’re paying $1.00 and not $0.80 today.
- It’s gum! Why is this so hard!
Just charge $1.00 up front or $0.90 — whatever gets your margin. Don’t make the customer play games and decipher the price. It’s really simple not to screw this up.
Envato should drop the BS. Having “two prices” for items is confusing to buyers. Don’t make them pay extra to not make a deposit, and don’t hold them hostage with deposits in arbitrary amounts.
Just set one price and charge it. That’s how 99% of commerce works. Simple.
I guarantee potential buyers have walked because they didn’t understand the pricing situation (or want to).
Changes to Envato’s proposal:
1. Let authors choose which support bullet points apply to each item.
2. This lets authors disable support terms for old items that they still want to sell, while informing the buyer that support is not included.
3. Conditions that are supported (green check marks) or not supported (red crosses) should be made very clear. Envato needs to make it very clear that the additional services offered by some authors are truly valuable, and that means making it clear which authors don’t do those things. This is basically punishment for them, but if that’s where Envato is heading it must be explicit.
4. Support should not include all item updates forever. This means very different things for graphics, HTML templates, WordPress themes, and Magento themes. It’s not a one-size fits all condition. That’s completely unsustainable, and needs to be addressed with a different pricing model. I’ve asked for this many times over the years, and am working on my own policy driven approach to the problem.
Suggestions for Envato
1. Pricing: From a buyer perspective, these changes will make me think support is included in the purchase price, but the pricing is dirt-cheap because it isn’t. If support becomes a feature Envato promotes then prices need to increase globally (not just WordPress).
Envato is still way underpriced compared to other marketplaces (especially certain categories with high development cost, i.e. Magento). It’s unfair to ask authors to “officially” support their items without giving them the option to receive a price that reflects the costs of giving that support “officially”.
2. Discoverability: The marketplace should be split then between supported items and unsupported items because this is a significant driver of value for authors. If all items are jumbled together and buyers (still) can’t effectively filter down using faceted navigation, then this just introduces another differentiation challenge for authors.
3. Separate Envato’s terms and my terms: If Envato wants to slap a boilerplate list of terms on every TF item, then most buyers will quickly learn to ignore it. Don’t mix the author’s custom terms and notes with this info because they need to be visible for each and every item.
4. Necessarily Envato’s terms will need to be broad (and therefore less applicable). The author’s custom information should be placed first on the support page, followed by how to contact the author, then Envato’s general notes.
5. I have never used the FAQs because the design sucks. I can’t re-order them, I can’t group them under headings, or write complex formatting within answers so it’s easier to read. It’s simply not useful to shove a shoeboxed list at a buyer. FAQs should probably be rewritten, axed, or at least de-prioritized as much as possible.
Anything Envato puts into place that applies globally is going to be incorrect for some percentage of authors. Support policies have been 100% the author’s decision until now. Envato needs to give us better tools for making our policies clear and consistent — not enforcing a global policy that suits Envato because it’s easier to implement.
This is not something that should go-live in one week from survey to launch.
Thanks Laranz! Will have to wait and see who the winners are…
Vote here: http://www.thenetawards.com/
The Net Awards recognise the best new designers, developers, entrepreneurs and agencies on the scene, honouring the most exciting new tools and technologies to see the light of day over the last 12 months.
Related, I’m nominated (Brendan Falkowski) for the “Brilliant Newcomer of the Year” category. I’d love it if the ThemeForest community could rally some votes for me.You can read about the nominees here: http://www.netmagazine.com/features/net-awards-2013-top-10-brilliant-newcomers
If you have to ask you shouldn’t be offering that service until you have experience building sites and using different platforms. The client is relying on you to understand what they don’t.
Magento Community is a self-hosted platform, and it’s a great platform if you want to work on the code yourself. If you’re talking about the SaaS version Magento Go, which is hosted, then yes there are monthly fees. But if you think $15/mo is expensive, you probably don’t have the resources to run an effective eCommerce site on any platform.
Web infrastructure is a cost of business. You’re either paying someone else to host the application or you’re hosting it yourself and paying for the server. If you want to save time, buy something that is designed specifically for eCommerce and that means starting with eCommerce platforms instead of plugins or the (shudder) PayPal API.