A reseller package is a defined allocation for an individual customer account. It should describe what that customer can use without relying on vague promises such as unlimited resources. Plan your packages around the parent reseller allocation and the type of websites you intend to host.
Recommended steps
- List the total storage, transfer and account allowance of your reseller plan. Reserve operating headroom for growth and support work rather than allocating every available resource on the first day.
- Create a small number of packages with clear limits for storage, transfer, mailboxes and databases. Where WHM is provided, use package names that remain meaningful if you later adjust pricing.
- Review the associated feature list separately from resource limits. A package quota defines the allocation; a feature list controls which control-panel functions are visible or available to the account.
- Test each package with a sample customer account. Confirm the displayed limits, website creation workflow and allowed tools. Check the backup and recovery scope instead of assuming that every account has an identical retention policy.
- Prepare customer-facing descriptions that match the actual package. Explain supported applications, migration limits and the contact route for assistance. Review your own allocation before accepting a workload that exceeds it.
Monitor actual usage and plan changes before customers reach critical limits. Avoid silently reducing an existing customer's resources when revising a package. Keep a record of which accounts use each package so that a planned change can be assessed and communicated accurately.
