Changelog

Freemius allows customizing the tone of the emails sent to your buyers on your behalf. The tone can be set anywhere between Playful—including emojis and more expressive language in the subject and body—and Professional, keeping the communication formal, clear, and emoji-free.

It came to our attention that this setting was not being consistently respected for a few system-generated emails, particularly some payment and subscription-related notifications.

We’ve deployed a fix to address this. All emails will now correctly respect your selected tone setting across all supported email types.

This week we’re rolling out a new feature aimed at helping makers better understand all transactional and automated emails Freemius sends on your behalf to buyers.

If you navigate to the Emails section, you will now see a new tab called Email History. From there, you can view a list of all emails Freemius has sent on behalf of your product.

You can also click Preview to inspect both the HTML and plain-text versions of each email.

This is the first phase of the feature. We’ve seen that makers often want visibility into buyer communications without having to wait for specific events to occur. The longer-term goal is to surface all types of emails Freemius sends—such as new purchases, renewal reminders, payment notifications, and cart recovery—upfront and in one place.

If you have practical use cases or suggestions for how this should evolve, please share them on our feature board. We actively review and prioritize feedback there.

The Freemius Developer Dashboard allows you to view detailed information about your users. One of the most useful capabilities is being able to log in as a user to the Customer Portal, making it easier to reproduce, inspect, and debug issues firsthand.

With this week’s deployment, we’ve strengthened the security around this flow. When logging in to the Customer Portal as a user, you will now be prompted to confirm your Developer Dashboard password.

This additional confirmation helps ensure the feature remains secure, even in scenarios where a device may be left unattended or otherwise compromised.

This week we are rolling out a couple of small bug fixes and quality-of-life improvements across our API and backend systems.

• We identified an issue where removing all products from a bundle could, in some cases, break the Customer Portal. The underlying issue has been addressed and fixed.
• The license.created event was not being triggered when licenses were created manually. This has now been corrected, ensuring consistent webhook behavior.

This week, following feedback from our makers, we are deploying a few small quality-of-life improvements to the Developer Dashboard.

• We are now sorting the product and store sidebar by title. This makes it easier to scan and quickly find related or similarly named items.
  
• We previously allowed non-square icons for products and stores, which could lead to inconsistent rendering in PDFs, Checkout, and other system-generated surfaces. The UI will now enforce square icons where required to ensure consistent presentation.

We received a bug report where the Customer Portal allowed customers to manually renew licenses that had already been cancelled.

Cancelling a license is a deliberate action taken by makers from the Developer Dashboard. In such cases, it’s expected that the license cannot be renewed by the customer afterward.

To align the Customer Portal with this behavior, the Renew button is now disabled for licenses that were manually cancelled by makers. A tooltip is also shown to explain why renewal is no longer available in these cases.

Freemius Checkout shows a checkbox for trial purchases that allows buyers to opt in to receiving a reminder email before the trial ends. This reminder helps buyers stay informed before an upcoming charge and gives them time to decide whether to continue or cancel. The same email also plays an important role in reducing disputes and chargebacks.

However, we noticed that the buyer’s selection was not being properly reflected in the Review step. The UI always indicated that a reminder email would be sent, even when the buyer had explicitly unchecked the checkbox.

This has now been fixed. The review step will correctly reflect the buyer’s choice and clearly indicate whether a trial reminder email will be sent.

This week, we released several quality-of-life improvements to our Developer Dashboard, with a focus on exports and the Review & License Recovery apps.

Improved UX of the Review & License Recovery App

Following our recent rebranding of the License Recovery and Review app, we’re rolling out a set of UX improvements to make these applications more intuitive and resilient.

The forms are now reactive to validation issues upfront, helping users identify and resolve problems earlier in the flow. We also addressed a few layout inconsistencies to ensure a cleaner and more predictable experience.

Fixes in the Exports

We identified a couple of minor gaps in our export mechanism that could lead to missing context in exported data.

• The licenses export was missing the license key
• The affiliates export was missing the user ID

Both issues have been resolved with today’s deployment, ensuring exports now include all the expected fields.

Fixed License Unit in the Analytics UI

We noticed an issue where the license unit was not correctly reflected in the Analytics filtering UI.

This has now been fixed, and the label correctly reflects your configured license unit.

We are glad to announce that we have started collecting, reporting, and remitting VAT in Norway for all B2C transactions. The VAT handling follows the same model used for other European authorities.

For applicable transactions where VAT is collected, a compliant VAT invoice is automatically generated.

The invoice clearly shows the VAT amounts in both the original transaction currency and the local NOK currency, as required by regulations.

For B2C transactions, companies can enter their Norwegian VAT number and, after validation, will be exempt via the reverse-charge scheme.

The rollout is automatic and applies to all Norwegian transactions from now on.

We are releasing a new feature aimed at easing the life of AI SaaS makers. In the age of AI, consumptive or usage-based pricing has become increasingly popular, and Freemius supports this model out of the box (check our video tutorial).

We also understand that this pricing model can directly impact your refund policy. For example, if you are building a generative AI application with a subscription and top-up model, you may want to offer a money-back guarantee only for unused credits.

You can now configure this behavior directly from the Freemius Developer Dashboard. Simply go to Plans → Refund Policy and enable the “Limit refunds to unused credits for usage-based features” checkbox.

Once enabled, Freemius will automatically include the appropriate clause in the refund policy generated for your product. You can read more about this behavior in our documentation.

Please note that this feature is currently available for SaaS-type products only. If you have other product types and a valid use case, feel free to reach out to our support team and we will be happy to explore enabling this option.

This week we’re rolling out a few improvements to our Documentation website.

New Feature: Filter Documentation by Product Type

At Freemius, we’ve been pushing hard to expand our platform for SaaS makers. This has introduced a growing set of new features, tools, SDKs, and supporting documentation (if you haven’t already, you can take a quick look at our Year in Review to see what’s new).

As the documentation grew, it became increasingly important to clearly separate WordPress- and SaaS-related guides, so makers don’t have to second-guess which SDKs or tools apply to their product.

With that in mind, we’ve introduced a filtering concept on the documentation pages. You can now select SaaS or WordPress to view a focused subset of guides relevant to that product type, or keep All selected to browse everything.

You’ll also notice that some pages adapt based on the selected category. For example, the Sales Analytics documentation now reflects the chosen product type where applicable.

This should make it easier to understand which features and workflows apply to the type of product you’re building. With this foundation in place, we’ll gradually roll out more fine-tuned and targeted guides.

More Guidance for LLM and AI

We recognize the growing importance of building with LLMs (large language models) and AI-powered tooling. To make our documentation easier to consume by AI scrapers, agents, and developer tools, we’re now exposing the following resources in the footer:

• llms-full.txt — All of our documentation bundled into a single, large Markdown file.
• llms.txt — A summarized version of the documentation with links to individual guides, in Markdown format.
• OpenAPI — Direct access to our OpenAPI specification.

One of the many useful features of the Freemius Developer Dashboard is the ability to explore all your users in the context of a Store. Since a store can have multiple products, this view makes it easier to see all users in one place. The same UI also allows you to view and update information for individual users.

It came to our attention that the Billing Information form in this view was not working correctly and was failing to update any of the fields.

With today’s deployment, this issue has been fixed and billing details can now be updated as expected.

We identified an issue in our Customer Portal where the country dropdown was not correctly reflecting the user’s billing country.

This has now been fixed, and the dropdown will consistently show the correct billing country for the user.

We have added a new tab to the Product Settings page called Useful Links. This tab brings together several self-service tools—such as the Customer Portal and the License Recovery Tool—that you can easily share with your customers. In addition, it also lists all legal pages that Freemius generates for your product as your MoR.

You can access this section from Settings → Useful Links.

By grouping these resources in a single place, this update makes it easier to discover and share some of the built-in tools Freemius provides to help with customer support and product management.

We have rolled out a major update to the Developer Dashboard aimed at improving the onboarding experience for makers. Some time ago, we introduced the Setup Checklist to outline the steps makers need to follow to integrate their product with Freemius.

However, we realized that the button was not prominent enough and was easy to miss. To improve this experience and make the next required step more obvious, we have introduced a new banner at the top of the Developer Dashboard.

This banner highlights only the next mandatory step and automatically gets out of the way once the integration is complete. Makers can still access the full Setup Checklist page at any time to review optional steps and further customize or grow their product.