An inquiry catalog first, an online shop second
Most product themes assume a cart. RT-Theme 20's vendor description splits the job in two: if your medical or health items are "not suitable to sell online" and what you need is a catalog with a "price inquiry form", you use the built-in product catalog tools; if you do want to sell, you use the theme with WooCommerce.
That ordering matters when you plan content, because the two routes store the same product differently. A catalog entry carries specifications, photos and a request-for-quote path with no cart, checkout or payment gateway behind it. A sellable item lives in WooCommerce, where pricing and stock already have a home. Decide which one you are building before you type in a single product, since moving entries later is content work, not a settings switch.
The vendor frames the design around medical equipment, veterinary, laboratory, clinics and pharmacy, and ships three demos with colour skins in that range. Treat that as a starting vocabulary rather than a limit on what the catalog can hold.
What a showcase entry actually stores
The catalog is a custom post type, described in the feature list as custom product posts with "specially designed single product pages". The vendor names four controls that shape every entry: placement of the single product's top or left navigation, unlimited photos per product, and a choice of fullwidth, right sidebar or left sidebar layouts.
Those are editorial decisions, not decoration. Navigation placed at the top or the left changes how a visitor moves between items in the same category, which is what someone comparing three similar instruments actually does. Unlimited photos lets one entry show the device, its accessories, the labelling and a site-of-use shot instead of a single hero image. The sidebar option is per layout, so a dense specification page can drop its sidebar while a category landing page keeps one.
The vendor also says you can keep the default product page styling or build the page yourself, which sets the division of labour: the post type supplies the repeating structure and fields, the builder supplies arrangement.
38 modules, and why content-pulling modules matter most
The theme runs on WPBakery Page Builder, listed in the vendor's feature set under its former name Visual Composer, with 38 custom modules. The relevant ones for a catalog are those that retrieve existing entries rather than add ornament: showcase products, WooCommerce products, testimonials, team members and blog posts can each be placed on any page with what the vendor calls extended module options.
In practice a home page or a landing page can surface six catalog items, a carousel of client testimonials, and staff profiles without re-entering any of that content into the page itself. Edit the product once and the module reflects it. The vendor also lists one-click carousels for products, testimonials and blog posts with several layout options, plus drag-and-drop management for tabular content, accordions and icon lists — useful for spec tables and downloadable-document panels.
Rows are unlimited and can be styled individually or through the global colour sets, and Google Maps modules with multiple locations are listed for clinic groups or distributors with several sites. Slider Revolution is named as included, with built-in Content and Circle slider types described as quick to assemble.
Skins and global colour sets: one palette across every page
The vendor says demo content can be imported and pre-made skins switched "with a single click", and that a skin of your own can be built in the panel. Styling options cover managing all colours, changing the skin and creating a new one; typography settings expose Google fonts with controls for size and colour.
The global colour set is the part that earns its place on a catalog. When module rows inherit a shared set instead of carrying their own colours, a palette change reaches pages built months apart. That is the difference between a site you restyle once and one where every new page drifts away from the last one. The three demos exist mainly to show the intended medical and health range before you pick a starting point or a blank canvas.
Category browsing built into the widget set
Seven custom widgets ship with the theme, and two are written for catalog navigation: an expandable Category Tree and a Category List. On a nested catalog — imaging, consumables, laboratory glassware — an expandable tree in a sidebar does work a flat menu cannot, and it is a widget you drop in rather than a page you assemble.
The remaining five cover the surrounding site: Flickr, recent posts, popular posts, contact info and testimonials. Contact Info pairs naturally with the inquiry model, since a visitor who cannot add an item to a cart needs an address or phone number somewhere predictable.
The vendor lists WPML and Polylang compatibility, a master .po file and RTL support, and declares Contact Form 7 and Gravity Forms compatibility in the marketplace attributes, observed on 4 November 2026. Those matter if the inquiry form is your only conversion path. Separately, the changelog records a GDPR checkbox fix on the theme's default contact form, which suggests that form is the theme's own rather than only a plugin integration.
Where the package and compatibility claims stop
The feature list credits WPBakery and Slider Revolution as included items and attaches store prices to both. Those are vendor and marketplace statements about the ThemeForest package. Recent changelog entries also show those plugins updated release after release alongside an RT-Theme 20 Extensions plugin, which is a maintenance signal rather than proof of what any archive contains.
Compatibility attributes observed on 4 November 2026 declare WordPress 5.1.x through 7.0.x, WooCommerce 6.x through 10.x, plus WPML, Contact Form 7, Gravity Forms, WPBakery and Bootstrap 4.x. The latest changelog entry claims WordPress 7.1.3 and WooCommerce 11.2 support — beyond the range those attributes cover — so read the changelog for the recent picture and the attributes as the period they were recorded for. None of it has been tested against your PHP version, host or plugin combination.
The ThemeForest file list names PHP, CSS and JS files; a Sketch file of the home page design sits in the feature set for anyone matching a layout handed over by a designer. Demo images, the fonts actually in use and the exact wiring of the inquiry form are worth confirming in the vendor's documentation before you commit.
Questions & answers
Do I need WooCommerce to run the product catalog?
No. The vendor describes the built-in catalog tools as an alternative to the WooCommerce shop, with a price inquiry form standing in for a cart. The showcase post type, its single-product pages and the product modules are not described as depending on WooCommerce.
Does the theme support right-to-left languages?
The vendor lists RTL support alongside WPML and Polylang compatibility and a master .po file. Those are marketplace declarations from the vendor description, not the result of testing the theme against a particular translation plugin or locale.
Can an imported demo be styled without touching code?
The vendor's stated workflow is to switch pre-made skins from the theme panel or build a new one there, with colour and Google font typography controls. Module rows can inherit global colour sets, so palette changes reach pages built at different times without editing each row.
