Offer customer-selectable VM specifications through the module’s Products page. Review the generated choices and your own pricing before making the offering available.

Prepare the saved product

Save a product using PD Google Compute Engine, the intended server group and explicit resource defaults. The catalogue can use cached data or a shipped fallback. Its machine-type list is filtered, its OS list is curated, and the presence of a choice does not establish capacity or quota for an order.

Generate and review all five dimensions

1. Open PD Modules → GCE → Products and find the intended product.
2. Choose Generate options if no generated group exists. For an existing group, review the Rebuild from live catalog confirmation first.
3. Inspect Region & zone, Server plan, Operating system, Disk size and Snapshots you can keep. The reviewed generator writes all five dimensions, even if some are hidden.
4. Review the disk-size dropdown. It is not a free-form per-GB slider, despite older descriptions. The default visible selection includes zone, plan, OS and snapshot allowance; disk size starts hidden.
5. Open System Settings → Products/Services → Configurable Options to edit the group’s choices and your own prices. The product’s Configurable Options tab attaches groups rather than serving as the full pricing editor.
6. Check each billing cycle and currency, then preview the effective specification, snapshot allowance and total before opening the product for orders.

The generated disk and snapshot choices need review even when hidden. Do not assume they automatically match the values entered under Disk size (GB) or Included snapshots in Module Settings.

Change visibility separately

Use the product’s checkout-dimension controls and choose Save visibility to change which dimensions customers see without rebuilding prices. Read the result and inspect the saved choices and actual order form.

Generated selections can override module defaults. Confirm a zone and machine type that work together; the catalogue’s combined lists are not an automatic deployment test of every combination.

Treat rebuilding as a replacement

Rebuild from live catalog rewrites the generated choices and resets prices to defaults. Record custom choices and prices first, and consider the references used by existing services. Rebuilding is different from saving visibility.

Generating options does not create a VM or choose the intended automatic-setup trigger. If a write outcome is uncertain, inspect the existing group and the last operation result before generating again. Keep the existing group until that outcome is clear. Do not include provider credentials or customer billing data in shared screenshots and examples.

See the PD Google Compute Engine WHMCS guide for related setup, or explore PD Google Compute Engine.