The OVH VPS module sells OVHcloud VPS: new client orders are placed on your OVH account automatically (auto-paid), or you can link VPS you already own. This article covers getting the module ready to sell; day-to-day operation is in OVH VPS — Service Management.

1. Install the module

Upload ovh_vps to components/modules/, then go to Settings > Company > Modules > Available and click Install on OVH VPS.

2. Add an OVH Account row

On the module's Manage page click Add OVH Account and fill in:

• Account Name — a label for your own reference.
• Endpoint — ovh-eu, ovh-ca, ovh-us, kimsufi-eu/ca or soyoustart-eu/ca.
• OVH Subsidiary — e.g. FR, DE, GB, CA, US; must match the endpoint.
• Application Key / Application Secret / Consumer Key — see OVH API Credentials, Endpoints & Subsidiaries for minting a token with rights on /me/*, /order/*, /vps/*, /ip/*, /services/*.

The connection is validated against the OVH API before the row saves. Add one row per OVH account/endpoint you sell on.

3. Create packages

Add the module row before creating packages — the package fields load live from the OVH catalog through it. Under Packages > Add Package select module OVH VPS and set:

• VPS Plan — the OVH plan ordered when a client buys this package.
• Datacenter — where new VPS are deployed.
• Default OS Image — the operating system installed on new VPS.
• Options Margin (%) — your markup on OVH addon prices (paid OS, upgrades). Example: 20 sells a 10.00 OVH option for 12.00. See Packages, Margin Pricing & Configurable Options.

Assign the package to an order form as usual.

4. Verify the cron tasks

Under Settings > Company > Automation (Module tasks) confirm both tasks exist and are enabled:

Pending services never activate without a running Blesta cron.

Heads-up: a real, auto-paid OVH order is placed for every new client order. Test the full flow by importing an existing VPS first (see the management article) before opening the package for sale.