Selling subscriptions, not just publishing a page
A storefront that takes an order and emails it to somebody is not selling subscriptions. The hard part is everything after checkout: creating the account, activating the service, starting the billing cycle, storing a payment method and charging it again next month.
OpenBRM deploys with an integrated ecommerce component that sits on top of the billing engine, so the order a customer places is the order that bills them. There is no export, no nightly synchronisation, and no second product catalogue to maintain.
What happens at checkout
- The customer account is created in the billing system
- The subscription is activated, firing any provisioning hooks you have configured
- The billing cycle starts on the customer's own date
- The payment method is stored against the account for recurring collection
- Confirmation notifications go out from the same templates as your invoices
One catalogue, one price
Products, bundles and prices shown in the storefront come from the billing system's catalogue. Change a price or launch a promotion in the bundle manager and the storefront reflects it, because there is only one source of truth. This removes the most common ecommerce billing failure: the site advertising one price while the invoice shows another.
Self-service after the sale
The same component gives existing customers a place to view invoices, make payments, change plan and update payment details — which reduces the support load that otherwise scales linearly with your subscriber count.
Product bundling · Payment gateway integrations · Payment processor setup