@jessie_risch That's a drastic decline. from what I've seen with other WooCommerce product owners, that is not the case.
My guess, are you shifting away from the dropshipping niche?
English
Youssef
101 posts
Youssef
@mryoubou
Developer, designer, & entrepreneur. Building powerful WooCommerce plugins @CartseraHQ
Katılım Nisan 2018
35 Takip Edilen70 Takipçiler
#WoosaScoop - €14k MRR
That is how much our WooCommerce plugins generate today.
2023: €50k
2024: €35k
2026: €14k
Because of this, I decided to do something outrageous. Can you already guess?
English
@jessie_risch you're right, it's something I'm working on to improve at
English
@mryoubou Honestly? You’re thinking as a developer not as a marketer or customer succes agent. Getting the customer in, is the hardest. Lifetime will help with that and you can probably upsell them either way with another plugin or service.
English
While everyone is talking about WordPress 7.0, let's talk about lifetime deals.
I recently removed the lifetime plan from Cartsera. I don't think it's a sustainable business model, especially for products that need continuous updates and support.
But since almost everyone still does LTDs, you feel kinda forced to do it too.
I'm curious to know, do we keep going like this, or is it time for a change?
English
@PineDigitalCo I thought about a Facebook group as it's very common among other product owners, for now I don't have enough users to create it, maybe later when it feel right to it
English
Permanently, but that's also because of my particular audience with this specific plugin.
Have you thought about a community around your products so it's not necessarily just you helping out? Customers helping other customers. Another benefit is you can often times answer a question once, and support many.
English
below 20% is actually good.
I did dig deeper on this topic, I found some some interesting similar ones here on X from years ago, nothing has changed since then. I think it's how it is in WP world and I'm here over thinking it. I'll probably revert this change and see how it goes before making any final decision.
English
All time (but I only have it for the last 2.5 years of 6): 7.5%
Currently active licenses: 25% (but of course, the number of lifetime licenses is the same as in the first percentage)
I would need to do some math on the percentage of all licenses bought (including active or expired) since I started doing lifetime, but I would say around 15%.
English
@MarcoAlmeidaPT @PineDigitalCo what percentage of customers end up choosing lifetime vs yearly?
English
@PineDigitalCo @mryoubou I have a lifetime deal for all my plugins at 3.75x the price of the annual price. Most new WooCommerce shops (what my plugins are for) are not around more than that, or if they do, they’ll probably won’t ask for much support after 4 years.
English
@PineDigitalCo Yes, but thinking long term, I don't want to end up supporting a plugin where the majority are lifetime users.
do you plan to offer the LTD for a limited time or permanently?
English
@mryoubou I don't see a problem with it, especially for new/fairly new launches. Just launched a plugin myself and added a lifetime option at 3x the annual price.
It looks like your product falls in the fairly new category.?
English
@gridpane raised a good point.
When you build a WooCommerce store, do you actually test it for these scenarios or just build, launch and hope for the best?
Youssef@mryoubou
That wasn't my point of this post, but I get where you're coming from. Here are some k6 results from my testing. Load test ran for 14 minutes with mixed guest and logged-in checkout flows, peaking at 12 concurrent active VUs and completing 547 full checkout journeys. For a 1GB RAM/CPU VPS with no object caching, I'm happy with the results. For now this is more than enough for me, and if needed I can scale the server to handle heavier load. This is why I self-host, specifically to have more control and avoid the limitations and bloat that come with most legacy "one size fits all" hosting stacks. Isn't this exactly what you're solving at Gridpane?
English
That wasn't my point of this post, but I get where you're coming from.
Here are some k6 results from my testing. Load test ran for 14 minutes with mixed guest and logged-in checkout flows, peaking at 12 concurrent active VUs and completing 547 full checkout journeys.
For a 1GB RAM/CPU VPS with no object caching, I'm happy with the results. For now this is more than enough for me, and if needed I can scale the server to handle heavier load.
This is why I self-host, specifically to have more control and avoid the limitations and bloat that come with most legacy "one size fits all" hosting stacks.
Isn't this exactly what you're solving at Gridpane?
English
@mryoubou I didn't actually miss the point.
Do you actually know the point at which your site will fall over on your current hosting environment?
How many concurrent checkouts you can handle?
If you don't know this, and almost no one does, you really gotta fix that.
English
@ciorici Not a good idea to mock a user either. They have paid attention and time to your product.
English
#ShopifyDiary 372: Very proud of my marketing specialist Leo for representing @Barn2Plugins at @DsMatie's Wide Event yesterday.
The best bit was when he was pitching Barn2 Bundles & Bulk Discounts to potential partners. He opened the app listing page and one person commented that we have the Built for Shopify badge. We genuinely had no idea that it had finally been granted after multiple rounds of feedback 🎉🏆
At today's marketing meeting, we're going to discuss whether it's finally time to remove the free tier and properly start monetizing the app.
English
@gridpane I think you missed the point. Cart and checkout are fast, no caching is used page or object on them.
I looked at gridpane, we use similar stack, I was about to roast you haha if I found you using apache like other bloated hosting. x.com/mryoubou/statu…
Youssef@mryoubou
@scottbuscemi @natmiletic here you go
English
@mryoubou So can we load test your Woo checkouts?
You can’t pay your bills with those hundos.
English
@mryoubou @natmiletic Now do the cart page with an item in the cart
English
there's repetitive work we have to do most of the time, that makes editing variations a pain in the a**.
Adding a popup to prefill values at the time of generation and apply them to all variations would help a lot
Another example is downloadable files, most of the time it's one file but you have to add it to every variation, when all that changes is the price or something else.
A checkbox to set the files once, like a simple product, and hide that field across all variations would be very helpful
English
Currently, when you generate variations in @WooCommerce it's all or nothing. You can either create each one manually, or generate all possible combinations in batches of 50 (🫠).
@poligilad00 and I are exploring this idea: what if you could choose which combinations to create when generating?
#radicalspeedmonth
English
What I like about WordPress is if a hosting keeps increasing their prices like this, I can simply export my website and move it somewhere else
Webflow@webflow
We're simplifying our plans, and updating pricing to match what modern marketing teams need. The web is changing faster than ever, and AI is making it easier to build, manage, and grow content-rich sites. We've heard from customers that they need better ways to scale, so today we're announcing updates that do three things: - Simpler plans and updated pricing. We’re introducing a new Premium Site plan by combining the CMS and Business plans. As part of this, pricing and limits are updating across all paid Site plans. - A plan for fast-growing teams. Introducing the Team plan, an all-in-one offering for teams that have outgrown self-serve but aren't ready for Enterprise. It unlocks capabilities previously unavailable on self-serve, like AEO agents, page branching, single-page publishing, publishing workflows, and so much more. - AI as the foundation. We’re introducing AI credits and including them in every Workspace plan, so all customers have built-in access to the latest AI features they need. To learn more about these updates, visit our blog: wfl.io/48Stauj
English
@jamesckemp no problem! yes, that would help alot, variations can get out of control easily for products with alot of options
English
@mryoubou Thanks! I’ve been thinking about it specifically for variations and I think it would help in multiple places
English
I faced that problem with fontsera.com years ago. server load would reached 100% on certain pages/actions and timed out.
I was using variable products at the time, 8 variations per product, multiply that by over 1000 products + thousands of attachments (images and fonts, sometimes one product can have over 20 fonts).
This bloated the post table, HPOS wasn't a thing back then. the only option was left with is to stop using variable products, I had to build a plugin similar to Product Add-Ons but for for pricing options and switched to simple products only + other optimization
this massively freed up the wp post table and solved the timeout issue. its been working fine since then.
English
@mryoubou Have you got any examples of times when products having their own tables would have improved perf? It’s something we’re strongly considering, so good examples help out the case forwards as it’s a big change!
English