Fluent Cart Feedback: Smarter Checkout Field Controls, Tax ID Flexibility, Renewal Reminders, Migration Guides & EU E-In
Hey team and colleagues! π
First of all - amazing progress with FluentCart lately, especially the auto-geolocation feature and how the EU VAT module now appears automatically for EU users. This is a huge step forward in compliance and user experience.
However, after several rounds of real-world testing, Iβve identified a few key areas that could greatly improve the checkout, account, invoicing, and documentation systems - especially for businesses operating globally and under strict legal frameworks (EU, UK, US, etc.).
Hereβs a structured summary of the main points π
1οΈβ£ TAX ID should be an optional, configurable checkout field
Currently, when a user is auto-geolocated, the βEU VATβ field appears β which is great β but thereβs no way to control when or if this field should appear.
This causes both compliance and UX issues:
- For B2C, collecting a Tax ID can be unnecessary or even non-compliant.
- For B2B or high-ticket B2C, collecting a Tax ID is mandatory for proper invoicing.
π‘ Suggested solution:
Add βTax IDβ as a standard field in Settings β Checkout Fields, allowing admins to enable/disable it globally (and later per checkout form).
This field should accept multiple formats β e.g., EU VAT, UK VAT, AU ABN, CA GST, or βOtherβ β so that businesses can adapt to different tax regions.
2οΈβ£ Users should be able to manage their Tax ID and subscriptions in the Account area
Currently, customers can only edit basic data (name, email, payment methods) β but not their Tax ID.
This becomes problematic when a user requests an invoice after purchase and didnβt provide their tax information during checkout.
Manual work= +costs
π‘ Suggested solution:
Add an editable Tax ID field inside My Account β Profile, so users can update billing data anytime.
In addition, as several users already mentioned, subscription management must meet legal standards:
- Users must be able to cancel subscriptions directly from their account dashboard β this is a legal obligation in many jurisdictions, especially across the EU.
- They must also receive renewal reminder emails before any automatic renewal takes place.
These reminders are legally mandatory in many regions (EU, UK, and parts of the US) and should be configurable in Email Notifications with flexible timing options (e.g., 3, 7, 14, or 30 days before renewal), to ensure compliance with local laws.
Any gap here, can result in problematic liabilities in many states worldwide. Fines, and not just refunds.
3οΈβ£ Checkout and Receipts: VAT labeling improvements
EU VAT calculation works so nicely (π), but the display could be more precise.
Currently, the system only shows βStandard Taxβ or βReduced Taxβ, without country or rate info.
π‘ Suggested solution:
Show VAT info in the following format:
- ES VAT (21%)
- FR VAT (20%)
- DE VAT (19%), etc.
Also, replace βTax Estimateβ with βTaxβ β invoices and receipts must show definitive tax details, not estimates.
β The βReverse Chargeβ mention is already working perfectly. Excellent implementation there!
4οΈβ£ Product & Checkout Templates
We urgently need layout templates for product and checkout pages.
When creating templates with Thrive Theme Builder (and similar tools), the checkout layout often breaks β with incorrect padding, dropdown misalignments, and layout conflicts.
π‘ Suggested solution:
Add built-in Template options for FluentCart pages (similar to what FluentCommunity already provides).
This would prevent styling issues and ensure visual consistency across builders.
5οΈβ£ Migration Guides & Manual Subscription Creation
Right now, many users are in a stand-by situation, waiting for official migration paths or documentation to move from other systems.
Time is precious here with this, due to what I am going to mention on point 6.
π‘ Suggested solution:
Provide Migration Guides or at least manual instructions on:
- How to migrate from other carts (SureCart, WooCommerce, etc.).
- How to manually create or import subscriptions, for those using external subscription management tools or accounting systems.
Even a short, clear tutorial would help many businesses transition confidently into FluentCart instead of waiting indefinitely.
6οΈβ£ EU E-Invoicing & Compliance Roadmap
This is one of the most strategic and time-sensitive topics for the coming months.
For us and many others in EU, something that must be addressed prior to 2026, and that could actually cause strong vinculations with other softwares due to legal compliance.
As already discussed in several threads, the EU E-Invoicing and live verification Framework is becoming mandatory across Europe β with specific deadlines in each country.
For instance, in Spain, the first phase (for invoicing companies) started in July 2025 (and past years too), and SMEs must comply by January 2026, followed by freelancers in July 2026.
This means that all platforms claiming to generate invoices will be legally required to connect directly to certified e-invoicing systems like *VeriFactu (Spain), Peppol (EU-wide)**, or equivalent national gateways.
After checking this with their teams, I have to say that have make this pretty simple: just a toggle, and you're done with your EU obligations.
π‘ Suggested discussion:
It would be incredibly helpful to know whether FluentCart plans to adapt to this new framework β or to allow integration with such systems.
The deadline, I know, is quite short. But we are receiving tons of questions regarding "which software should we use". And sadly, in EU, there are big actors. And any custom solution incurs on a serious probability of not complying. Basically, because it's almost compulsory to create your own invoicing software if you want to comply with verification requisites by your own.
As Iβve mentioned in the community before, major EU invoicing companies and tax software providers (those already handling OSS, VAT MOSS, and cross-border compliance) have started adding cart/checkout functions directly inside their platforms.
This is creating a significant competitive shift: many SMEs and freelancers β now facing mandatory e-invoicing β are starting to migrate their entire checkout process to accounting platforms that can generate and transmit invoices in real time, instead of using separate cart systems like FluentCart.
The legal landscape is also pushing in that direction:
- Non-compliance penalties can reach β¬10,000ββ¬50,000+.
- There are few affordable alternatives for small businesses to remain compliant.
- Most βbridgingβ solutions rely on API connections between separate systems (cart β invoicing β tax authority), which adds complexity and risk.
This is why *integration with official e-invoicing channels (like VeriFactu or Peppol)* could make FluentCart the first* cart system in WordPress truly compliant with EU legal invoicing standards β and a clear winner in the upcoming regulatory wave.
Summary
β
Add configurable Tax ID checkout field.
β
Allow users to edit Tax ID and manage subscriptions in their account.
β
Include renewal reminder emails with flexible scheduling.
β
Show precise VAT country and rate (no βestimateβ).
β
Add product & checkout templates to prevent layout conflicts.
β
Publish migration guides and manual subscription setup instructions.
β
Start discussion and roadmap for *EU invoice tech format requirements and e-invoicing (VeriFactu, Peppol, etc.) integration.
β
Ensure subscription cancellation** is available from user dashboards.
These enhancements would make FluentCart not only compliant but future-proof, setting a new standard for EU-ready checkout and invoicing in WordPress.
Woo is facing the same problem, and for what I am seeing, most users are just deciding to sync with big SaaS for this. Or create mu plugins or custom solutions (with big investments here).
Thanks again for your incredible work and commitment to improving the ecosystem.
Hopefully we can start using FC soon!
cc: Shahjahan JewelΒ
#verifactu
I think the Fluent team underestimates the EU requirements for tax and accounting regulations in e-commerce.
AndrΓ© SalierΒ Compliance in general usually is a real issue. And this topic, itβs something where you need to have into account the big picture: not just EU VAT, but also the technical requirements for invoices + e-invoicing framework. The team made an incredible work with EU VAT, however there are 2 stages left that are simply needed if any EU merchant wants to be able to use FluentCart in the future.
Sadly, if platforms like FluentCart (and the wider open-source ecosystem) donβt provide native or easily pluggable connections to systems such as VERI*FACTU (Spain), Peppol (EU) or other national e-invoicing frameworks in the coming months, the reality is that private invoicing SaaS providers will completely dominate the market.
Why? Because solopreneurs and small businesses simply canβt afford months of custom development or dedicate internal resources to build and maintain these integrations on their own.
In practice, businesses are already facing a simple and very pragmatic decision:
- Use a cart plugin + pay separately for invoicing software + pay again for a connector to systems like VERI*FACTU.
- Or just pay for a single invoicing SaaS that already includes checkout, legally valid invoice generation, tax-authority connectivity, and full compliance guarantees.
The second option is winning every time β and large accounting software providers have understood this perfectly.
Because, as good as FluentCart may be, whatβs the point of having a transaction or invoice history if those invoices arenβt legally valid or connected to the tax authority that requires them?
Keeping a history of invalid invoices is not a feature β itβs a liability.
And sending automated receipts or invoices that donβt meet the strict formal criteria of e-invoicing laws creates even bigger risks.
Thatβs exactly why many EU clients who genuinely love FluentCartβs Reports Module or see its great potential, are now migrating to SaaS ecosystems β simply because they have no viable, compliant alternative.
And itβs rather ironic: tax authorities initially promised βpublic API connectionsβ or even an official open-source connector for third-party systems like FluentCart. Yet in the end, all they delivered was a digital certification form and a recommendation to subscribe to certified SaaS providers β some even subsidizing the first few months.
This situation creates a structural imbalance. Once a business enrolls in one of those certified invoicing programs, it also enters the technical verification framework β meaning that, under current rules, the company becomes obliged to remain within that program until December 31st of that fiscal year.
So unless the open-source community β including FluentCart β acts soon, hundreds of thousands of European users will spend all of 2026 tied to proprietary invoicing software. And once theyβre locked in, very few will risk switching back due to the compliance and data-migration complexities involved.
Itβs almost inevitable that, a few years from now, weβll see competition-law discussions around this dynamic.
Because right now, the reality in Europe is simple:
βEither you use one of the officially certified invoicing systems β or your invoices wonβt be valid and you will get fined.β
Meanwhile, those same SaaS providers now offer embedded checkout widgets, legally valid invoice views, direct data transfer to tax authorities and accountants, and even secure 5-year storage β all requirements under EU and national e-invoicing laws.
Quite a case indeedβ¦
Jorge de los ReyesΒ and for WooCommerce there is a certified plugin "Germanized", which means that hardly any customers will migrate from WooCommerce to FluentCard.
AndrΓ© SalierΒ Europeans are probably investing more time in compliance than in innovation and creation.
Such a pity tbh πββοΈ
Letβs see if the fluent team comes with a solution to this.
Otherwise, I also see too complicated that anyone in EU uses just a cart.
The tandem with Saas will be a thing sure! (like with Germanize for woo, or alikes).
But probably, many business will just stick with the SaaS and alΓviate the burden of customizing an external cart.
Missing such a great tool like FC. But at least, being able to focus on the business instead of all this invoicing hell that we all are yet to witness π«
Iβve experienced it before working in B2G, where a couple of years ago you could easily lose a morning drafting a proper invoice in their systems.
SaaS did a great job here with one-click compliance with this. I guess they with the proper care to this issue, this could also be a thing with FluentCart.
But, a serious legal analysis should be conducted prior to this because there are many edges here: like, the compulsory remittance of ID accreditation among others and how privacy is handled.
This could also be the cause of why many carts are just leaving this to this SaaS companies. And why also many multinationals are starting to switch theirs custom carts to this SaaS solutions that are fully integrated with the ERP, CRM and accountancy softwares.
We have created a peppol conform invoicing plugin for woocommerce. See https://peppolcommerce.eu
Our next version will integrate also with FluentCart and this integration is in the last testingphase and will be availlable in a few days
congrats Natascha VantuykomΒ ! π
Thatβs an impressive step forward β and genuinely exciting news for the ecosystem.
Itβll be fascinating to see, once the integration is fully live, how you position it against the growing competition from SaaS platforms β and also against those, like yourself, who have decided to build their own SIF (Invoicing System). Because, in the end, the challenge remains the same:
Either a Cart + extra cost for the compliance plugin,
or an all-in-one SaaS that already includes invoicing, accounting, and tax connectivity β backed by strong reputational trust from regulators and accountants alike.
Still, this could turn into a real game-changer if executed right. Iβm genuinely curious to see it in action soon. π
Also, please donβt hesitate to let me know if you plan to cover the Spanish VERI*FACTU system β the deadlineβs approaching fastβ¦ but who knows, maybe youβll make it before January! π«‘β₯οΈ
That being said, FluentCart β as a solution offering invoicing within the EU β should make this a true βone-clickβ feature, at least if it aims to compete head-to-head with SaaS or continue marketing itself in the EU as an invoicing-capable platform.
Again, itβll be interesting to see how third-party integrations handle the situation of a system showing βinvoicesβ in user history that are not legally compliant. πββοΈ
We are taking this feedback very seriously.
Ripon SarkarΒ thank you Ripon! β₯οΈ
you guys are the best!
