Yesterday's 1.6.5 added the new Appearance settings. Thanks to everyone who tried it and sent feedback. 1.6.6 is a small follow-up release that fixes the styling issues you reported, plus a few checkout fixes.
Better theme colour matching
- When you choose "Inherit from theme", FluentCart now uses your theme's colours on all block-based themes, plus Astra, Blocksy, Kadence, Divi, GeneratePress and Bricks.
- The settings preview now shows your theme's actual colours.
- Text and active states stay readable on every palette.
- These now use your storefront colours: shop filters, the price slider, carousels, toast notifications, the checkout tax field, the address modal buttons and Stripe's payment-method tabs.
- The primary button now has its own hover colour.
Checkout and Stripe fixes
- Fixed Apple Pay / wallet payments on some browsers. The wallet now opens directly from the Place Order click.
- If you close a Stripe QR payment window, the checkout button becomes usable again.
- Clicking Place Order twice quickly no longer starts a second order.
- Some translated state names that appear in more than one country now translate correctly.
Update from Dashboard → Updates as usual. If anything looks off with your theme, post a screenshot here and we'll look at it. 🙌
We sell online but also do tradeshows. With our Shopify, there is a POS solution. I hope that Fluent Cart will someday have a POS solution. Meanwhile, not sure how I will handle tradeshows. I guess I'll have to get a separate, third party payment solution and enter the sales manually.
Thank you so much for FluentCart 1.6.5. The date and timezone work has landed
in the release, the separator filter is there exactly as discussed, and the new
email confirmation flow is a real gift for stores that sell to guests. It is a
pleasure to translate a plugin that moves this fast. Three small things came up
while we were translating 1.6.5 into German, kept together here so they are
easy to read in one go.
7. A licence notice assembled from fragments, with a hardcoded date
app/Services/PluginManager/FluentLicensing.php:237 builds the expiry notice
by concatenating two translatable fragments with untranslatable English text:
'<p>Your ' . $plugin_title . ' ' . __('license has been', …)
. ' <b>' . __('expired at', …) . ' ' . gmdate('d M Y', …) . '</b>, Please 'Two things follow from that:
YourandPleaseare outside the catalogue, so the sentence stays half
English in every language. German word order also cannot be reached from
two fragments pinned in place, so the best a translator can do is a hybrid.- The date uses
gmdate('d M Y', …), so it is both a hardcoded pattern and
rendered in GMT rather than the store timezone. East of UTC an evening
expiry shows the previous day.
One __() call with placeholders would fix both, for example:
__('Your %1$s license expired at %2$s.', 'fluent-cart-pro')with the date formatted the way the rest of 1.6.4 does it.
8. on %s carries two meanings and has no msgctxt
The same msgid is used for two different things:
app/Helpers/Helper.phplines 1383 and 1406: the schedule anchor, "on
Friday", "on Aug 19"app/Models/Order.phpline 643: the tax base, "19 % on 69,00"
German needs a different word for each, am Freitag but auf 69,00, so one
translation is always wrong in one of the two places. _x() with a context
would solve it without touching the English text, the same fix as for Apply
and More.
9. Two spellings of "colour" in the new 1.6.5 colour settings
A small one, noticed while translating the storefront colour module in 1.6.5.
app/Services/Theme/ThemePalette.php uses British spelling in two strings,
line 816 and the plural entry at line 823:
The active theme does not publish a colour palette, …
%1$s provides %2$d palette colour. / … palette colours.The other 51 strings of the same feature use American spelling, including
ColorPalette.php and api/StoreSettings.php, which render on the same
screen. Nothing breaks, and translations are unaffected, but the English UI
shows both spellings side by side.
I own FluentCart but have not made the switch from Woo yet. I sell my own print books via my shop and am using the USPS Shipping Method plugin to show customers live USPS shipping rates, typically Media Mail for US customers. I am also able to purchase and print shipping labels at the live rate directly from my WP admin.
Please consider adding to FluentCart the ability to look up live rates and to purchase and print shipping labels at that rate.
I own FluentCart but have not made the switch from Woo yet. In addition to my own print and digital books, I use my shop to promote affiliate products, with shop items linking out to external sites via my referall links. It appears FluentCart does not have this capability. Please consider it!
Hi
We're currently migrating several clients sites from WooCommerce to FluentCart, and we have SKU and EAN codes for every single product variation. We noticed that while FluentCart has a SKU field per variation, there's no dedicated GTIN/UPC/EAN/ISBN field (WooCommerce has had this for years, right next to the SKU field in each variation).
This field is essential for us, and for most e-commerce stores, for several reasons:
- Google Shopping / Merchant Center – GTIN is required for most product categories in Shopping feeds; without it, listings get rejected or deprioritized.
- Marketplaces (Amazon, eBay, Cdiscount, etc.) – nearly all require a valid GTIN/EAN to list a product.
- Price comparison engines (Idealo, etc.) – use GTIN to match products across sellers.
- Ad platforms (Meta, TikTok Shop, Pinterest) – increasingly rely on GTIN for product feed validation and enrichment.
- Universal product identification – unlike SKU (internal/seller-specific), GTIN uniquely identifies the physical item across systems, avoiding duplicates and mismatches.
- Logistics/physical barcodes – EAN is typically the barcode printed on the product itself, needed for warehouse and supplier syncing.
This is a pretty standard e-commerce field, and its absence is currently a blocker for properly migrating and exporting our catalog.
..........
About GTIN and how it should be placed in FluentCart
.........
To be very clear GTIN is the international name for the code used to identify a product (Global Trade Item Number). Depending on the country, it may be referred to differently but GTIN is the standard name: GTIN = UPC = EAN = ISBN, etc.
So GTIN is a unique code for each product variant
This code is used to identify products across Google Shopping, Merchant center, price comparison websites, advertising platforms, shipping systems, and many other services.
It is essential to be able to assign one GTIN code to each variation of a product.
Otherwise it is impossible to use all those essential services for an Ecommerce site
This is an international standard used across ecommerce websites.
For example, in WooCommerce, as shown in the first screenshot attached, each product variation has 2 different codes: SKU, which is an internal inventory/tracking code. (so for an internal use) GTIN, which is the unique product identifier for each specific variation.
As you can see in the second screenshot attached, FluentCart would therefore need an additional GTIN field directly below the SKU field when editing each product variation.
Thanks for the great work on FluentCart otherwise 👍
Nicolas
I think about a year has passed since the launch, and a lot has certainly happened. In traditional B2C business involving physical goods, it seems there’s still quite a bit of “tinkering” needed for the German and European markets. Even though it was once said that this market is very important.
Is there any indication of whether and when this will change?
A lot of you told us about the default color customizations for your storefront. So in 1.6.5 you get to pick the colors.
There's a new Appearance tab under Store Settings. You can keep FluentCart's colors, let it inherit the palette from your theme (block themes, Astra, Kadence, GeneratePress and more), or set your own colors with a live preview. It applies everywhere: shop, product pages, cart drawer, checkout, customer dashboard, even the Stripe card fields.
A few other things in this release:
- Customers now verify their email before accessing their dashboard. Past guest orders with that email merge into the account automatically.
- All dates now follow your WordPress date, time and timezone settings. Emails, invoices, thank-you pages, dashboards, all of it. No more US-style dates in a German renewal email.
- New Compliance setting to choose if customers get logged in automatically after account creation.
- Pro: we went through Authorize.Net, Paddle and Mollie line by line. Better timeout recovery, no duplicate charges, cleaner refunds and subscriptions.
Plus a bunch of smaller fixes and improvements.
Full release note here: https://fluentcart.com/blog/fluentcart-1-6-5/
Next week, we are going to release something really big and exciting for FluentCart.
Can please integrate with delivery platform for easy to handle the shipping?
Example: easy parcel malaysia etc
urgent because get a lot of order using fluent cart. Manual submit order is sucks