Skip to main content

What this page is for

The Packages page is where you set up the actual products your customers can buy – things like hosting plans, VPN plans, game servers, or any other service you sell. Packages are organised into groups, so you can keep related products together on your website (for example “Web Hosting”, “VPN”, or “Game Servers”).

What you’ll see

  • Groups – Each group is a section that contains one or more packages.
    • Add Package: Add a new package inside this group.
    • Edit Group: Change the group’s name or settings.
    • Hide Group: Temporarily hide this entire group from customers.
    • View Link: Get a direct link to this group on your site.
    • Delete Group: Remove the group (and stop showing any packages under it).
  • Packages inside a group
    • Each package row has actions like Edit, Delete, and View Link, letting you adjust or preview individual packages.
For most teams, the usual flow is:
  1. Create one or more groups (for example “Shared Hosting”).
  2. Use Add Package in a group to add each individual plan you want to sell.

Adding a new package

When you click Add Package, you’re taken to a form with a few sections. Below is what each part does, in plain language.

Package info

This is the basic information your customers will see.
  • Package name
    The name of the product your customers will see (for example “Starter Hosting”, “WireGuard 100GB”, “Minecraft Basic”).
  • Description
    A rich text description that appears on the order page. This is where you explain what’s included, who it’s for, and any limits.
  • Theme
    • E‑commerce view – A richer, more “store‑like” layout for the product.
    • Simple – A cleaner, text‑focused layout. Choose whichever fits your brand and how much detail you want to show.
  • Tax class
    Controls how tax is applied to this package:
    • Nontaxable – No tax will be added.
    • Any other entry – Uses one of your configured tax classes.
  • Trial period
    Number of days a customer can use the package before the first payment is taken. Leave at 0 if you don’t offer a trial.
  • Quantity
    How many units you have available, if you want to limit stock. For digital services this is often left high or unlimited; for capacity‑limited services (for example a small node) you can use this as a stock counter.
  • Out of stock
    When turned on, the package is treated as unavailable so new customers can’t order it.
  • Featured
    Marks the package as a featured plan. This is usually used to highlight a recommended or best‑value option on your website.
  • Prorate
    When enabled, BillingServ will align the first invoice to your billing date (instead of charging a full period immediately), which is useful for customers joining mid‑cycle.
  • Exclude from API
    Hides the package from the public API. Use this if you want a package available in the admin but not visible to custom storefronts or integrations.

Product images

You can upload images that represent the package (logos, screenshots, marketing visuals).
  • Supports multiple images.
  • Only standard image types (JPEG, PNG, GIF, WebP) are allowed.
  • Images are shown on the package page and can help customers quickly understand what they’re buying.

Attachments

Attachments are files that customers might need after ordering, such as:
  • PDF guides
  • Terms and conditions
  • Setup instructions
You upload files here once, and they’re stored with the package so customers can access them later.

Billing cycles

Packages can have one or more billing cycles. For example:
  • Monthly
  • Yearly
  • One‑off setup
For each billing cycle you configure:
  • Price
    The recurring price for that cycle (for example the monthly fee), shown in your default currency.
  • Setup fee
    A one‑time cost charged when the package is first ordered (for example an installation or onboarding fee).
  • Billing cycle
    How often the customer is billed. Options include:
    • One‑off
    • Daily / Weekly / Fortnightly
    • Monthly
    • Every 2, 3, 6, 12 months
    • Longer terms like 24 or 36 months
You can add multiple cycles so customers can choose between, for example, monthly and yearly billing on the same package.

Package options

This section links the package to any Package Options you’ve already created (like extra RAM, storage, or add‑ons).
  • Select one or more options to show on the order form for this package.
  • Customers will then be able to pick from those extras when they order.

Integrations (automation)

If this package is tied to an external system (like a hosting control panel, VPS platform, or game server panel), you can connect it here so BillingServ can automatically create and manage services.
  • Integration
    Choose which system this package should provision to (for example cPanel, DirectAdmin, Plesk, Virtfusion, Virtualizor, or Pterodactyl).
Depending on what you pick, you’ll see different extra sections:
  • cPanel / WHM
    • cPanel server – Which connected cPanel server to use.
    • cPanel package – Which package on that server this product should map to.
  • DirectAdmin
    • DirectAdmin server – Which DirectAdmin server to provision on.
    • DirectAdmin package – Which DirectAdmin package to use for new accounts.
  • Plesk
    • Plesk server – Which Plesk server to connect to.
    • Plesk package – Which Plesk plan this package represents.
  • Virtfusion / Virtualizor
    • Server – Which virtualization node to use.
    • Package / Plan – Which plan on that platform to create when someone orders.
  • Pterodactyl Game Server
    • Pterodactyl server – Which Pterodactyl panel to use.
    • Server location – Where the server should live (for example a specific datacentre).
    • Game category (Nest) – The type of game (for example “Minecraft”).
    • Game type (Egg) – The specific game template.
    • Memory / CPU / Disk / Database limits – Resource limits that will be applied to new game servers.
If you’re not ready to connect automation yet, you can leave the integration fields empty and use the package as a purely manual product.

Using the Packages page day‑to‑day

  • Add or edit packages when you launch new products or change pricing.
  • Use Hide Group or Out of stock when you want to pause selling something without deleting it.
  • Gradually attach Package Options and Integrations as your offering and automation mature.