Before you start
- Agreed amount, currency, billing frequency and cycle/trial terms.
- An enabled recurring-payment configuration for the installation.
- A distinction between product setup and a customer’s actual subscription: a plan is not a customer renewal.
Open in your admin application
Use your installation’s admin address with one of these routes. Replace {id} with the actual record identifier.
/subscription-plans/subscription-plan-insert/product-edit?ProductID={id}/product-renewalsCreate neutral billing terms
Open the plan insert page
Go to
/subscription-plan-insert. Enter Plan Code, Plan Name and Description so operators can distinguish the schedule.Enter amount and cadence
Set Amount, Currency Code, Billing Interval and Billing Interval Unit. For example, 49 USD every 1 months represents a monthly schedule. These are field-value examples, not a seeded plan. Enter text values without quote characters.
Set cycle and trial terms
Review Billing Cycles, Trial Amount and Trial Billing Cycles if used. Verify the intended gateway interpretation in the configured integration. Leave internal Data alone unless the deployment-specific runbook requires it. Set Is Enabled and save.
Attach the schedule to the product
Open the Subscription product
In the product workspace select Subscription Billing. If creating a new product, choose Product type Subscription first.
Select the schedule
Choose Subscription billing schedule. Its amount and frequency are copied into the product. Inspect the displayed price and interval/unit for an exact match before enabling.
Save the product
Save and reopen it. An enabled recurring product requires a valid enabled schedule, positive price/interval and matching frequency. Saving a product configures future purchases; it does not create a Product Renewal by itself.
Verify a customer purchase
Complete the configured checkout
Quote and purchase the subscription for the correct AccountID using the normal order/payment procedure. Review the recurring description on the line item before payment.
Inspect the customer record
After fulfillment, open the resulting renewal/subscription link or find it in
/product-renewals. Verify account, product, amount, environment, lifecycle state and Next Billing.Keep plan changes separate from live lifecycle changes
Changing product/plan setup is not proof that existing gateway subscriptions changed. Use the lifecycle operations guide for an existing customer’s billing.
Fields & records
| Field / record | Meaning or use |
|---|---|
| SubscriptionPlan | Reusable billing terms: amount, currency, interval/unit, cycles and optional trial. |
| Product | The sellable item and its selected schedule; configuration for future checkout. |
| ProductRenewal | Customer-specific lifecycle record created/managed through subscription operations. |
| SubscriptionPayment | Payment history, not the schedule itself. |
Verify the result
- Enabled product amount and cadence match its enabled schedule.
- No customer renewal is assumed until the purchase/creation operation succeeds.
- The customer record has the intended account, environment and billing lifecycle.
Troubleshooting
| What you see | What to check or do |
|---|---|
| Product price and billing frequency must match | Reselect the correct plan and verify all three values before saving. |
| No renewal after saving a product | Expected: product setup is not subscription creation. |
| Existing customer still has old terms | Use explicit lifecycle operations; a plan edit is not a verified remote update. |
Version & scope
Procedure checked against current Feeding Frenzy forms and services. Source verification is not a claim that a live payment, message, customer transaction or full operator run occurred.
Public guides describe shared controls, records and configuration boundaries using fictional data. Tenant URLs, credentials, customer records, provider identifiers and installation-only procedures belong in customer-controlled documentation and are excluded from public pages and search.
- Version
- 2.0.0
- Change source
- Current Feeding Frenzy forms/services plus reconciled Wiki topics
- Feedback key
guide:subscription-model
Feedback records only the page, guide ID and yes/no choice. It never records documentation search text.
Implementation references (3)
FeedingFrenzy.Admin/wwwroot/kScripts/SubscriptionPlans/SubscriptionPlansAdmin.ks.htmlFeedingFrenzy.Admin/wwwroot/kScripts/Products/Product.Edit.ks.htmlFeedingFrenzy.Admin.Business/CommerceSubscriptionOperations.Lifecycle.cs