Invetex

A settings hierarchy, not one options screen

Invetex's feature list spends its longest paragraph on the theme framework rather than the homepage design. The vendor describes a "Setting Inheritance and Override System" alongside 750+ customizer options and a custom theme options panel. Read together, those three lines describe a hierarchy: you set a value once at a broad level, and narrower levels can override it.

That matters for a consulting site because the sections do not behave alike. A services landing page, a case-study index and a quote request page may each need a different header treatment, a different colour emphasis or a different spacing rhythm. Inheritance gives you a way to keep the site coherent by default while breaking from it deliberately. The vendor's WordPress plugin description makes the same claim in different words, describing the ability to set individual parameters for different site sections and supported plugins.

What the marketplace text does not say is how deep the hierarchy goes or which settings can be overridden at which level. If your build depends on one specific override, check that setting in the theme's own options before committing to it.

Headers and footers are Elementor layouts

Many themes give you a header builder with a fixed set of toggles. Invetex's layout features instead state that you can customise header and footer layouts in Elementor Page Builder. If that is accurate, the site's chrome is edited on the same canvas as its pages, which removes the usual split between "design the page" and "configure the wrapper".

ThemeREX's own addon widgets extend that surface. Recent release notes describe a Layouts widget gaining responsive panel size and styling for the panel or popup container, the overlay and the close button, and a Layouts Cart widget gaining an option to hide a zero counter. Those are details you notice when a site has a persistent shop panel or a slide-out navigation area rather than a plain horizontal menu.

This is where Invetex differs from other Elementor-based corporate themes: the structural pieces are treated as editable layouts rather than theme settings. The trade-off is that whoever maintains the site needs to be comfortable in Elementor, since the header is no longer a screen you can change without touching the builder.

The consulting modules: appointments, quotes, projects and events

Below the framework sits the working content. The vendor lists booking appointments, advanced contact and request-a-quote forms, premade project and services modules, event management, and a WooCommerce store as the theme's business features. For a consultancy, that combination covers the two common intake paths: a booked call and a written brief.

The description does not say which demos use which module, or how the booking and quote flows are wired to their underlying plugins. Treat the feature list as a statement of what is available to build with, not a promise that a fully configured booking system appears after import. Projects and services are described as modules, so expect to place and populate them rather than inherit a finished taxonomy.

The plugin list gives a sense of intended partners: Quickcal appears alongside contact form and event plugins, The Events Calendar is named, and WooCommerce appears with wishlist and product-filter tooling in the addon changelog. Those names indicate direction, not a required-set checklist for every layout.

Gutenberg is supported, but Elementor is the canvas

The marketplace attributes record Gutenberg Optimized as Yes, and the theme's changelog backs that up with concrete work: an option to choose whether styles load into the Gutenberg editor through add_editor_style or enqueue_style, plus fixes for fonts, icons and the editor styles wrapper. So block editing is not a fallback state you should assume is broken.

Still, the feature list puts Elementor at the centre: page content, header and footer all pass through it, and Marketplace attributes observed on 4 November 2026 list Elementor and Elementor Pro as compatible. If your team writes in blocks and only occasionally opens a builder, plan for the theme's presentation layer to live in Elementor anyway.

The same attribute record lists WooCommerce 6.x.x and WPML, and a WordPress range running from 4.9.x through 7.0.x. Those are declared compatibility lines from the vendor, not results of our own testing, and the upper end of that range moves with releases. Confirm the version you actually run before relying on it.

What the changelog says about upkeep

ThemeREX publishes long, specific release notes, and the recent entries are more informative than a feature list for judging maintenance. Version 2.25.0 records a batch of security fixes in the addon layer: a potential server-side request forgery path through SVG images loaded by URL, stored cross-site scripting in Elementor background text, presets and an Instagram widget, and PHP object injection in the addon's settings decoder. Version 2.24.0 added WordPress 7.0 compatibility styles and hardened AJAX handlers, and 2.22.0 lists PHP 8.5 compatibility.

Alongside security work, the notes show mobile behaviour being repaired: an iOS submenu that closed immediately after tapping its parent item, keyboard focus looping in the mobile menu, and hash links no longer jumping to the top of the page. Those are small fixes that affect whether a consulting site's navigation actually works on a phone.

The vendor also states plainly that images used in the live preview belong to their respective owners and are not included in the template. Budget for your own photography of people, offices and case studies; on a consulting site the portraits and meeting-room shots carry much of the credibility that layout cannot.

Questions & answers