1. Open System Settings and Product Addons, then choose Add New Addon.
2. For a manually configured general addon, choose Independent Product. Use a predefined Add-On Feature only for the documented panel feature it supplies.
3. Enter the name and description, choose the welcome email and review whether the addon should appear during the initial order.
4. Configure its payment type, enabled cycles, prices and setup fees. Select Applicable Products so the addon is offered with suitable services.
5. If fulfilment is automated, configure the supported module and activation timing in Module Settings. If fulfilment is manual, assign an internal process for completing the order.
6. Save and test an initial purchase and a later purchase against an existing service.

An addon may use a different billing cycle or Next Due Date from its parent, especially when purchased later. If you enable prorata, verify the resulting alignment and first invoice. Explain any separately billed renewal in the customer-facing description.

Review Suspend Parent Product carefully. An overdue optional addon should only suspend the hosting service if that is the approved policy and customers are informed. A convenience feature and an essential licence may need different treatment.

Your company has an approved website-maintenance service that renews separately from hosting. A product addon can represent that separate billing and fulfilment record.

1. Open System Settings > Product Addons > Add New Addon.
2. Choose Independent Product for a manually configured general addon.
3. Enter the name Website maintenance and explain the approved work included.
4. Configure the actual payment cycle and prices, then select only the applicable hosting products.
5. Document manual fulfilment or configure its supported module.
6. Test a purchase with new hosting and a later purchase against an existing service.

Expected result: the addon has the correct due date and delivery process. Review whether an overdue optional addon should affect the parent hosting before enabling any parent-suspension behaviour.

Show on Order controls availability during the initial purchase, while Hidden and Retired have separate display effects. Hiding an addon is not a reliable way to prohibit all direct-link orders. Review the documented visibility behavior before using it to withdraw an offer.

Keep existing purchased addons and their renewal obligations in the change plan. After any pricing or module change, inspect an existing addon record and a new test order. Confirm that the correct remote feature is delivered and that cancellation of the addon has the intended effect on the parent service.

• Add and price WHMCS configurable options
• Configure recurring and one-time WHMCS product prices
• Set WHMCS suspension and termination automation deliberately
• Run an end-to-end WHMCS test order before launch

• WHMCS: create an addon
• WHMCS product addons
• WHMCS product configuration options

• Create recurring service addons in WHMCS