Client fields describe the account, product fields describe an ordered service, and support-department fields describe a ticket. A server module may require a precisely named product field, so consult its documentation before choosing a more readable label.

1. For a client field, open System Settings and Custom Fields. For a product or support field, open the relevant product or department's Custom Fields tab.
2. Add the field name, input type and a short description explaining what to enter. Use a dropdown when a controlled list will prevent ambiguous values.
3. Select Admin Only, Required Field, Show on Order Form and Show on Invoice according to the field's actual purpose.
4. If validation is necessary, test valid, invalid, empty and international input. Avoid restrictive examples that reject legitimate modern domain names or customer details.
5. Save and preview the appropriate registration, product or ticket form using a test account. Check the administrator record and any resulting invoice or email.

Do not display internal routing values, private account identifiers or credentials on invoices. A Password field encrypts its stored value, but it still needs a justified purpose and controlled access. Prefer a supported secure access method over asking customers to place reusable administrator passwords in ordinary support text.

Product fields presented during ordering may be viewable afterwards without being editable by the client. Explain the support route for correcting a value that affects provisioning.

Your onboarding team needs to know whether a new hosting service is for a business website, portfolio or test project. Use a product custom field because the answer describes this service rather than the whole customer account.

1. Open the relevant product's Custom Fields tab.
2. Add a dropdown named Website purpose with the approved choices Business website, Portfolio and Test project.
3. Write a short description explaining how the answer helps onboarding.
4. Enable the intended order-form visibility and decide whether a response is required.
5. Place a test order and inspect the saved service field.

Expected result: staff receive a consistent service-specific answer. Leave invoice visibility off unless customers need the field on billing documents.

Inventory modules, email templates and invoice output that consume a field before renaming or removing it. A friendly display label can preserve a required internal name using the documented separator format. Existing invoice snapshots may retain earlier field data, so changing the current client record does not necessarily rewrite historical documents.

• Add and price WHMCS configurable options
• Create WHMCS support departments and staff access
• Customize WHMCS email templates and merge fields
• Configure WHMCS data retention using an approved policy

• WHMCS custom fields
• WHMCS product configuration options

• Collect service information with WHMCS custom fields