Manual Service integration guide
Manual Service connects supported other product modules workflows to LucidCP. Use this checklist to configure, link and validate the module before production traffic.
Procedure
Step-by-step
-
01
Plan the manual fulfilment workflow
Document what the administrator must create, which credentials or delivery notes the customer receives, and who owns suspension and termination. The Manual Service module has no remote API account or provider package.
Step 1 of 16 · Define the manual delivery checklist before publishing the package.Select the preview to inspect the full-resolution interface. -
02
Confirm the module is available
Open Developer → Modules & Gateways and verify that the Manual Service module is installed and available before creating a connection or product.
Step 2 of 16 · Confirm that Manual Service is available in Developer → Modules & Gateways.Select the preview to inspect the full-resolution interface. -
03
Add the local Manual Service connection
Open Infrastructure → Servers, add the Manual Service module and use its label to identify the fulfilment team or service type. No hostname, port or API secret is required.
Step 3 of 16 · Create the local Manual Service entry; it does not connect to an external provider.Select the preview to inspect the full-resolution interface. -
04
Confirm the manual module state
Save the connection and run its built-in check. LucidCP should confirm that no remote connection test is required.
Step 4 of 16 · Confirm that the local manual module is ready and requires no remote credentials.Select the preview to inspect the full-resolution interface. -
05
Set the fulfilment ownership
Use a dedicated server group only when it helps route manual orders to a specific operational team; otherwise link the product directly to the Manual Service entry.
Step 5 of 16 · Optionally use a server group to route manual orders to the correct team.Select the preview to inspect the full-resolution interface. -
06
Create the LucidCP product package
Open Products / Services → All Products, create a product category if needed, then select New Product. Use one LucidCP product for each package customers should be able to order.
Step 6 of 16 · Create the sellable LucidCP product package from Products / Services.Select the preview to inspect the full-resolution interface. -
07
Complete package details
On the Detail tab, set the package name, category, descriptions, visibility, stock and order limits. Keep the product hidden while the automation is being tested.
Step 7 of 16 · Complete the package identity, catalogue placement, visibility and ordering rules on the Detail tab.Select the preview to inspect the full-resolution interface. -
08
Describe the server features
On Server Features, add the customer-facing feature list and structured CPU, RAM, disk and traffic values used by storefront comparison tables.
Step 8 of 16 · Add package features and structured specifications exactly as customers should see them.Select the preview to inspect the full-resolution interface. -
09
Map the manual delivery module
On Automation Settings, select the Manual Service entry or its routing group. There is no provider-side plan identifier to enter.
Step 9 of 16 · Map the package to Manual Service without entering a provider package or API value.Select the preview to inspect the full-resolution interface. -
10
Require administrator fulfilment
Keep the product in the manual fulfilment path so a paid order appears for administrator action. Record the final hostname, username, password or delivery note on the service only after the work is complete.
Step 10 of 16 · Configure the product so paid orders wait for the documented administrator delivery process.Select the preview to inspect the full-resolution interface. -
11
Configure pricing and billing cycles
On Pricing, enter only the cycles you sell, choose the default cycle and set any one-time setup fee. Confirm currency and tax treatment before publishing the package.
Step 11 of 16 · Set recurring prices, the default billing cycle, setup fee and tax behaviour.Select the preview to inspect the full-resolution interface. -
12
Add options, requirements and upgrades
Attach optional add-ons, required customer inputs and valid upgrade targets where the package needs them. Do not duplicate values that the Manual Service module already controls automatically.
Step 12 of 16 · Attach only the optional add-ons, order requirements and upgrade paths required by this package.Select the preview to inspect the full-resolution interface. -
13
Save and verify the storefront package
Save the product, re-open each tab to confirm the values persisted, then inspect the customer store preview for the name, features, available cycles and order requirements.
Step 13 of 16 · Verify the completed package in the customer store before accepting a live order.Select the preview to inspect the full-resolution interface. -
14
Run a controlled manual order
Place a non-production order, complete its invoice and confirm that it reaches the manual fulfilment queue without attempting an external API call. Complete the checklist and activate the service from the admin workspace.
Step 14 of 16 · Confirm that the paid test order enters the manual delivery workflow and can be completed by an administrator.Select the preview to inspect the full-resolution interface. -
15
Verify customer delivery
Open My Services in the customer workspace and confirm that the delivered Manual Service service, credentials, status, usage information and supported actions are shown correctly.
Step 15 of 16 · Check the delivered Manual Service service and its available customer controls.Select the preview to inspect the full-resolution interface. -
16
Monitor provisioning after launch
Review the module queue, failed jobs, activity log and provider log during the first production orders. Correct the underlying mapping or provider error before retrying a failed action.
Step 16 of 16 · Follow provisioning jobs and investigate any failed module action before retrying it.Select the preview to inspect the full-resolution interface.
Checklist
Best practices
- Start with the smallest API permission set and expand only when a documented action requires it.
- Rotate provider credentials regularly and immediately after a suspected leak.
Reference
Module details
- Integration
- Manual Service
- Category
- Other Product Modules
- Availability
- Included with licence
- Directory page
- View integration profile
