How to Manage WISECP Package Features: A Guide to Free Showcase Logic and Comparison ...

How to Manage WISECP Package Features: A Guide to Free Showcase Logic and Comparison Tables

When you are building a hosting or server sales website with WISECP, package presentation matters just as much as pricing. The way you display package features on pricing cards, the number of features shown at first glance, and the relationship between those features and the comparison table can directly affect both usability and conversions.

According to the Datawise documentation, the Package Feature Builder is designed to generate JSON-based package features for product groups, display those features in pricing tables, and optionally use the same structure inside the Comparison Table component. The documentation also explains that you can define how many of the first features appear in the pricing card, assign a name, description, icon, and value type for each feature, and set the value type as either text or availability. It also states that a separate JSON output must be created for each package in a product group.

This is exactly where a recent support request raised a very smart suggestion: what if showcase features could be managed independently from the comparison table logic? In other words, some items could be shown as icon-only labels, some as plain short text, and some as icon plus text, without forcing everything into a strict text-versus-availability model.

That request makes perfect sense. The logic of a sales-focused pricing card is not always the same as the logic of a technical comparison table. On a pricing card, you may want to highlight quick, clean, highly readable labels such as “LiteSpeed,” “Free SSL,” or “Weekly Backup.” On a comparison table, however, you may prefer more detailed technical values, yes/no indicators, or extended descriptions. In the shared screenshot, the pricing cards clearly use short, easy-to-scan features at the top of each package, which shows that the showcase area is meant to help users scan and decide quickly.

So how does the current structure work?

In practice, because standard WISECP does not provide a separate native field for an independent showcase layer, the theme’s Package Feature Builder uses the same structured data for both product cards and comparison tables. The documentation confirms that the Comparison Table component requires this JSON structure and will not generate the table without it.

That means if you are using the comparison table, you should keep a certain level of consistency in package features. However, one important point is often overlooked: using the comparison table is optional. If you only want attractive package cards on your product pages, your structure can be much more flexible. Datawise documentation states that you can choose a default pricing table style in theme settings, use different styles for product packages inside FonPageBuilder, and override styling through a custom.css file that is loaded last.

This is why our support response recommended a practical workaround: use one of the existing package styles or create a completely custom product package style. The process is straightforward. You add a new style key to the package_styles array in theme-config.php, then duplicate one of the existing grid_ style files inside the builder/product-styles directory and adapt it for your own design. With that approach, the way package features appear in the product card becomes fully customizable. Since the custom style file belongs to your own setup, the risk of losing it in future updates is also lower.

What does this approach give you?

First, it allows you to turn the showcase area into a sales-driven summary instead of a rigid technical list. Second, it lets you present the same feature structure differently depending on the layout. Third, if you are not using the comparison table, you gain much more freedom in how your package cards look and behave. Fourth, you can build a package presentation that better matches your brand and your audience.

Still, the original support suggestion remains valuable: adding a truly independent “Showcase Layer” in the future would make the system even more user-friendly. It would allow store owners to decide which elements appear in the package card without being forced to mirror comparison table logic. For users who want cleaner and more marketing-oriented package boxes, this would be a strong improvement.

In short, the current Datawise and FonPageBuilder structure already offers a flexible way to manage WISECP package features, but if you want to fully separate showcase presentation from comparison data, the best current solution is to build a custom package style. When JSON-based package features, ready-made pricing styles, and custom styling are combined properly, the result can be both technically solid and commercially effective. If your goal is not just to list features but to sell packages, then the showcase area should be treated as a conversion tool, not just a technical checklist.