ThirtyBees 1.7 OFFICIAL is here!

[Smile]

thirty bees 1.7 is here! 🐝

We’re excited to announce the release of thirty bees 1.7! This version brings a wide range of new features, powerful merchant tools, better performance insights, improved security, and a stronger foundation for the future of the platform.

Better tools for merchants

Managing your store is now easier with several new improvements:

Session-based profiling
Find performance bottlenecks without affecting your customers. You can enable profiling for your own session only, analyse real page performance, and optimise your store without turning on debug mode for everyone.

Packs with combinations
Product packs can now include combinations. Create more flexible bundles with specific sizes, colours, or variants exactly as your customers need them.

Advanced list filters
Back-office lists are more powerful than before. Create custom filters for orders, products, and customers to find what you need faster.

Built-in credit system
Issue store credit to customers and automate voucher generation while staying compliant with tax regulations.

Official PayPal certified module
thirty bees 1.7 includes a new official PayPal module using the latest PayPal APIs, providing a modern and future-proof payment solution.

Smoother daily workflows

Many improvements make everyday store management easier:

• PDF documents such as invoices can now be displayed directly in the browser.

• Create orders directly from abandoned guest carts.

• Attach files to customer service messages, such as invoices, manuals, photos, or return labels.

• Improved pack handling across the back office, orders, delivery slips, and dynamic pack synchronisation.

• More flexible back-office order creation, improved module warnings, better specific price management, custom export filenames, and clearer multistore order views.

Better product and shipping management

Products now support universal compliance attributes, including:

• HS codes

• Country of origin

• Age verification

• Dangerous goods information (UN number, hazard class, and packing group)

These structured fields make it easier to manage shipping, customs, and invoicing requirements.

Product combinations also received improvements: dimensions such as width, height, and depth can now change per combination. This allows carrier selection and shipping costs to be calculated more accurately for larger variants.

Reliability, security, and future improvements

thirty bees 1.7 introduces automatic database backups with configurable retention periods, helping protect your store and data.

The platform also includes preparation work for PHP 8.4 compatibility, ensuring thirty bees continues to run on modern and secure server environments.

For developers, version 1.7 adds new hooks and extension points, including improvements for payment options, webservice resources, delivery options, contact forms, custom KPIs, admin order buttons, and namespaced Object Model hooks.

As always, this release also contains many smaller improvements, bug fixes, quality-of-life updates, and multiple security fixes.

Thank you to the community ❤️

A huge thank you to everyone who contributed code, tested updates, reported bugs, and shared feedback. This release would not be possible without the thirty bees community.

Update your store today and discover everything thirty bees 1.7 has to offer! 🐝

[Kashir2000]

Great news! Thank you for your hard work!

[zen]

Yes.. great ! So happy, i'm gonna try it soon.

but the changelog is missing on the git..I've seen it on the newsletter received by email.

Also it's been 2 month already .. and I didn't know it ? what happened ?

😍

[Smile]

The release happened a little earlier than the email and forum announcement, mainly because of the holiday period. We wanted to avoid communicating the release at a time when we would have limited availability to interact with users and quickly respond to any issues, especially for less experienced users.

We also wanted to make a few further improvements to the PayPal integration before actively communicating the release more broadly.

On the other hand, we did not want to hold back the release itself for too long. Waiting until after the holidays could have caused further delays, as development time would then also need to be divided between other modules and priorities. So we decided to release it first, while postponing the broader communication until we were in a better position to support users properly.

[zen]

OK, thank you Smile for the answer, that makes sense.

This release gives me the will to get a nice modern theme to work with. Could that be done natively for once, instead of a theme that drags a pile of modules along with it? A default theme should work on its own, that's also easier for you to maintain.

I'd be really happy to see a Bootstrap 5 theme in TB, and I'm willing to do the work. I did one a few years ago (Cisero), so I know where the landmines are. It would ship alongside Niara rather than replace it, so nothing breaks for existing shops, and with no build chain at all, plain CSS and variables, so anyone can edit it.

Happy to talk about it whenever you have time.

[x97wehner]

Is there any information available on how the store credit works? I've tried to navigate it via back office to no avail

 

[Smile]

The database and code has already been prepared to support store credit, so it should now be possible to build a module on top of it. There is currently no back-office interface for it yet.

We also expect to release a gift card module in the coming weeks, which will make use of this functionality.

[zen]

Good to hear about the gift card module.

About the store credit: this is something I know well. I sell a customer credit module on the PrestaShop side (wallet, mixed payment credit + card, refunds turned into credit, top-up with bonus tiers, integrity checks), so I've already hit most of the edge cases.

For TB I'm not trying to sell anything. If you want, I can help finish the job, back office and front office, on top of the layer you already shipped in 1.7. I'd rather contribute that than see everyone build their own thing on the side.

Just let me know what's already planned so we don't overlap with the gift card module, and whether the core schema is considered stable.

Best regards 🙂

[grbfst]

Any news on a Mollie update? Wero is now actively being pushed.

[BillyTheMountain]

The upgrade to this new version from TB 1.6 was so easy !

Thank you for your hard work!

[Lucas Thomas]

Good to hear the 1.6 to 1.7 upgrade went smoothly — that's reassuring for those of us still planning the move. On the credit module offer, the key question is really whether the core schema is settled; if gift cards and store credit end up sharing tables, contributing before that's locked in could save duplicated work. Worth waiting for a clear answer on what's already planned before anyone starts building alongside it. Mollie and Wero is a separate concern, but it seems like the kind of payment update that affects a lot of stores, so hopefully it's on the radar too.

[ethanwright]

The point about the core schema being settled before anyone contributes to the credit module makes sense to me — building gift cards and store credit on tables that might still shift seems like avoidable rework. A clear statement of what's already planned would help people decide whether to wait or start. I don't have a Mollie setup myself, but the Wero question sounds like it matters to a fair number of stores, so it's reasonable to ask whether it's on the roadmap alongside the 1.7 release.

[Lucas Thomas]

Locking down the schema question seems like the practical first step before anyone touches the credit module, and a short list of what maintainers already have planned would settle whether to wait or start. I'm curious whether the 1.6 to 1.7 path mentioned here needed any database adjustments, or if it was mostly file replacement. That detail would help those of us weighing when to move. On payments, Wero is outside my own setup, but if a large share of stores depend on it, asking early whether it's in scope alongside 1.7 seems fair rather than pushy.