SpaLab

Therapist and procedure pages sit under the booking layer

SpaLab's feature list pairs "Therapists / Procedures Pages Included" with a "Reservation Plugin" and names a Spa Booking Calendar, reservations, appointments and gift cards in the same breath. That reads as a content model rather than a contact form: staff members and treatments become things you build pages around, and the booking layer is meant to attach to them.

"Included" carries less weight than it appears to. The description does not say whether the reservation plugin travels inside the theme package, arrives as a separate installer, or needs its own licence, and gift cards are not attributed to any specific component. If card revenue or online appointments are central to the launch, test that path on a staging copy before committing to a date.

Retail stock is handled by WooCommerce

The shop is described as WooCommerce, with the vendor naming homemade soaps, organic and ayurvedic products, creams, shampoos and nail lacquer as intended inventory. That means variations, stock counts and shipping — the parts a themed product grid cannot handle alone — are WooCommerce's responsibility.

Marketplace compatibility attributes observed on 3 November 2026 declare WooCommerce 5.x through 9.x, alongside Elementor, Elementor Pro, The Events Calendar, Events Calendar Pro and WPML. Those are seller and marketplace declarations, not a record of anyone installing SpaLab against each release. Because a treatment business often runs several plugins at once, the useful check is a staging site carrying your real stack, not the version list.

One theme, two builder changelogs

SpaLab is unusual in documenting two editing routes side by side: the vendor links a changelog for an Elementor build and a separate one for a WPBakery Page Builder version. The WordPress theme metadata carries the name "Spalab Elementor", and the feature list adds a visual shortcode generator and a theme options panel. The marketplace records Gutenberg Optimized as Yes, so the block editor is not excluded, though the described workflow leans on builders and shortcodes.

For a team that already works in Elementor, that is the natural route; a WPBakery shop can follow the parallel changelog. Decide before importing demo content, since the demo you import should match the builder you intend to maintain. The listing does not clarify how the two builds are packaged relative to each other, so confirm that against the current release rather than assuming both arrive together.

Preset skins and settings that reach past the page body

The vendor lists 20 preset skins plus unlimited colour variation, with customisation extending to the header, menu bar, buttons, footer and fonts, and 600+ Google Fonts for body text, header and menu. The practical value is carrying a brand palette through the booking buttons and the shop, not accepting the demo's own styling. The trade-off is drift: element-by-element colour settings reward restraint, and the presets work better as a coherent base than as twenty looks to mix.

The settings also cover column management for every page and post, with global defaults, and a sidebar manager that places the sidebar left, right or removes it for a full-width layout, either site-wide or per page and post. On a site that mixes wide treatment galleries with narrower blog posts, setting the sidebar rule per post type saves repeating the same choice page after page.

Images, documentation and what the declarations mean

The vendor states that the demo photographs are copyrighted and are not included for download, with purchase links offered instead. On a beauty site, imagery does most of the work, so treat the demo as a guide to spacing and composition and budget for your own shoot or stock licences before you build pages around pictures you cannot publish.

Other listed items — HD help videos, "well documented" status, widget-ready sidebars, high-resolution assets, and browser support from IE9 through Chrome — are seller and marketplace claims dated to the 3 November 2026 observation, not findings from a build here. The same applies to the booking flow, checkout and any WPML translation setup: walk each one through once on your own hosting with your own content.

Questions & answers