Backlog
77Under consideration
Paypal as payment option
Some customers have requested for paypal as payment option
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!
Purge Customer Data / Reset Test Customer
t would be very useful to have a “Purge Customer Data” action in the Moonbase dashboard, especially during development and beta testing. Deleting a customer currently does not necessarily return the associated product/device state to a clean starting point. Licenses may remain as revoked records, while associated device activations can still remain active and trial/device history may continue to affect eligibility. As a developer, I would like an explicit administrative action that completely resets a customer for testing by removing or resetting: Customer/user data Licenses Trials and trial eligibility/history Device activations Pending activation requests Orders/entitlements associated with test activity Any other state that could prevent the same account or device from behaving like a completely new customer Ideally this could be called something like “Purge customer data” or “Reset test customer”, with a clear confirmation dialog explaining that the action is destructive. This would make repeated end-to-end testing much easier and, importantly, allow developers to restore a known clean state without having to contact Moonbase support.
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.
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.
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.
Sandbox/Simulation Mode for Purchase Flow Documentation
I want a way to simulate the purchase flow without making an actual purchase so that I can take screenshots for a user guide. This would be helpful for creating documentation without incurring costs.
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.
Essential Transactional Emails for Updates and Bugs
I want to be able to send "essential transaction" emails to all customers when a version update is released or when there are bug notifications with workarounds. This is important because currently MailerLite only reaches those who have opted in, but these updates are critical for all users regardless of their marketing preferences.
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.
Next up
3Committed and queued
GBP as holding currency
To reduce fees for UK sales, supporting GBP as a holding currency would make sales there better.
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.
Product resales (cross-merchant)
Many Moonbase merchants already work with each other: they bundle their plugins with another company's, give away a partner's product in a promotion, or sell each other's products in their stores. Today all of that is done by hand. Codes are bought and swapped in batches, the money is settled afterwards with spreadsheets and invoices, and customers have to redeem a code on another website, with another account, before they get what they paid for. We want to make this part of Moonbase. Any merchant should be able to resell another Moonbase merchant's products in their own store, on their own or bundled with their own products, with each merchant paid for their part automatically. What we want to accomplish Collaborations without the admin. Two merchants agree on terms once in Moonbase. Every sale after that is split and paid out to both, with nothing to reconcile afterwards. One checkout for the customer. A customer can buy a bundle with products from several companies in one go. Each license comes from the company that makes the product, so activations, downloads and updates work just as if they'd bought it directly. Product owners stay in control. You decide which of your products others may sell, who may sell them, and on what terms, such as a fixed wholesale price or a share of each sale. Easy enough for a single campaign. Joint bundles and cross-promotions are one of the best ways to reach customers who already buy from someone else. Setting one up should take minutes, not a round of emails. What it won't be This isn't a marketplace. Every store stays its merchant's own, and a product is only resold where its owner has agreed to it. Some bundle features will work differently for another merchant's products. Partial bundles, for example, can't take them into account, because your store can't see what a customer already owns from another merchant. Tell us how you'd use it If you already sell or bundle products together with other companies, leave a comment about how you do it today, what terms you usually agree on, and what you'd need from this to move it into Moonbase.
In Progress
2Actively being built
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.
Gift purchases
Occasionally, we have customers who wants to buy products as a gift for others. We should support this better, either by being able to buy a voucher code, or schedule the delivery of a purchase to another email address.
Done
61Recently 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.
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.
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.
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.
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.
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.
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.
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.