Backlog
91Under consideration
GBP as holding currency
To reduce fees for UK sales, supporting GBP as a holding currency would make sales there better.
Limit one trial per user/email across devices
I want to be able to limit trials to one per user/email across all devices. Currently, users can start multiple trials by switching devices, and I need to prevent this by enforcing the limit based on their email address.
Localize customer UI
Customers in certain markets prefer seeing interfaces in local languages, so we should be able to support local languages as well as local currencies.
Pricing based on Purchasing Power Parity (PPP)
An issue that comes up every now and then is how to best support markets with a lower purchasing power than the rest of the world. Today, we don’t support pricing based on region, although we do support pricing per currency (with more being added through @Local Currency Support), but it would be better if we could discriminate based on region or country.
Time-Based Release Access License Entitlement
We want to be able to sell time-limited release access license entitlements, which gives access to using the product forever, but only with versions released within a certain time after purchase. Typically, you say you get lifetime access with 1 years worth of free updates. Updates after this point needs a new license (or upgraded, but we need to build support for this). This is an alternative to the version-based release access entitlement.
Social logins for customers
We should allow customers to sign up and log in with social accounts like Google, Facebook, etc. This should streamline anonymous sign-ups.
Customer support system
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!
Bulk/Global License Activation on Single Plugin Activation
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.
Support SSO for customers using external providers
For merchants already running their own authentication solutions, or relying on 3rd party platforms like auth0, clerk, etc, it would be good to support SSO using these for customers. This would streamline the customer journey, and not require new credentials.
Limit redemptions per customer for coupons
Right now, we can limit the number of redemptions per coupon and code, but we want to limit it by customer. It won’t prevent users creating multiple profiles to redeem a code multiple times, but we still want the effect of exclusivity around a single code that is easier to share than having to generate personal codes.
Next up
8Committed and queued
Marketing Automations
To take full advantage of the close customer connections Moonbase enables, we want to build marketing automations to unlock even more potential. These automations will be able to do things like provisioning new licenses based on purchases, send emails based on trials expiring, and much more. If you have concrete scenarios you wish to see supported, please leave a comment or reach out to us! This feature will be built once we have support for @Email Campaigns.
Support for Abandoned Purchase / Abandoned Cart Email Automation
I’d love to see built-in support for abandoned purchase or abandoned cart notifications — where merchants could automatically trigger an email or webhook when: a customer begins checkout or adds items to a cart, but does not complete the purchase within a specified time window. This would help merchants improve conversions by following up with customers who started the checkout process but didn’t finish it. Possible options could include: sending an email directly from Moonbase, including cart contents and a link to complete checkout a webhook event like CartAbandoned that could be sent to external marketing platforms (e.g., Klaviyo, Braze) configuration for the time delay and reminder frequency Thanks! This would fill an important automation gap for custom storefronts that don’t have built-in abandoned cart tracking yet.
Test payments
While developing website integrations with Moonbase, it would be great if we can support a test mode in order to make development easier. This can be similar in functionality to the demo mode accounts currently start out in, but should be toggleable per session or checkout.
Activate seats on license for sub-product
We currently support a sp:owned claim on license tokens that contain a list of owned sub-products for the customer and product. While developers can integrate an activation flow directly for each sub-product, it would be smoother if we can simply activate seats on those sub-products using the main product license, skipping an increase in license validation requests since each sub-product needs validation.
Rich text content for fulfillment messages and descriptions
To be able to have more flexibility when designing fulfillment instructions for products, but also descriptions for both products, bundles and releases, we want to support rich text content. Possibly Markdown content, or another format that is easily edited, which supports the basic things we need like links, images, lists, etc.
Allow merchant branding in email footer
Hi The footer in emails sent to buyers currently looks like this: [Moonbase logo] This email was sent to [buyer email address] on behalf of [merchant name] by Moonbase.sh — an authorized partner powering software delivery and licensing. [Moonbase address] Would it be possible to customize this footer? For better brand consistency, it would be great to have an option to display the merchant's logo and address instead. Perhaps the Moonbase footer could remain the default, with the merchant-branded version becoming available once emails have been configured to send from the merchant's own domain?
Revoked offline activation still appears in device list
I want the device list to hide revoked offline activations. Currently, when an offline activation is revoked, the seat count correctly updates to '0 of 5 seats used' and 'No activations yet', but the device list continues to show the revoked offline activation as a historical record. This is a visual discrepancy that should be resolved by hiding revoked offline activations from the list. [REF-RESEARCH:O3T6RB]
Coupon code links should show the coupon code on first click
moonbase.sh/buy/product?coupon=FLSTUDIO The purchase flow would be more enticing when clicking on an email or website link if there’s instant confirmation of reason for discount before the next step of the flow (where the coupon code is then shown)
In Progress
4Actively being built
Two-factor authentication
It would be great to have two-factor authentication, e.g., using an authenticator app, to make the Moonbase configuration backend more secure.
Passkey support
Right now admin & user accounts are only protected by passwords. Passkeys are a much stronger and modern authentication method which even work with biometric authentication: FIDO Passkeys: Passwordless Authentication | FIDO Alliance
Scoped API keys
To increase the security of integrations, we want to be able to scope API keys to specific endpoints and actions
Admin/Merchant user roles
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
Done
31Recently shipped
Email Campaigns
Since Moonbase already tracks customer newsletter statuses, and syncs these with external platforms, we want to build a way to also send email blasts from within Moonbase. We can also use the segmentation that already exists to support targeted campaigns for subsets of customers. A simple email builder will be needed to support outgoing emails, custom HTML will not be part of this feature to begin with. Custom sending domains will be required for merchants to use the feature.
Local Currency Support
To better support markets with stronger demand for shopping in their native currencies (Japan and South Korea being two), we want to build support for local currencies across all sales. This means we need to allow both: Explicit prices for any supported currency Automatically converted and prettified prices for local currencies Accounting for local purchasing power will not be part of this feature, but could be implemented by overriding specific currencies. Pricing for conversions will be added to our pricing plans, and we aim to keep this as low as possible. As part of this, we will also streamline the payouts, to convert all currencies on the Moonbase side before issuing a single payout transaction to each merchant.
Klayvio integration
Recently, many in our industry have switched to using Klayvio as their marketing platform, due to its unique capabilities around automations. We should consider building a native integration to enrich it with Moonbase data. Seems like it will be more capable than the current platforms we integrate with.
Newsletter Sign-Ups in the Embedded Storefront
Being able to capture newsletter sign-ups anonymously on websites, without having to force actual user sign-ups or purchases would be great to offer. This way, merchants don’t need to add bad forms from their newsletter/marketing platform to websites, as they can just use the embedded storefront that is already there to also power these opt-ins.
User groups
We would like to be able to assign our customers to different groups (i.e. Internal, Testing, Public). We would then grant access to individual product releases based on group membership. Customers would be assigned to groups manually (by an admin) or eventually through self-service routes like the user portal or invite links.
iLok integration
We’re partnering up with Pace to bring native iLok integration to Moonbase! This means: Your customers can connect their iLok account to get licenses deposited into their iLok account Moonbase will sync as much data back as possible, to power your marketing integrations Moonbase features like Rent-to-Own and partial bundles, and more will work out-of-the-box Do you have specific pain points with iLok today? Let us know, so we can build the best possible integration!
Partial Refunds
It would be really helpful if we can support partial refunds, where a configurable quantity or selection of items can be refunded. This needs to also handle the tax implications for partially refunding purchases.
CSV export of customer data
Would be handy to be able to simply export a CSV with data on all customers, without having to scrape the API, similarly to how we can export sales data.
Move purchase to another customer
Every now and then customers will enter the wrong email while making a purchase. Often, merchants can simply update the email of the customer account, and re-send the receipt. However, some times, the customer will create another account with the correct email, causing a conflict error when trying to change the email address. We should allow moving purchases to other customers, to have another path to resolving these issues quickly.
Mailjet Integration
https://www.mailjet.com/pricing/ They offer segmentations, Analytics, and a very powerful HTML editor among other features. Pricing Comparison With 4k subscribers and 5k mails per month we end up with the following prices: Mailerlite ~ 400€ a year (limited mostly be the number of subscribers) Klayvio ~ 1200€ a yer (limited by the number of subscribers) Mailjet (essential plan) ~ 200€ a year (no subscriber limit, but limited by mails per month) Mailjet (premium plan) ~ 320 a year Also Mailjet is hosted in Europe, and are fully GDPR compliant, which is becoming increasingly important.