The licensing analytics already support breaking down by custom metadata from the licensing client, but we want to also break down by parameters set on customers, licenses, trials and more. This way, we can segment analytics by our custom properties easily.

Christian Haase 2 days ago

💡

Feature Request

The one thing almost all Moonbase merchants have in addition to Moonbase is a ticketing system for handling customer support cases. If we could build a simple system within Moonbase, exposed in the embedded storefront and connected to customer accounts, it would alleviate and simplify the common setups merchants have. If you have specific thoughts and ideas around this, please share!

Tobias Lønnerød Madsen 4 days ago

💡

Feature Request

We want to be able to have different kinds of users on merchant accounts, restricting their actions and visibility. Typically for scenarios like: Marketing users who need access to marketing tools and analytics Financial users who need access to payouts and invoices Support users who need access to customer and license data

Tobias Lønnerød Madsen 9 days ago

💡

Feature Request

Creators and labels often enter into revenue share agreements where one party covers upfront costs (e.g., music video production, photography, marketing, artwork, or other project expenses). Currently, revenue shares are distributed immediately according to the agreed split, making it difficult to recover those initial investments before payouts begin. Proposed Solution: Allow users to attach one or more recoupable expenses to a revenue share agreement. Revenue generated from the sales would first be applied toward recovering these costs before any payouts are distributed according to the agreed revenue split. Once the recoupable balance has been fully recovered, distributions would automatically revert to the standard revenue share percentages, with all parties able to track the remaining recoupable balance and recoupment progress.

Tobias Lønnerød Madsen 10 days ago

💡

Feature Request

Would be nice if referrer information was also available for downloads, not just purchases

Jussi Viiri 10 days ago

1

💡

Feature Request

Brevo integration for automations. Currently we can not set up automated emails because of this.

Sabol Hill 10 days ago

💡

Feature Request

Would be great to allow paying out each holding currency separately to avoid conversion fees on receipt.

Benjamin D'urso 10 days ago

💡

Feature Request

What's missing is a way to automate and orchestrate that layer from external tools through a standardized connection. An MCP integration would allow operators to connect Moonbase to AI-powered automation environments and from there bridge project management tools, CRM systems, email platforms, and campaign planning workflows to trigger and sync actions across the stack. Concrete use case: Running email campaigns and discount campaigns in parallel, coordinated from a single source of truth. Today this requires manual effort across multiple disconnected tools. With an MCP connection, a workflow could automatically create or update a discount in Moonbase when a campaign goes live in an external platform, confirm sync status back to wherever that campaign is being managed, and keep everything aligned, completely hands-off once set up. Launches, seasonal sales, and affiliate campaigns all require tight coordination between pricing logic, checkout configuration, and outreach. MCP-based automation would make it reliable, repeatable, and scalable without much manual  work. An MCP server exposing Moonbase's core actions, such as creating or updating discounts, reading sales data, and triggering pricing changes, would let operators build their own automation layer on top using whatever AI or workflow.

Markus 12 days ago

💡

Feature Request

The API reference ( https://moonbase.sh/docs/storefronts/api/) mentions orders but does not expose the full API. I figured it out myself, but it would have been easier if there were a clean documentation with all properties and their expected formats.

Stanislaw Gorlow 16 days ago

📥

Feedback

We're looking to see a breakdown of unique device activations by metadata like platform (Mac/PC) and host application (DAW). Currently, we can only see validations, and having this granular data on activations would give us a much clearer picture of our user base. Being able to formally attach and track this metadata during the activation process would be incredibly valuable for understanding our audience.

Michael Vecchio 22 days ago

1

💡

Feature Request

Right now it doesn’t seem to be possible to add referrer when using the embedded storefront, so there’s no visibility into which referrers generate the most purchases

Jussi Viiri 24 days ago

4

🐛

Bug Reports

I want to be able to update or replace the Moonbase branding/button on the floating cart with my own logo (SabolHill). This is important for maintaining a consistent brand identity across the storefront.

Pat Watters 25 days ago

💡

Feature Request

I want a way for a single plugin activation to automatically activate all other licenses that a user owns. This would streamline the user experience so they don't have to activate each plugin individually.

Adi Rotem 27 days ago

2

💡

Feature Request

I want to be able to set up pre-orders for products that already have existing releases, but I need a way to prevent those pre-order customers from getting immediate access to the current releases. This would allow me to sell future access without giving away current content for free or prematurely.

Daniel 29 days ago

💡

Feature Request

I want to be able to add metadata to an activation using the Node.js SDK (e.g., in requestActivation()) to take advantage of advanced licensing analytics without having to use the endpoint workaround. This is important for tracking specific device or environment details like 'Is64Bit' directly in the activation flow.

Patrick R Vecchio about 1 month ago

1

💡

Feature Request

I want the online activation page layout to be improved or reorderable. Currently, "Purchase product" is the first option even when a user already has a license, which is confusing. It would be better if the license activation option was more prominent or if the order could be changed so existing license holders don't get confused.

Jussi Viiri about 1 month ago

💡

Feature Request

I want the account creation page that opens from the plugin popup to have an option to redeem a voucher code. This would help Plugin Boutique customers who get a download and a code to redeem it while creating their account.

Scott Silfvast about 1 month ago

💡

Feature Request

I want an option to redeem a voucher code directly during the account creation process when a user is redirected to Moonbase from a plugin. Currently, Plugin Boutique customers have to create an account and then find the redemption page separately. Adding a "redeem code" field to the "Create Account" page would make the onboarding flow much smoother for these users.

Scott Silfvast about 1 month ago

💡

Feature Request

On the hosted activation page, the instruction text says "Please log in or create an account to activate your product" but the button says "Sign in". This inconsistency can cause friction for literal-minded customers. I want these to be consistent (e.g., both using "Sign in" or both using "Log in") to ensure a smoother activation flow for resellers.

Scott Silfvast about 1 month ago

💡

Feature Request

A customer should be able to delete his account via the storefront without contacting support.

Stanislaw Gorlow about 1 month ago

💡

Feature Request