Clotya

Description writing moves into the product edit screen

Most of the repetitive work in a clothing shop is not layout. It is the same product record repeated: a title, a short line for the category page, a longer description with fabric, fit and care notes. Clotya's vendor description lists "Generate product descriptions using OpenAI ready" and "Generate product short descriptions using OpenAI ready" as theme features, and the changelog for version 1.4.6 pins down where they live — KLB AI integration adds "Generate Full Description (AI)" and "Generate Short Description (AI)" buttons to the WooCommerce product edit page.

That placement matters more than the feature name. You stay inside the normal WooCommerce editing screen rather than switching to a separate tool, and the generated text lands in the same fields you would otherwise type into. For a shop with hundreds of variations across colourways, the short description is the piece that usually gets skipped first, so having a draft button next to it is a practical shortcut.

The listing does not describe the prompt, the model, or whether the output responds to product attributes. Treat the buttons as a first-draft generator: read the result, correct fabric and sizing claims, and keep your own voice. Nothing in the evidence states that AI output is factually checked against your catalogue.

The same release line also brought a Brands A–Z list, search by product tags, and AJAX search that matches a variable product's SKU — smaller catalogue tools, but the kind that show development around product data rather than only around homepage blocks.

Two multi-vendor routes on the feature list

Clotya lists "Dokan (Multi Vendor Plugin) ready" and "WC Marketplace (Multi Vendor Plugin) ready". Two named routes is a deliberate claim: if you intend to run a marketplace where independent sellers list clothing, you can plan around either plugin rather than discovering after launch that only one is accounted for.

Read the word "ready" narrowly. The marketplace attributes do not name Dokan or WC Marketplace in the Compatible With field, and the ThemeForest file list covers PHP, CSS and JS files — theme files. No evidence says either plugin ships inside the theme, so budget for the plugin, its licence and its configuration as separate work.

If you are selling only your own stock, this section does not apply to your build. The two-vendor claim earns its place only when seller onboarding, commission rules and per-seller storefronts are part of the plan.

Order rules that change what a shopper can do

Several listed features act on the order rather than the layout, and together they shape buying behaviour without a custom plugin.

Min/Max Quantity Option sets quantity limits, useful when a fabric or size is genuinely scarce and you do not want one buyer clearing stock. Min Order Amount sets a floor for checkout, which suits wholesale-style clothing accounts or a shop absorbing delivery costs on tiny baskets. Catalog Mode turns the shop into a browsable catalogue without purchasing — the switch you want while a collection is still being photographed, or for a lookbook that points customers to stockists.

The Free Shipping Bar is a promotional nudge: a progress message tied to the free-shipping threshold, and the changelog adds a companion option in version 1.0.3 to hide other shipping methods once free shipping is available. Order on WhatsApp is a separate route for shoppers who would rather confirm sizing over chat than complete a checkout form — common in clothing retail, where fit questions stop a sale.

None of these appear in the evidence with configuration detail, so treat them as switches the vendor says exist. Whether a minimum order amount is enforced per cart or per customer, for example, is not stated, and it is worth confirming in the documentation or a staging install before you rely on it.

The product page, built up release by release

The changelog is a better record of the storefront than the feature list, because it shows what was added and when. Version 1.3.8 is the dense one: Side Cart, Login Popup, SKU and attributes on the product box, variations selectable directly on the product archive, column options for cross-sells and upsells, low-stock and shipping-class notices on the product page, and Single Sticky Add to Cart.

Variations on the archive is the entry worth pausing on. On a clothing catalogue, letting a shopper pick a size from the category grid removes a page load from the most common path — size browsing. Sticky add to cart does the complementary job further down a long description, keeping the purchase action in reach.

Earlier and later releases fill in presentation details: Quick View, product image zoom, YouTube and Vimeo video on the product page, a 360 view, product filters by colour and brand, mobile bottom menu and mobile product filters, plus AJAX add to cart for variable and grouped products and AJAX remove from cart. The mega menu is built from an Elementor template, which is the one navigation feature here that ties back to the page builder.

What none of this tells you is how the archive looks out of the box. The vendor's demo is the place to judge density, image ratios and how many products fit in a row; the changelog only says the controls exist.

Selling in more than one language, including right to left

The vendor lists "Compatible with RTL (Right to Left Arabic)", WPML support, Polylang support, Loco Translate support and a .POT file for all languages. Read that as a translation toolchain rather than a specific claim: WPML and Polylang are two different ways to run a multilingual shop, Loco Translate handles string edits without leaving WordPress, and the .POT file is what a translator works from.

RTL support is the item that affects design decisions rather than just strings. A fashion storefront leans on image and text placement, and a right-to-left layout mirrors those relationships, so it needs checking against your own layouts rather than assumed from a compatibility note.

Which languages a given demo ships translated is not stated. If a bilingual launch is the plan, plan the translation work as its own task; the theme supplies the scaffolding, not the copy.

Compatibility declarations and package notes

The vendor's compatibility list, as recorded in the marketplace attributes on 4 November 2026, names WooCommerce 6.x through 10.x, Elementor and Elementor Pro, WPML, Contact Form 7, Facebook and Bootstrap 4.x, with WordPress versions from 6.3.x through 7.0.x. Those are declarations of tested ranges, not results from running the theme against your PHP version, caching layer or plugin set — a staging check is still the only way to know how it behaves with your stack.

The record marks Gutenberg Optimized as No. That attribute describes block-editor optimisation, and on its own it does not mean the block editor is unavailable or broken; Clotya's editing model is Elementor, with page layouts and the mega menu built from Elementor templates.

The ThemeForest file list names PHP, CSS and JS files only. No child theme or demo content archive appears in that attribute, although the vendor feature list separately mentions a one-click demo data installer with XML, and the changelog added a theme setup wizard and a child theme in version 1.0.1. Two sources describing the package differently is worth knowing before you plan a build: confirm what actually arrives before designing around it.

The recent changelog is almost entirely two repeated lines — "Updated: WooCommerce outdated files" and "Updated: Clotya Core plugin" — with the vendor record last updated in October 2026. That pattern reads as a theme tracking WooCommerce template changes rather than one adding storefront features, while the AI buttons in 1.4.6 show it is not frozen. It is a maintenance signal, not a quality verdict.

Questions & answers