Create an app-hosting product that defines the region, instance plan and instance count a customer receives. Each intentionally provisioned service runs one app with one web-service component from its public source.

Create the offering

1. Open System Settings → Products/Services and create the intended product in its product group.
2. Use Other Products/Services as the product type. In Module Settings, select PD DigitalOcean App Platform and the server group containing the intended account.
3. Set the Region, Instance plan and Instances defaults. Review Resource name prefix, optional Project, Client: Redeploy and Client: Change source.
4. Review Automatically setup the product and select the trigger that matches your order process. A saved product does not turn on automatic provisioning by itself.
5. Save the product before generating customer checkout choices.

If you want customers to submit code at checkout, add text custom fields named Repository URL and Branch to the product and show them on the order form. Otherwise the customer supplies the source from the service page after activation. These fields collect a public source reference, never a provider API token or repository password.

Review the app settings

Choose App Platform regions and plans from this module’s lists. App Platform region names are different from Droplet region codes. The catalogue can be cached or use shipped choices when DigitalOcean cannot be reached, so a listed choice is not a deployment-capacity test for your account.

The module limits instance count to 1–5. Some DigitalOcean plans support only one instance; do not offer a larger count simply because the quantity control allows it. Confirm that the plan and count you intend to sell are supported together.

Project groups the new app in your provider account; it is organisational, not a separate hosting plan or a completed-deployment check. The normal background process attempts that assignment after the app becomes live. Review the selected account and project together.

Review checkout and source collection

Use PD Modules → DigitalOcean App Platform → Products to generate and inspect Region, App plan and Instances choices. Review their visibility, selected values and your own prices in every term or currency you offer before making the product available.

A service without a usable source can show Waiting for source after activation. That is different from a failed provider connection: the customer still needs to submit a public Git repository or public Docker Hub image. The API token stays with the host’s provider connection.

Verify activation and deployment separately

When ready, use your normal authorised provisioning test. A real deployment creates chargeable DigitalOcean resources. Check Clients & Apps, the service page and Activity; keep the normal cron running for deployment progress. A completed order or Ready options label alone does not establish that the app is live.

After the first successful deployment, open the service’s live URL and check the expected application. If an earlier attempt has an uncertain result, reconcile the existing service and provider app before another create action. Keep tokens and customer data out of shared screenshots.

See the PD DigitalOcean App Platform WHMCS guide for related setup, or explore PD DigitalOcean App Platform.