LucidCP connects your product catalog, payment state and hosting panel so automated hosting provisioning follows the rules you configure. Map the package once, test the complete order flow and give customers access through their service page.
A storefront package name is not enough to create a hosting account. The order needs a server, a compatible module and the exact provider-side package. LucidCP brings that mapping into product settings, alongside pricing, requirements and optional add-ons.
The product defines the offer customers buy: its name, billing cycle and configuration. The service is the customer-owned instance created from that offer. Keeping the distinction clear helps operators trace activation problems without changing every customer on the same product.
Assign a server directly or choose a compatible server group. The selected module determines which fields appear. Review credentials, provider permissions and connectivity before accepting orders; a successful payment cannot repair an unreachable hosting panel.
Enter the provider package identifier exactly as the panel expects it. For example, the cPanel product screen includes a cPanel Package field and optional resource settings. Plesk and DirectAdmin use their own mapping rules, explained in their integration guides.
The product automation screen offers automatic provisioning after payment, or a flow that requires staff approval. Choose the behavior that fits the product and test both the invoice state and resulting service state before making the product public.
An order, a paid invoice and a created account are separate checkpoints. Review the order timeline and module result when they disagree. Check whether the provider already created an account before retrying, so a temporary response failure does not lead to duplicate work.
After activation, the customer opens My Services to find the purchased product and available controls. Supported hosting modules may expose panel access or account details. The exact controls depend on the integration, so verify the customer view as part of your launch test.
Use a hidden test product and a controlled server account. The screenshots and field-by-field instructions in the linked guides show the operator side of this workflow.
Create the server connection under Infrastructure, select the hosting module and verify its API access. Use the provider-specific guide for required permissions and connection fields.
Set the storefront category, product name, billing cycle and price. Add requirements or configurable options only when the selected module can use those values.
Open Automation Settings, choose the server or server group and enter the provider package. Decide whether paid orders activate automatically or wait for approval.
Complete checkout using an appropriate test payment flow or a reviewed test invoice. Verify the order, invoice, provider account and service status together.
Open the customer view, confirm panel access and review the welcome information. Document failure handling and test supported lifecycle actions on the test account before launch.
Successful automation means the customer receives the intended service with the correct limits. A green connection test alone does not verify package names, billing behavior or the customer experience.
Compare supported operations and setup requirements on each integration page. Your provider account and panel license are configured separately from LucidCP.
It connects an accepted order and payment workflow to the hosting module that creates the customer account. LucidCP supplies the product mapping and service record; the external hosting panel performs the supported account operations. Both sides must be configured.
Yes. The product settings distinguish automatic provisioning from an approval-based flow. Test the setting with a non-production order and make sure your team understands which products still require a manual review.
Payment completion and provider account creation are different operations. Check the module response, provider access, package mapping and available capacity. Confirm the actual account state at the provider before retrying a failed action.
No. Lifecycle commands and customer controls vary by integration. Check the specific module page and test the operations your business requires; the presence of a module does not mean every provider feature is available.
The order-to-service model also applies to supported virtualization integrations, but a VPS needs platform-specific resources and template settings. Use the VPS automation page and the guide for your virtualization platform rather than copying hosting package settings.
Hi! Need help with plans, installation, or licensing?
Help Center Open a Support Ticket Integrations
