Categories
Need a custom hosting configuration?
Now it’s easy (and insanely affordable)
to get help from an expert. Whatever you
need, our pros can handle it for you so
you can focus more on what matters …
growing your business.
Platforms
You dream it — we code it. Tap into 10+ years of Blesta, WHMCS & Paymenter development.
WordPress plugins are coming soon
WordPress add-ons are on the roadmap. Tell us what you need.
From custom embedded firmware to cloud
platforms and mobile apps — we design
and build complete IoT solutions
tailored to your needs.
Sell products as real bundles. Bundle Orders makes selected native Blesta addon packages mandatory when a customer buys a configured base package — the addon is pre-selected, labelled Required, and can't be removed. Addons remain real child services, so provisioning, renewals and cancellation stay 100% native to Blesta.
Pair any base package with mandatory addons — at normal price or included free — through Blesta's own validated order flow.
Staff create simple bundle rules under Tools → Bundle Orders; the plugin enforces them on every active order form using Blesta's own addon relationships.
Create a rule per base package under Tools → Bundle Orders and pick the addon packages that must come with it. Rules use Blesta's native package groups and addon relationships — no custom product types.
Required addons are ordered as genuine Blesta child services with the parent's service ID. Module fields, configurable options, provisioning, renewal and parent-cancellation behavior all stay native.
Charge the addon's normal base price, setup fee and option prices — or mark it Included so the base service price becomes zero while configurable options remain billable.
Required addons are enforced on standard, wizard and AJAX order forms — and domain forms when enabled. The addon shows as Required, pre-selected, and can't be switched to None.
If a customer skips the UI and jumps straight to checkout, the addon configuration queue is restored automatically — the bundle can't be dropped by manipulating URLs.
The addon's pricing schedule is matched to the base service's term and period, preferring the cart currency. Quantity mirrors the parent, and checkout is blocked when no matching term exists — no silent mispricing.
First configure the addon relationship using Blesta's normal package groups — each required package must be active and assigned to a native addon group linked to the base package's standard group. Then open Tools → Bundle Orders and add a rule that lists the required addons for the base package.
Normal addon price charges the addon's native base price, setup fee and configurable-option prices. Included makes only the addon's base service price zero — configurable options remain billable. Included packages must have zero native setup fees and must not enable package price override.
Yes. Each required addon is created as a native child service carrying the parent's service ID. Provisioning, module fields, configurable options and renewals work exactly as if the customer had added the addon manually, and cancelling the parent triggers Blesta's own child-service cancellation flow.
No. On the order form the addon is pre-selected, labelled Required, and can't be switched to None. If someone bypasses the UI and goes straight to checkout, the addon configuration queue is restored automatically.
No. Rules only affect future customer purchases made through active Order forms. They never backfill existing services and don't apply to services created by staff or through the API. Uninstalling removes only the plugin's own mappings — packages and services are untouched.
Blesta 5.13.10 or newer with the Order plugin installed. Bundle Orders is part of the SystemFreaks All Plugins Suite license. Terms and currencies must line up: checkout is blocked when the addon has no pricing matching the base service's term and period.
United States [$]
United Kingdom [£]
Canada[$]
Greece[€]