Offer storage choices that match the saved backend and intended plan. PD Object Storage generates quota, bucket allowance, versioning and placement options where the selected backend supports them.

Generate and inspect the choices

1. Save the product’s Backend and server group on Module Settings.
2. Open PD Object Storage → Products and locate that product.
3. Choose Actions → Generate options.
4. Review values and prices under System Settings → Products/Services → Configurable Options.
5. Check the product’s option-group assignment and actual order form.
6. Compare an accepted selection with the resulting service.

The product’s own Configurable Options tab assigns groups; it is not the global option-price editor. Record existing values and prices before regeneration and review them afterwards rather than assuming every edited choice was preserved.

Check backend-specific placement and features

Amazon S3 and Spaces use Region. R2 uses Data Location. MinIO does not generate a location choice because its deployment endpoint determines placement. Versioning is not offered for an R2 product.

Quota mode belongs to the product’s Module Settings. Max Buckets includes the primary bucket. A larger bucket allowance does not increase the plan’s total storage allowance, and offering a setting does not add an unsupported provider capability.

Verify defaults and billing separately

Review the product’s default quota, maximum buckets, versioning and default region/data location. A saved hidden checkout value can still reach the order and override an intended default; inspect the accepted value and resulting service.

Storage measurements do not themselves prove an overage invoice was generated. Review WHMCS billing configuration separately and use the usage interpretation guide before relying on a displayed figure. Do not change a live product’s Backend merely to regenerate another provider’s options.

See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.