Plans & WHMCS products

Plan-based billing with per-plan feature flags. Define hosting plans in the addon (or import them from a Plesk service plan), map each to a WHMCS product, and toggle exactly which features it includes.

1. Define or import a hosting plan

Open ImpulsePlesk → Plans & Products. You have two ways to create a plan:

• Define one — give it a slug, a name, the exact Plesk service plan name, and limits (disk, bandwidth, domains, subdomains, aliases, mailboxes, databases), and tick the per-feature checkboxes it includes.
• Import from a Plesk server — list the service plans on one of your registered servers and import one (name and limits), or type a plan’s exact name to import it directly.

Each hosting plan maps to a Plesk service plan name, which is what the module applies at provisioning and plan-change time; that Plesk service plan sets the quotas on the server. The module keeps its own copy of the limits for the client area — import the plan again (Update) to pick up limit changes made in Plesk. The limits live in the module, not in WHMCS configurable options.

Imported plans arrive all-on

An imported Plesk plan comes in with every feature enabled — trim the feature flags per tier before you sell it.

2. Set the feature flags

Each plan carries a set of per-feature flags that control which client-area tabs and actions a customer on that plan can use: email, databases, SSL/TLS, DNS editor, FTP accounts, PHP settings, scheduled tasks, log rotation, protected directories, applications, WordPress, Node.js, Git, backups, and restore.

Two gates, one truthful upsell

Every gated client-area tab needs both an active operator license and the plan’s feature flag. So a “not included in your plan” message is always accurate. Plans that predate the feature-flag system are treated as all-on, so existing customers never lose access.

3. Understand the license tiers

Which features you can offer at all is set by your ImpulseCore license tier:

Tier	Key prefix	What it enables
Licensed	IPLSK-	The full feature set — every plan feature flag can be offered. No server, plan or service limits.
Developer	IPLSKDEV-	Same features, capped for testing: 3 hosting services, 2 servers, 3 plans. Developer keys aren’t sold with the module.
No key (Standard)	—	Orders still provision, but every feature-gated client-area tab stays off.

Set the key in ImpulseCore → Modules & Licensing → Licenses; ImpulsePlesk reads the cached tier from Core. See Installation & activation for entering the key.

4. Wire a WHMCS product

Create a WHMCS product and point it at the module:

1. Go to System Settings → Products/Services and create a product (or edit one).
2. On the Module Settings tab, set Module: ImpulsePlesk.
3. Pick the Hosting Plan from the dropdown — that single field carries the plan’s limits and feature flags.
4. Leave the product with no required server group. The module resolves the target Plesk server itself, so a WHMCS server group is not needed.

Don’t add configurable options for limits

Disk, bandwidth, mailboxes, databases and domains all come from the hosting plan, not from WHMCS config options. The product’s only module setting is the Hosting Plan dropdown; the one configurable option the module reads is an optional Region (a configurable option or custom field), which pins the order to servers in that region.

5. Prove one provision before selling

Place a test order on the product and confirm the end-to-end flow:

1. When WHMCS runs the module’s Create command, it creates a Plesk customer and subscription, persists the service row, stores the FTP/system secret in Core, and attaches the service to a Core Project. If it is interrupted, the provision cron (every 2 min) retries it.
2. Open the service in the client area — the Managed Web Hosting dashboard should render scoped to the customer’s own domain and resources only.
3. Walk suspend → unsuspend → terminate (a non-destructive fence) → day-7 purge to confirm the lifecycle.