Day 3 of release week and we are still shipping!
Today's update is for everyone selling digital products. We rebuilt the Amazon S3 integration from the ground up and added full native support for Cloudflare R2. Both are set up from a guided wizard right inside WordPress admin, no more editing config files and hoping it works.
Quick rundown of what is in 1.3.21:
- S3 Integration, reimagined. A proper three-step wizard: Credential β Bucket β Security. Browse your existing buckets, create new ones, set Block Public Access, and verify the connection. All from the admin.
- Cloudflare R2, fully native. R2 has its own driver, its own bucket tooling, and you can pick jurisdictions (APAC, EEUR, ENAM, WEUR, WNAM, OC, or Automatic) when you create a bucket. Zero egress fees on Cloudflare's network is a big deal if you sell large files.
- Two credential modes. Define keys in
wp-config.php(recommended, keeps credentials out of the database), or store them encrypted in the DB if you prefer UI-only setup. - Consistent storage interface. Whether you run S3, R2, or both, the mental model is the same. One provider list, toggles to enable or disable, edit settings without reconnecting.
Also in this release:
- Strengthened server-side price validation during PayPal checkout.
- Bunch of bug fixes. Bucket creation issues, S3 file deletion, a fatal error on checkout when a product reference was missing, SKU constraint issue on variations without SKUs, PDF template styling on Pro.
Read the full changelog with screenshots and developer docs: https://fluentcart.com/blog/fluentcart-1-3-21/
2 more releases dropping this week. Stay tuned π
For a client of mine we used Mollie, but SEPA was not activated (by Mollie) for some reason, so she added a Stripe account.
She has a few members that paid through Mollie with creditcard. What happens to their subscriptions when we disable Mollie on checkout?
i wonder if there is a setting like this
Hey everyone,
Iβve been following the discussions here for a while, and I feel like I need to get something off my chest regarding the constant requests for more third-party integrations.
First off, letβs remember what FluentCart actually is: a high-quality e-commerce framework. It provides us with a solid API and plenty of hooks, which means we have the freedom to connect almost anything we need. In my opinion, itβs not the core team's responsibility to build a native connection for every single niche product on the market. That task should fall on the third-party platforms themselves or on us as developers.
If youβre genuinely stuck because a specific endpoint or hook is missing, then by all means, submit a feature request! Thatβs how the framework improves for everyone. But demanding built-in support for services that only a tiny fraction of users will ever need just leads to one thing: bloat.
The whole mission of FluentCart is to stay lean and fast. We should want a system that focuses on core e-commerce functions. Things that actually drive conversions and support a healthy business, rather than a platform cluttered with bells and whistles that most of us don't use.
Letβs appreciate the lean architecture we have and focus on building great things with the tools already provided.
Just my two cents!
Are there any plans to add municipal tax rates for US users? Or perhaps a way to at least upload a CSV?
Day 2 of release week π and this is a big one.
Been working on this one quietly for a while, and we finally shipped it today.
We built a one-click migrator that moves your entire EDD store into FluentCart. Products, orders, customers, subscriptions, licenses, coupons, tax rates. All of it. In one run.
And yes, your subscriptions will keep running. This was the scariest part for us to build and honestly the part I am most proud of. Your existing Stripe and PayPal subscriptions keep billing your customers on schedule right after migration. No re-authorization, no awkward emails to customers, no payment hiccups. The next renewal just happens like nothing changed.
A few other things worth mentioning:
- Zero downtime for software license customers. If you sell plugins or themes, your customers' sites stay active through the whole thing. Nothing for them to reactivate.
- Fully resumable. Server times out, browser closes, connection drops. Does not matter. Reopen and it picks up right where it stopped.
- Built-in validation. Every order gets checked before it gets written. Bad data never makes it in.
- WP-CLI support for larger stores that want to run it from the terminal.
Designed so you can run it on staging first, review, reset, run again, and only move to production when you are happy with it. That is how we use it internally too.
This is just the start. WooCommerce and SureCart migrators are already cooking, coming soon.
If you have been waiting for the right moment to leave EDD, this is it.
Full write-up with all the details, what gets migrated, what does not, and how to run it: https://fluentcart.com/blog/edd-migration-to-fluent-cart/
I am surprised that you have not integrated with Printful or Printify or even the actual shipping companies to get accurate pricing. This product is so good, but missing the most important connections to help it stand out above all others. So close, but yet so far away, and leaving people wondering, is this just good for selling digital products, as any physical product is manually processed.
Another release is out today, and this is a big one for stores selling physical products.
We finally shipped proper packaging support. This is the base we needed before we can build accurate shipping rate calculations and carrier integrations on top. Been wanting to get this in for a while, honestly.
The variation editor also got a full redesign. The old side panel was getting too crowded, especially once you add subscriptions with trials, setup fees, inventory, and now packaging fields too. It needed a proper rethink.
Here is what is new in 1.3.19:
- Packaging Support for Physical Products. New Packages screen at Settings β Shipping β Packages. You can create reusable package profiles (Box, Envelope, Soft Package) with length, width, height, unit, and empty weight. Assign them per variation and the data goes straight into the order. This is what rate calculators need to give you proper quotes.
- Redesigned Variation Editor. A new modal with two columns. Variations list on the left, the selected variation on the right, with clean collapsible sections for Pricing, Inventory, SKU, and Shipping. Simple edits stay simple, and complex variations finally get room to breathe.
- Lots of internal improvements.
Plus a fix for price input fields that were showing values in the wrong format, and another fix for saved views conflicting with active filters in the product list.
Full release notes with screenshots: https://fluentcart.com/blog/fluent-cart-1-3-19/
We may have another awesome release this week, so stay tuned. Please leave a comment about this release, especially the new redesigned Variation Editor.
Hi everyone,
I'm running a membership platform on FluentCart + FluentCommunity + FluentCRM (migrated from Digistore24) and I've hit what I consider a critical gap in the post-purchase flow. I'd love to hear how others are dealing with this β and hopefully build enough community signal to get this addressed natively.
The problem
When "Create User Account Automatically after payment" is enabled, FluentCart silently creates a WordPress user β but there is no native email sent to the customer with their username or a way to set a password. The customer completes a purchase and then has no way to log in.
Why the obvious workarounds don't work cleanly
-
WordPress default new user notification β works, but fires for every registration site-wide, not just paying customers. Also looks generic and unbranded.
-
FluentCRM Automation with
{{contact.wp_password_reset_link}}β structurally broken for this use case, because the merge tag only resolves after Double Opt-in confirmation. Paying customers shouldn't be gated behind a marketing consent flow to access what they just bought. -
Custom WP Coder snippet on
fluent_cart/order_paidβ what I'm currently using. Works, but requires custom PHP and excludes non-developer store owners from running FluentCart in a production-ready state.
What I'd expect
A native "New Account Created" email in FluentCart β Settings β Email Notifications, triggered immediately after a new user account is created post-purchase, containing the username and a password setup link. Independent of any FluentCRM Double Opt-in status.
This is standard in WooCommerce, SureCart, ThriveCart, EDD β basically every comparable platform. For FluentCart to seriously compete in the membership / digital products space (which the FluentCommunity integration explicitly targets), this needs to be a native feature.
Questions to the community
- How are you handling this in your own setup?
- Has anyone built a more elegant workaround than the WP Coder approach?
- Has the dev team given any indication this is on the roadmap?
I've already raised this via support ticket and it's been logged as an improvement request, but I think it deserves more visibility. If you're running a membership site on this stack, please chime in β the more voices, the more likely we'll see this addressed soon.
Thanks,
Philipp
chart.tech
How can i make this.. example. People register an account on wordpress sign-up or fluent form. And need to pay with fluent cart first. Before acc created. If the user not pay. The acc will be not created automatically

