Subscription Plan Customization

🚨 Need to create subscription plans in NetSuite but not sure where to start? 🚨 No worries! I’ve created a step-by-step tutorial to help you set up subscription plans in NetSuite, making it easy to manage recurring services seamlessly. 📅💼 What’s in the Tutorial? 1️⃣ Understand Subscription Plans Subscription plans can include recurring services, usage, commit-plus overage, and one-time charges. Use add-on item lines for simplicity, without needing a full plan or price book. 2️⃣ Navigate to Subscription Plans Go to Lists > Subscription > Subscription Plans > New to create a new subscription plan. 🔍 3️⃣ Enter Plan Details Name your plan (e.g., “My First Plan”). ✏️ Choose the Initial Terms (e.g., one year) and define the subscription term length. 📅 4️⃣ Configure Subscription Terms Standard terms align items with the subscription start date. Custom terms allow editable end dates until any subscription line becomes active. 5️⃣ Evergreen Term Setup Enables ongoing revenue for two years unless extended by invoicing preferences. ⏳ 6️⃣ Add Line Items Select items under the Line subtab and specify: Type: One-time, recurring, usage, or commit-plus overage. 🔍 Billing Mode: In advance or arrears. 💳 7️⃣ Renewal Preferences Set renewal options and preferences like uplift pricing for price increases at renewal. 📈 8️⃣ Price Book Setup Use the Price Book subtab to create price plans for each item after setting up the subscription plan. 💰 🎥 Watch the full tutorial in the comments! 💡 With this guide, you’ll create and manage subscription plans like a pro. Let me know if you have questions or feedback below! 👇 #NetSuite #SuiteBilling #SubscriptionManagement #Tutorial

I was to design a dynamic seat-based subscription model for an application only to realize that none of the big payment gateways in Nigeria support this with automatic renewals. Here's what I did: A seat-based subscription model is the type used by platforms like GitHub or Jira where you’re billed based on the number of users (or “seats”) you add to your team. The more seats, the more you pay. Global payment gateways like Stripe support this natively, but one of the business requirements was to stick to gateways in Africa. So I had to design it myself. Here’s how I approached it: - Worked with stakeholders to define pricing plans and what each plan offers per user - On subscription, collected the number of users, selected plan, and billing interval from the client - Calculated the total amount, charged the user, and after a successful charge, extracted and stored the authorization details amongst other data securely - Calculated the next billing date based on their interval (monthly or yearly) I then set up cron jobs to: - Check when the next renewal is due - Recalculate the number of seats - Use the saved authorization details to charge again - Update the next billing date If a renewal failed: - Sent emails to inform the user - Generated a one-time payment link for them - Retried a fixed number of times - If all retries failed, auto-cancelled the subscription and notified the user I also built services for: - Cancelling, restarting, upgrading, and downgrading subscriptions - Restricting seat addition based on their active plan It was a bit complex to design and set up manually, but it gave us full control over billing logic and how we manage seats per team. If there’s any payment gateway in Africa that already supports this kind of model, I’d love to know. #softwareengineers #tech #systemdesign

Too many businesses don’t innovate on pricing, subscription, or membership models for their unique customer set and usage habits. Mostly because historically creating nuanced pricing and shipping models have been too cumbersome to execute against, not because they aren’t significant revenue and retention drivers. Let's take a look at an example: Say your company sells diapers. Companies that offer a subscription for diapers may set up a 30- or 60-day delivery option for their subscribers, but what if that cadence doesn’t match the time frame of how often that customer needs a new pack, and how frequently the baby needs to be sized up. It's not only inconvenient for the customer to be on a 30-day delivery option without being considerate of the number of diapers that the customer is using, how frequently their baby wears them, and how easily they can size up as the baby grows, but it also leads to downstream issues of churn, customer support issues, returns, and more. Customers need more flexibility in their pricing and subscription options while taking into account custom patterns and behaviors that ultimately lead to long-term retention. This is one of the main use cases we solve for at Prive. Let your subscription and pricing strategy be a nimble superpower.