WHMCS ships seven order form templates. Standard Cart and Nexus Cart suit any product. Premium, Pure and Supreme Comparison, Universal Slider and Cloud Slider put plans side by side and can show product group features. Pick one as the system default, override it per product group, and customize by building a child template that names a parent in theme.yaml.
A WHMCS order form template is the folder inside /templates/orderforms/ that draws the shopping cart: the product list, the configuration step, the cart and the checkout. It is separate from the system theme, which draws the rest of the client area. One install can run several order form templates at once, one per product group.
Everything below is checked against the WHMCS 9.1 documentation, read on 19 November 2026. The documentation home page lists 9.1 as the General Availability release, with 9.0 and 8.13 on Long-Term Support and anticipated end-of-life dates of 31 December 2026 and 31 January 2027. Choosing and setting a shipped template works on any install. Customizing one does not: every order form customization page opens by saying WHMCS Cloud does not currently support the method.
Which order form templates does WHMCS ship with?
Seven, and the Order Form Templates page describes each in a line. Two are general purpose and five exist to compare plans. The page also records how many products each is drawn for, the number that settles most of these choices.
| Order form template | What the documentation recommends it for | Group features | Products |
|---|---|---|---|
| Standard Cart | The default template. Any type of product. | No | 3 |
| Nexus Cart | An improved template with a dynamic interface. Any product. | No | 3 |
| Premium Comparison | Comparing several products. | Yes | 3 |
| Pure Comparison | Comparing several products. | Yes | 4 |
| Supreme Comparison | Comparing several products. | Yes | 6 |
| Universal Slider | A slider for any product type, with percentage bars per feature. | Yes | 4 to 8 |
| Cloud Slider | Comparing products. Best with four feature comparisons each. | Yes | 2 to 12 |
All seven support headlines, taglines, feature highlights and featured products, so those are not a reason to pick one. The Bootstrap note on that page names Six and Twenty-One as the themes compatible with all of them. The Nexus Cart is part of the Nexus theme, which arrived in WHMCS 9.0.
How do you choose the right order form template for a product group?
Count the plans in the group, then decide whether a visitor has to compare them. The rest follows.
In words: a group nobody compares, such as one license or one managed service, takes Standard Cart or Nexus Cart. More than six plans takes Cloud Slider, the only shipped template documented up to twelve. Want a slider rather than columns, with at least four plans? Universal Slider, which the documentation puts at four to eight. Otherwise Supreme Comparison above four plans, Premium or Pure Comparison at four or below.
Two things narrow the field further. Product group features, the feature list you attach to a whole group, only render in the five comparison and slider templates. And the Ordering page says the Sidebar Toggle Option setting, which shows the Show Menu link and the category sidebar, applies to Premium Comparison, Pure Comparison and Cloud Slider only.
Where do you set the WHMCS order form template?
In three places, and they override each other in a fixed order.
| Where you set it | Path | What it covers |
|---|---|---|
| System default | Configuration > System Settings > General Settings, Ordering tab, Default Order Form Template | Every group with no template of its own, plus View Cart and Checkout for everyone. |
| Product group | Configuration > System Settings > Products/Services, edit the group, Order Form Template, Use Specific Template | Product selection and the configuration step, for that group only. |
| URL parameter | ?carttpl=directoryname on your WHMCS URL | That visitor's whole visit. It beats both settings above. |
The sentence behind most confusion appears in the documentation twice: View Cart and Checkout always use the default order form template, because a cart can hold products from several groups at once. A per-group template changes the product list and the configuration step, and nothing after. Change the Default Order Form Template gives the click path for both settings.
One trap lives on the group, not the template. The Product Groups page warns that when an order holds items from several groups, only the payment gateways all of those groups share will appear. Two groups with none in common leave the customer unable to pay.
How do you preview an order form template before clients see it?
Append ?carttpl= and the template's directory name to a cart URL. The Preview a Template page documents that parameter, and ?systpl= for system themes, with a cart example in this form:
https://www.example.com/whmcs/cart.php?carttpl=newtemplate
Use the directory name, not the display name in the dropdown. The parameter outranks both settings and holds for the rest of that visit, so walk every step: the one you are judging may be a step the template does not own.
WHMCS compiles templates into templates_c. The System Cleanup page says template changes need those cached files cleared through Empty Template Cache at Utilities > System > System Cleanup, and that /templates_c must be writeable.
How do you write product descriptions a comparison cart can read?
One feature per line, in the form Feature: Value, in the product description field. That is the whole format. The comparison and slider templates parse those lines into the feature rows the documentation calls feature highlights.
Disk Space: 1000MB
Bandwidth: 5GB
Email Accounts: 5
Subdomains: 3
Addon Domains: 1
WHMCS recommends the same features, in the same order, for every product in a group, because columns only line up when every product offers the same rows. The Universal Slider entry asks for one description format across the group so the page does not shift as a visitor moves between products.
If a description needs HTML instead, the highlights have to go. Disable Feature Highlights documents the edit: in products.tpl, remove the {if $product.featuresdesc} block and the {foreach $product.features} loop, and put {$product.description} in their place. Make that change in a child template, never in the shipped folder.
The group itself carries a headline, tagline, icon and feature list on the group edit screen. My guide to WHMCS configurable options covers what the configuration step shows once a plan is chosen.
How do you create a child order form template that survives updates?
Make a folder, give it a theme.yaml that names a parent, and copy in only the files you change. Create a New Order Form Template and the developer page on Order Form Templates give the same four steps.
- Create a folder in
/templates/orderforms/. The name must be alphanumeric, all lowercase, and may use underscores. It becomes the template name. - Add
theme.yamlwith at leastconfig:and, under it,parent: standard_cart. - Copy from the parent only the
.tplfiles for the steps you are changing, then edit the copies. - Select it in the Ordering tab or on a product group.
Premium Comparison is the shipped proof that this works: the documentation says it consists only of a products.tpl file, with every other step coming from Standard Cart. Each file you copy stops receiving the parent's fixes, so copy as few as you can. The Custom Order Form Templates page lists every cart file and what it draws, and my guide to the WHMCS theme structure covers the folder layout.
The Theme Configuration File page lists the other keys: name, the label shown in the Ordering tab and the group dropdown, plus description, author, dependencies and provides. WHMCS compares dependencies against provides each time you pick a system theme in the General tab, and an unmet dependency is what produces the compatibility error the Ordering tab displays.
For a template you plan to keep for years, start from Git. Create Customizations with Git says to clone the matching repository from the WHMCS GitHub account so each release arrives as a diff you can merge. Reading that account today, the only cart repositories are orderforms-standard_cart and orderforms-nexus_cart, so a child of a comparison or slider template is a manual job at update time.
How do you restyle the cart without touching template files?
Through a css/custom.css file. The CSS Styling page recommends creating one instead of editing the shipped stylesheet, because it loads after the stylesheet it overrides and WHMCS updates leave it alone. In the Standard Cart repository, common.tpl loads the cart stylesheet and then custom.css after it when that file exists. For color, spacing and type that is the whole job, and it leaves one small file to carry forward instead of a frozen copy of the cart.
The Nexus Cart is a special case, and the limit matters before you choose it. The Nexus Cart page describes it as a single-page application for the domain registration, results and cart pages, introduced in WHMCS 9.0, and states that the layout of those pages cannot be modified. What you get instead is a documented set of CSS variables in templates/nexus/css/custom.css for color, rounding and font size, and those values reach the cart as well as the client area.
So the trade is real: Nexus Cart gives a cart you can recolor in minutes and cannot restructure, Standard Cart one you can rebuild step by step. That decision belongs at the start of a WHMCS theme customization job, not halfway through one.
What do you check before the new order form goes live?
Walk a real order through it. This is the list I run before switching a store over.
- Preview with
?carttpl=and complete a test order through to the completed page. - Check View Cart and Checkout, which use the system default, not the group template.
- Put items from two product groups in one cart and confirm a gateway is still offered.
- Read every description for stray lines not in
Feature: Valueform. - Open the group page on a phone, where collapsed sidebars and sliders behave differently.
- Empty the template cache, then load the cart once as a logged out visitor.
- Check conversion or affiliate tracking inside the
{if $ispaid}block incomplete.tpl.
That last one catches people, because the tracking sits in a file the new template may not own. My WHMCS and Google Tag Manager guide covers what belongs in that block.
When is a custom WHMCS order form the wrong call?
When a shipped template plus CSS would do, and when the change you want is not a template change at all.
- Layout you cannot reach. On the Nexus Cart the single-page screens are fixed. No child template changes them, because the markup is not in a
.tplfile you own. - Pricing display. What the cart shows is set by the product and by settings. Monthly Pricing Breakdown in the Ordering tab divides longer cycles into a monthly figure store-wide.
- Logic, not layout. Anything conditional belongs in a hook, not in PHP inside a template. My WHMCS hooks guide covers where those files go.
- Update cost. Every file you copy is a file you maintain. A cart forked whole is a cart someone diffs by hand at each release.
- Smarty 4. WHMCS 9.0 removed the
{php},{include_php}and{fetch}tags. An old third-party cart that uses them will not render. My WHMCS 9 upgrade guide covers it.
I have no measured figures on what any of these templates does to conversion, and I will not invent any. The honest test is your own: switch one product group, leave the rest alone, and compare over a long enough period. My WHMCS services page sets out the wider build work.
What else do people ask about WHMCS order form templates?
Can I use a different order form template for each product group?
Yes. Edit the group at Configuration > System Settings > Products/Services, tick Use Specific Template and pick one. It draws the product list and the configuration step for that group. View Cart and Checkout keep the system default, so the cart can look different from the page the visitor arrived on.
Why has my order form template not changed?
Check in this order. The group may have its own template, which overrides the default. The step may be View Cart or Checkout, which always use the default. A ?carttpl= link may have pinned a template for your visit. And compiled templates are cached, so clear Empty Template Cache at Utilities > System > System Cleanup.
Which order form template is best for hosting plans?
For three or four plans side by side, Premium or Pure Comparison matches the documented product counts. For a longer list, Supreme Comparison goes to six and Cloud Slider to twelve. WHMCS publishes no conversion data on any of them, so treat these as a fit for the number of plans you sell.
Does WHMCS have a one page checkout?
Not as a shipped order form template. The closest in the box is the Nexus Cart, documented as a single-page application for the domain registration, results and cart pages. A true single-step checkout means a third-party template or custom work, re-tested against each WHMCS release.
Does WHMCS Cloud support custom order form templates?
No. Every documentation page covering them opens with the same note: WHMCS Cloud does not currently support the customization method. On Cloud you choose among the shipped templates.
If you want a cart built or rebuilt rather than picked, I take that on as WHMCS development work, with a free scoping call of about 30 minutes and a written quote within one business day.
Last reviewed 19 November 2026. Disclosure: I am a freelance WHMCS developer and I sell WHMCS theme and cart customization, so I am not neutral. I am CTO at ElySpace, a freelance developer for Marmaids LLC, and founder of WHMCSPilot and MagizAI. Template names, counts, settings, file names and version dates come from the WHMCS 9.1 documentation, the WHMCS developer documentation and the WHMCS GitHub account, read on 19 November 2026.