Maintain a delivery record for every hosting plan so the website description, billing product and provider package agree. This record makes launches, upgrades and support decisions easier to review.
IN THIS ARTICLE
01 Build the plan mapping
Start with the public offer, then record the corresponding technical and billing settings. A useful mapping includes:
| Area | What to record |
|---|---|
| Commercial plan | Public name, billing product ID, cycles and approved prices |
| Provisioning | Module, provider connection, package name and resource limits |
| Client features | Control-panel access, enabled management tools and permissions |
| Operations | Backup scope, renewal owner, support scope and escalation route |
| Optional services | Separate charges, activation prerequisites and cancellation behaviour |
02 Validate each published claim
- Create a test service using the actual billing product and provider connection.
- Inspect the provisioned package and compare disk, traffic, account limits and permitted features with the plan record.
- Sign in through the customer workflow and test the tools included in the offer. Confirm that a hidden or disabled feature is not advertised as available.
- Check a nondefault billing cycle and an optional component. Compare the initial charge, recurring amount and delivered resource.
- Document any provider, platform or plan condition next to the relevant feature. Avoid treating a feature available on one control panel as universally available.
- Have the commercial and technical owners approve the same record before changing public copy or applying prices to existing customers.
03 Keep the mapping current
Review the record when a provider changes a package, a module adds a capability or a plan is retired. Preserve existing customer agreements separately from the current sales catalogue and confirm which services should receive a change.
Common questions
Can the billing product and provider package have different names?
Yes. The explicit module mapping matters. Record both identifiers so administrators do not choose a similarly named but incorrect package.
Does changing the public plan description update existing services?
No. Review and execute the supported provisioning or pricing change separately, then verify the affected services.