HostBill product forms collect order information and, for supported field types, let customers choose priced resources. Configure the visible choice, its price and its provisioning meaning together. A field that appears correctly in the cart is not automatically connected to a server limit.
IN THIS ARTICLE
01 Create a useful form field
- Open Settings > Products & Services, choose the order page and product, then open Components > Forms.
- Add a new field or copy a reviewed field from another product. Select the type that matches the task: text for information, a dropdown for one option, or a quantity control for a measured amount.
- Enter a clear field name and description. Mark it required only when the order cannot be fulfilled without it. Avoid asking customers for information that your existing account or service records already provide.
- Define the supported values, limits, default selection and prices. For a resource option, follow the provisioning module's documented mapping to the relevant server setting.
- Review cart and invoice visibility. Keep credentials out of ordinary invoice descriptions and use an appropriate protected field type when sensitive setup information is genuinely necessary.
- Decide whether customers may edit, upgrade or downgrade the field after ordering. Check upgrade fees, proration and any rule that prevents a promotion from discounting this component.
- Add conditional field logic only when it helps customers make a valid choice. Test each branch, including changing back from one selection to another.
02 Verify values beyond the cart
Order a nondefault configuration and compare the submitted form values, invoice lines and provider-side resources. Check whether the customer can edit a field after provisioning and what operational action that edit actually triggers. Document a manual fulfilment step if the selected module does not automate it.
03 Example: collect a HostBill onboarding preference
Your hosting company offers two agreed onboarding routes, self-service or assisted. Use an informational product field to capture the choice, then connect it to your documented fulfilment process.
- Open the product under Settings > Products & Services and choose Components > Forms.
- Add a dropdown named
Onboarding preference. - Use the values
Self-serviceandAssisted setup, with a description explaining what the selection means. - Set the approved default and visibility, then save.
- Place a test order using the nondefault value and inspect the saved product information.
Expected result: staff receive a clear fulfilment instruction. The dropdown does not itself perform assisted setup or change a server resource unless an integration has explicitly been configured to do so.
Common questions
Why was an option charged but not provisioned?
The price can work independently of the module mapping. Inspect the saved field value and the connected product configuration, then confirm that the integration supports the requested resource change.
Should I copy every field from a similar product?
Copying saves setup time, but inherited defaults, prices and hidden values may be wrong for the new offer. Review each field and test the combinations customers can actually buy.