FluentCart feedback roundup: hands-on testing and migration questions
Over the last two months, especially during a hands-on staging assessment for migrating an existing EU store from SureCart, I have opened the following FluentCart discussions.
A few points have already been clarified or improved, notably reviews and email verification in 1.7.0. I am collecting everything in one place so the remaining questions and requests can be reviewed in context rather than scattered across several threads.
INVOICING AND EU READINESS
β’ Feature request: Proper credit notes / corrective invoices for refunded orders
https://community.wpmanageninja.com/portal/space/fluent-cart/post/feature-request-proper-credit-notes-c
β’ EU store migration: please clarify the current invoice document and numbering model
https://community.wpmanageninja.com/portal/space/fluent-cart/post/eu-store-migration-please-clarify-the
β’ Receipt vs Invoice is confusing: please clarify the workflow and templates
https://community.wpmanageninja.com/portal/space/fluent-cart/post/receipt-vs-invoice-is-confusing-please
β’ Potential Fiscal Compliance Risk: Test Orders Share and Consume the Live Invoice Sequence
https://community.wpmanageninja.com/portal/space/fluent-cart/post/potential-fiscal-compliance-risk-test
MIGRATION, CHECKOUT AND ACCOUNT EXPERIENCE
β’ SureCart β FluentCart migrator
https://community.wpmanageninja.com/portal/space/fluent-cart/post/surecart-fluentcart-migrator
β’ FluentCartβs autologin option
https://community.wpmanageninja.com/portal/space/fluent-cart/post/fluentcart-s-autologin-option
β’ Add a native option to hide decimals for whole-number prices
https://community.wpmanageninja.com/portal/space/fluent-cart/post/add-a-native-option-to-hide-decimals-for
β’ FluentCart translations may need a native-speaker review across all languages
https://community.wpmanageninja.com/portal/space/fluent-cart/post/heads-up-fluentcart-translations-may-ne
ECOSYSTEM AND GROWTH WORKFLOWS
β’ FluentForms + FluentCart integration
https://community.wpmanageninja.com/portal/space/fluent-cart/post/fluentforms-fluentcart-integration
β’ Native review requests with product-linked smart links (largely addressed by 1.7.0, which is great to see)
https://community.wpmanageninja.com/portal/space/fluent-cart/post/feature-request-native-review-requests
β’ Post-purchase upsells
https://community.wpmanageninja.com/portal/space/fluent-cart/post/when-will-we-get-post-purchase-upsells-i
β’ FluentCart shortcode for subscription upgrades
https://community.wpmanageninja.com/portal/space/fluent-cart/post/fluentcart-shortcode-for-subscription-up
POSITIVE DESIGN FEEDBACK
β’ Really impressed by FluentCartβs checkout and storefront design flexibility
https://community.wpmanageninja.com/portal/space/fluent-cart/post/really-impressed-by-fluentcart-s-checkou
This is constructive feedback from a real migration assessment. FluentCartβs performance, design flexibility and pace of development are impressive.
The main go/no-go questions for our EU production migration are now concentrated around the invoice-document model, separate test/live numbering, corrective invoices, and the predictable migration of historical orders and invoice references. I hope this index makes it easier to review, prioritise and respond without losing the wider context.
P.S. cc: Shahjahan Jewel Rasel Siddiqe
Thanks Jorge! Seems like we've really got our work cut out for us. π Really appreciate the time you took to go through all these posts and creating this repository. Development team will appreciate this direction as well.
A small note; FluentForms team is working diligently on the integration. As it's beyond the scope of FluentCart devs, we can't really provide a concrete timeline rn.
- Invoices: Our team started working on it and we are going to release them soon. we are skipping the credit note as we don't have store credit features, so it's a direct refund receipt.
- Test order should be done on staging or if in production, should be deleted before go live. To handle test order in production + invoice number together will create tons of technical complexity which I want to avoid.
- SureCart β FluentCart migrator => team is working, we need a volunteer who can give us access and run our scripts as those data seats in their saas service and we don't have any live store to test.
- FluentCartβs autologin option -> only happens on the first order and account creation at that flow. you can disable now in the latest version.
- FluentCart translations -> Translation project is handled by WP ORG project. Please contribute here: https://translate.wordpress.org/projects/wp-plugins/fluent-cart/
- Others: Noted
Thanks again for all the feedback. This is how we can build the most optmized ecom solution :)
Shahjahan JewelΒ Rasel Siddiqe
Thanks for the thoughtful replies. Great to hear that invoice work is underway, and thanks, Rasel, for the FluentForms update.
- Corrective invoices / credit notes: I don't mean store credit or a customer wallet. I mean the tax document correcting an already issued invoice after a full or partial refund. This is not Spain-only: the EU VAT Directive treats a document that amends and specifically refers to the original invoice as an invoice, and the European Commission explicitly discusses credit/debit notes (EU invoicing guidance). National numbering rules differ: Spain requires a separate series for corrective invoices (Articles 6 and 15), while Ireland requires a unique credit-note number (Revenue guidance). So a configurable corrective-invoice/credit-note document, linked to the original and adjusting the tax amounts, seems important for EU stores. A payment refund receipt alone does not solve this. Could this be included in the upcoming invoice work, or exposed through a documented extension point?
- Test orders: Staging covers initial setup, but not testing a new checkout or workflow after a store is live. I appreciate the complexity. Is there a recommended way to test without consuming the official invoice sequence?
- Translations: Following Jose Luis DuronΒ suggestion, I reviewed the Spanish strings this morning and have just submitted six suggestions on WordPress.org, including targeted tax terminology corrections. They are awaiting editorial review.