Two editing surfaces: Elementor for layouts, Unyson for site settings
The vendor describes Medizco as built with Elementor and bundled with ElementsKit for its Header & Footer Builder, Mega Menu Builder and Layout Library. Separately, the theme runs on the Unyson framework, and the changelog records that version 1.6 added a Medizco tab to it.
That split is the first thing worth knowing. A new header, footer or mega menu is an Elementor layout you build, not a preset you pick in the options panel. Site-wide settings such as colours and fonts live in Unyson behind its Medizco tab. When something needs changing, knowing which of the two holds it saves a hunt.
Elementor and Elementor Pro both appear in the compatibility list recorded on 4 November 2026, but the feature description points to the free builder plus ElementsKit rather than naming Pro-only widgets. Check the specific elements you intend to use before assuming a Pro licence is required.
The clinic components the changelog keeps returning to
Medizco ships content blocks aimed at a practice rather than at a generic business: a doctor slider and a services carousel. The release history is the clearest evidence that these exist as named components. Version 2.1 added an ordering option to the doctor slider and fixed a slider issue, 3.5.2 fixed dot navigation on the doctors slider, and 3.7 fixed the services carousel.
Recurring fixes cut both ways. They confirm the widgets are maintained, and they suggest looking closely at sliders and carousels with your own content before launch, particularly on an older copy of the theme.
Around them the vendor lists image, video and colour sections, parallax sections, smooth animation, Google Fonts, Font Awesome icons and a separate 200+ line-icon set. The attributes record four or more columns and high-resolution assets. These are pieces for a services grid, a team page and a location block, not a finished page structure.
Homepage and menu styles, and how they got there
The vendor lists 3+ home page designs and 3+ menu styles, and the changelog shows the set growing: version 1.4 added three more home styles, 1.5 added two homepages for COVID-19, and 1.3 added an RTL demo. Between them they show the theme has been applied to more than one presentation of a clinic, with a right-to-left starting point available.
Menu style is an early decision here rather than a detail to defer, because the header comes from the ElementsKit header builder. Choosing a style means choosing a header layout you then edit in Elementor, not switching a preset in Unyson.
One-click demo import arrived in 3.6.0, alongside a fix for broken demo templates. It gives you a clean starting copy of a homepage; the imported demo is a template to replace, not a finished site.
Meform handles the enquiry path
The vendor lists Meform as its own contact form builder and describes a working Ajax contact form with validation. That changes the most important pages on a clinic site: appointment requests, department-specific questions and general contact messages are built in a tool the theme supplies rather than added through Contact Form 7 or similar.
Whether that suits you depends on how far the form has to go. The vendor describes a builder and Ajax validation, but not booking, calendar or availability logic, so scheduling behaviour would need to come from a separate plugin. Compare Meform's field types against your actual intake process before committing.
Google Maps has a different setup path: the vendor says it is configured through data attributes, so a location map is a markup setting rather than a plugin option. Consent handling for embedded maps is not covered by the description.
WooCommerce is listed, but not described as a store build
The compatibility attributes name WooCommerce 7.x, 8.x and 9.x. That states integration, not shop design. The feature list and description say nothing about product templates, shop layouts or commerce widgets, so selling supplements, skincare or paid consultations means shaping those pages with WooCommerce itself.
There is one hint the shop pages were considered: version 2.6 fixed banner issues on the shop page and the product single page, which suggests both receive the theme's banner treatment. That is styling rather than conversion-focused design.
A compatibility list is a declaration, not a test record. If your store runs a WooCommerce branch outside the listed ones, check it on a staging copy first.
Versions, files and what they don't settle
The marketplace package attribute names PHP, CSS and JS files, and the vendor describes the build as Prepos and Sass based, which matters only if you plan to compile the stylesheets yourself. Documentation is marked Well Documented, and the theme is listed as responsive and widget-ready with high-resolution assets.
The declared WordPress range runs from 6.0.x through 7.0.x, and the browser list covers Firefox, Safari, Opera, Chrome and Edge. The vendor prose still mentions Internet Explorer in its cross-browser wording while the attribute list leaves it out, so the two statements do not match. Gutenberg Optimized is marked Yes; that says the block editor was considered, not that the Elementor layouts transfer into blocks.
The changelog closes on upkeep rather than features: 3.7.1 fixed a licence activation issue, and 3.7.3 addressed PHP deprecation notices and icon-library problems. On a theme with a licence-activation step, that history makes checking activation after an update worthwhile instead of assuming the site carries on untouched.
Questions & answers
Do I need Elementor Pro to build the header and footer?
The vendor describes header, footer and mega menu building through ElementsKit, which the theme bundles, and the compatibility list includes both Elementor and Elementor Pro. The description does not reserve layout building for Pro, but check whether any specific ElementsKit widget you need is gated before deciding on a licence.
Can Medizco take appointment requests?
Meform is the vendor's form builder, and the theme includes an Ajax contact form with validation — that is where an appointment request form would be assembled. The description does not promise booking or scheduling logic, so calendar and availability behaviour would come from a separate plugin.
Does an RTL starting point exist?
Yes. The changelog records version 1.3 adding an RTL demo, so a right-to-left layout is available as a starting point alongside the other homepage designs.
