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/*.
• When OVH Retires a Plan — hide the package, or keep it visible as out of stock. See Product Import, Margin Pricing & Configurable Options.
• Hide the OVH brand in option names — remove "OVH" from synced option labels and value names for a white-label storefront.

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

3. Import products (recommended) or create packages by hand

The fast path is the Import Products section on the module's Manage page: tick the OVH plans you want to sell, set the margin, the package group, the status and the billing terms, and click Import Selected Plans. Each plan becomes a package with the OVH name, a specification description, margin-applied monthly/yearly prices and its configurable options (location, OS, addons). See Product Import, Margin Pricing & Configurable Options for the details, including automatic import of new plans.

To create a package by hand instead, 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 — the default location for new VPS (clients can pick their own when the Location option is offered).
• Default OS Image — the default operating system (clients can pick their own when the OS option is offered).
• Margin (%) — your markup on OVH prices. Example: 20 sells a 10.00 OVH plan for 12.00.
• Offered Billing Terms, Price Sync and Offered Options — see Product Import, 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.

4b. Order form template (optional)

The suite ships an order-form template pack named OVH (plugins/order/views/templates/ovh/). Select it on the order form that sells your OVH packages: Packages > Order Forms > edit the form > Template: OVH.

The template keeps every Blesta order step and changes only the configuration step:

• Location shows one card per datacenter with the country flag, the city and the datacenter code.
• Operating System shows one card per image with its icon.
• The OVH add-on families (Snapshot, Automated Backup, Additional Disk, control panels) show as rows with their prices.
• A Your configuration panel shows the term, the selected options and an estimated total. The final total, with taxes, shows at checkout.

The cards work with the keyboard (Tab, Enter or Space). When JavaScript is off, the standard select fields show instead.

5. Welcome email and root password

The panel manages the root password for the client:

• OVH sends its own delivery email (with the first root credentials) to your OVH account address, not to the client. The client does not need it.
• When OVH delivers the VPS, the cron reinstalls the fresh VPS once with a panel-generated root password. The panel stores this password encrypted on the service.
• The client reads the password on the service page: Actions > Root Password > Show / Copy.
• The client can change the password at any time with Actions > Root Password (reset over SSH) or with the Reinstall tab (new OS, new password).
• The client does not need an email for the IP: the service page's IPs tab shows the live IPv4/IPv6 from OVH, and the VPS name (vps-xxxx.vps.ovh.ca) is a resolvable hostname.

Set each package's Welcome Email so the client knows what to do. The password and the service name become available at delivery, a few minutes after the order. If your welcome email goes out before delivery, point the client to the client area instead of the tags. A safe template:

Subject: Your VPS is being deployed

Hello {contact.first_name},

Thank you for your order. Your VPS is being deployed. Deployment usually completes in a few minutes.

1. Log in to the client area.
2. Open Services and select your VPS. The server name, the IP addresses and the controls appear there when deployment completes.
3. Open Actions > Root Password and click Show to read your root password. Change it at your first login.

If you need help, open a support ticket.

Admin note: the tag {service.ovh_vps_root_password} carries the managed password in service emails that render after delivery (for example a resent welcome email). The initial reinstall takes some minutes after delivery — the password works when that reinstall completes.