FluentCart + Fluent Forms Integration
I was wondering, if it will be an integration with fluent forms so as we can make some conditionals, and charge using FluentCart instead of the Payments module of Fluent forms.
Just in the way as FluentBooking integrates with FluentForms: which is pretty nicely :)
Use case: we have not been able to use Fluent Forms Payments due to tax management issues on our side regarding settings and so. But, taking into account, Fluent Cart will have EU VAT management... I am pretty excited of the chance of having an integration just like the one with booking :)
Hey Jorge de los ReyesΒ
Being able to add Fluent Forms fields into Fluent Cart would be very helpful! It could be added for the purchase process, my account etc.
Paal Joachim RomdahlΒ absolutely!
I think both ways would be a handy integration!
Jorge de los ReyesΒ Yes. It sure would!
A native integration would let us keep everything in one flow with proper conditional logic and pre-filled checkout fields. Hope this gets prioritized soon! Shahjahan JewelΒ Is there a timeline for this integration?
was there ever some development regarding this?
Tomaz BacunΒ No news, sadly.
Jorge de los ReyesΒ help me out. I see your post from last year... are EU taxes available in fluentcart?
Vibe Code Yes, absolutely.
The location of the settings has changed a little since the first releases, but you should find everything under Settings β Tax β Rates.
If you completed the setup wizard and selected either the EU region or a specific EU member state, you'll see your selection there. Clicking on it will open the EU-specific tax settings, including OSS, non-OSS, thresholds, and the related options.
If you selected the EU region, all VAT rates for the different EU member states are automatically included and correctly named.
There was previously a bug where, if you selected only a single member state (for example, your own country -non OSS, just local), tax rates were generated incorrectly instead of using the proper predefined ones. However, I believe that issue has been fixed now.
Jorge de los ReyesΒ I don't see any EU country. It's not new installation.
Vibe CodeΒ what does appear there when youβre not using the Search bar? You should be seeing the default tax related region (that is editable).
Jorge de los ReyesΒ all countries except EU countries
Vibe CodeΒ search directly for EU. Not for individual EU member states (eg.: Spain). You should see there EU as a whole region.
Jorge de los ReyesΒ wow! thanks. works. what an awkward UX
Jorge de los ReyesΒ you are better than documentation! thank you sir. all sorted
Vibe Code well, technically, legally, and formally, itβs not really that awkward. But probably a notice of this could be helpful for the UX π .
My guess is, itβs probably due to the complexity of the technical VAT management, reverse charge, and especially the β¬10,000 OSS threshold. That needs a global calculation and reporting.
These features need to be handled as a whole because, once you exceed the threshold for cross-border B2C sales within the EU, you may need to regularize your tax position and migrate to the OSS scheme correctly. Something similar happens for B2B tax reporting.
And thatβs only one part of the challenge. There are many other country-specific requirements as well, including local tax authority reporting and verification, so yes: it will inevitably become legally more complex over time in the next years π
The good news is that the team is already working on these regional requirements (eg.: VERI*FACTU -taking advantage of the chance of you sharing Spain as an example) . Iβm optimistic that FluentCart will become a very strong solution for the European market, allowing businesses to manage payments and tax compliance within a single platform. That includes the mandatory e-invoicing and tax reporting systems that are gradually being introduced across EU member states, each with its own local requirements and integrations. And without the hassle of having to integrate third party softwares.
Iβll ask the team for that UX enhancement!
Vibe CodeΒ happy to help mate! Itβs easy to get lost in a small setting π . Letβs keep improving it!
Iβve already reported this as a UX engagement suggestion in case it could help in the future π