Changelog

This week we are releasing additional fixes and enhancements to the Customer Portal. These changes are aimed at providing a better experience for your customers.

Better Site and Subscription Details

We cleaned up the sidebar that displays site, subscription, or license details.

Depending on the context, the most relevant information is now displayed first. Additional information and configuration options, such as “License security“, are now placed inside an expandable section. To make the experience smoother, the UI will also remember whether a user has expanded any of these sections.

Better FAQs

FAQs are now displayed based on the relevant products available in the store.

For example, if the user hasn’t purchased any WordPress products, or if your store doesn’t sell any, the “Installation” (or website-related) FAQs will no longer be shown. Similar improvements have also been applied to the Support Contact Form.

This week we are rolling out a useful update to the Store Settings page in the Freemius Developer Dashboard. Previously, all store configurations were displayed on a single page, which made it difficult to quickly find the relevant settings. Many makers also shared similar feedback with us.

To improve the UX, we are now grouping related settings into separate tabs.

For example, the basic configuration is now grouped under the “Information” tab. If you’re looking to embed the Customer Portal, you can now find it under the “Customer Portal” tab.

Additionally, we have fixed a few minor UI glitches across the Developer Dashboard. We hope this change makes it easier for you to navigate and manage your store settings.

Freemius supports tax refunds against a valid tax ID. For example, if a customer forgot to enter their VAT number during checkout, you can issue the refund from the Developer Dashboard. The associated subscription will then be updated and the tax amount will be exempted using the reverse charge mechanism.

We identified an issue in the Developer Dashboard where the tax refund option for Norway was not working properly. This has now been fixed.

We identified a regression in last week’s email style update where the footer was mistakenly pushed inside the main email content area. This unintentionally made the “Sent by Freemius” line more prominent. When sending emails to customers on your behalf, our goal is to give better visibility to your product.

With that in mind, we have deployed a fix as shown in the screenshot above. We also ensured the footer renders nicely in dark mode for email clients like Gmail.

With the evolution of AI, our software industry has taken a huge leap. Language and technical complexity are no longer barriers to creating software. Anyone with a product idea can now build applications and SaaS products with platforms like Lovable, Bolt, etc.

Once such software is created, there’s often value in sharing it with others—and eventually monetizing it. At Freemius, we understand this can be challenging for non-technical makers.

With that in mind, and to make it super easy for everyone to integrate Freemius Checkout and monetization, we’ve released a guide for a full end-to-end integration of Freemius with Lovable.

It all happens with a single prompt:

Implement the Freemius integration based on the knowledgebase content.

The outcome is as impressive as this:

• Integrated Pricing Page and Checkout: Your users will see the pricing you’ve configured in Freemius and will be able to purchase your product through the Freemius Checkout.
  
• Gated Premium Features: Easily gate premium features behind a paywall, and only allow access to users who have purchased your product.
  
• Integrated Accounts Page: Show active subscriptions and payments right within your app. Also link to the Freemius Customer Portal for advanced account management.
  

Head over to our docs to get started with the integration.

Freemius supports growth pricing or high-volume rates where the more you earn, the more you save. When your monthly gross sales exceed $50,000, the revenue share drops progressively, going as low as 0.5%. You can read more about it in our docs here.

This discount is applied automatically during the monthly payout. With today’s deployment, we are introducing a clearer UI in both the reverse invoice and the payout email so you can easily see the exact volume discount applied to your earnings.

As you can see, the reverse invoice will now prominently display the volume discount applied for the payout.

Similarly, your payout emails will also show the volume discount you received for the month, making it easier to reconcile your earnings at a glance.

This week we are rolling out several polishing improvements to our email system. These changes affect most of the emails sent by our system and include a number of small fixes.

The most notable update is the improved layout and overall visual consistency.

In addition, we have fixed a few UI glitches that appeared in certain dark mode email clients.

Overall, our emails are now more compliant and better optimized for compatibility across a wide range of email clients.

We have introduced a new API endpoint to help makers easily and securely download invoices for users. The new endpoint is:

/products/{product_id}/users/{user_id}/payments/{payment_id}/invoice.pdf

Detailed documentation can be found here.

This is especially useful if you’re implementing the Customer Portal inside your application (for example using the JS SDK). The endpoint validates that the payment belongs to the specified user before delivering the invoice, adding an extra layer of safety in user-facing integrations. For these use cases, we recommend using this new endpoint over the more direct one.

In last week we released an update following a compliance requirement from the wp.org plugin review team. The SDK integration snippet generated by the Developer Dashboard will now always have the is_org_compliant flag present (even though implicitly it has a true value).

This week we are releasing another update where our deployment mechanism will inspect the codebase itself and automatically add the flag if it is missing. This change ensures existing products remain compliant, even if the integration snippet was not manually updated.

As a follow-up to the recently released email customization feature, this week we are deploying the following enhancements:

1. The email section no longer requires a title to be present, giving you more flexibility when adding concise instructions or contextual notes.
2. The custom section now appears earlier in the email, with a UI that feels more naturally integrated into the overall email layout.

You can head to Emails → Customization to start customizing it right away.

We have also further enhanced the UI/UX of the Developer Dashboard around this feature:

1. The preview UI is now snappier and more compact.
2. A separate Styling tab has been introduced for email branding customization, reducing clutter under the single Customization tab.

This week we are rolling out follow-ups addressing several UI glitches and styling enhancements in the Customer Portal.

These changes are primarily at the infrastructure level and touch many UI components across the portal. As a result, you should now experience better visual consistency, especially when applying custom themes using CSS variables. Below are the notable improvements:

1. All icons are now rendered as inline SVGs, allowing your custom CSS to style them more reliably.
2. Several minor alignment issues have been resolved based on feedback from our makers.
3. We audited and replaced all remaining hard-coded color values with CSS variables to ensure custom styling works more predictably.

In addition to the UI fixed, we also fixed an issue where the portal could remain on a stale page after login. For example, if a store sells only SaaS products (and has no Websites page), users will now be correctly redirected to the Licenses page.

We have rolled out the following quality-of-life improvements to the Developer Dashboard.

Template Under WordPress Products

We realized in the last release we accidentally removed the “Template” type from the WordPress category. Many makers use Freemius to sell WordPress-related templates (for example, page builder templates or customization templates for plugins), so this made it harder to locate the correct product type during setup.

To address this, the Template type has now been added back under the WordPress Products category in the new product form.

Higher Bulk Pricing Support

Based on feedback from makers selling large credit bundles, we have increased the quota limit of pricing to support values up to 100,000,000 (100 million).

This makes it easier to configure plans for products that operate with high-volume credit systems.

More Exposure to Webhooks

To improve discoverability, webhooks are now available as a top-level menu item instead of being nested under “Integration”.

We received consistent feedback from SaaS & App makers that webhooks are a core part of the integration. Promoting it to a primary navigation item makes the integration workflow more direct and aligned with how modern SaaS products are built.

This week we are rolling out some small but important enhancements to our Checkout, aimed at delivering a better experience to your buyers, especially for SaaS and App makers.

Better Title for Plan Update

Our Checkout previously showed the title “License Update” when buyers tried to upgrade or downgrade their subscription. While this makes sense for WordPress products, we understood that for SaaS & App products it could be confusing. To make the flow more intuitive, we now identify such cases and display the title “Plan update” instead.

Similarly, for manual renewals the Checkout will now display “Subscription renewal” instead of “License renewal”, aligning the terminology with how SaaS and App makers typically position their offerings.

Back Button Hides Automatically

To further streamline the Checkout experience, when buyers reach the Review step (and about to pay), the back button will no longer be shown.

This reduces confusion where two left arrows were previously visible on the left side of the screen—one to return to the billing form and another to navigate back to the product’s website.

Better Fallback for the Billing Cycle Selector

Recently, we published an update where our Checkout automatically detects if there is no annual discount and, in such cases, falls back to displaying the billing cycle selector instead of the upsell UI. At that time, the billing cycle selector defaulted to responsive_list mode.

After reviewing feedback from makers with all three billing cycles configured, we are now defaulting the selector to dropdown mode, as it consumes less vertical space and keeps the layout more compact.

Cleaner Purchase Email for Licenses

We received feedback that the information shown in purchase emails about multi-unit licenses could be confusing for buyers. For example, if someone purchased a 5-Device license, the email previously displayed this as “Activations: 0 out of 5 devices”. This terminology is not always familiar outside the WordPress ecosystem. Additionally, in many SaaS and App scenarios, license usage is managed directly by the product, so Freemius may not have visibility into actual usage.

To make this clearer and more universally applicable, the email will now display a simplified label such as “License Type: 5 devices”, which better aligns with different product types and usage models.

This week we are releasing a new feature to support embedding our Customer Portal on more than one domain. Freemius allows you to embed the Customer Portal into your own WordPress website to provide a more seamless experience for your buyers. However, for security purposes, the portal will not load unless it has been embedded on the specified domain.

We understood this could be limiting in real-world workflows. Especially when testing the integration locally or in a staging environment, the URL is often different, making it impossible to see the portal in action.

To address this, you can now go to the Settings page of your Store and use the newly introduced Additional Whitelisted Domains configuration.

You can add as many additional domains or hostnames as needed, and the Customer Portal will load securely on those domains without any issues.

As per the updated guidelines from the wordpress.org review team, we are updating the integration snippet our system generates for the Freemius WP SDK. Previously, the is_org_compliant flag was only present in the snippet if it was explicitly set to false. Our SDK always treats the integration as WordPress.org compliant.

With the latest compliance update, the flag is now always present, defaulting to true.

For new products, this change ensures your first submission won’t get rejected due to a missing compliance flag. For existing products, we recommend making this manual change in your integration snippet. We will also follow up soon with an update to our deployment mechanism so the flag is automatically added to your integration snippet in newly generated versions.