Autusin

A phone layout you switch on, not just a squeezed desktop

Plenty of WooCommerce themes call themselves responsive and stop there. Autusin's vendor description draws a distinction: the theme ships both responsive layouts and mobile-specific web designs, and the mobile set is enabled or disabled from Theme Options. Turn it off and the site falls back to the responsive layouts.

That matters because a phone-specific shop layout is a design decision, not a CSS breakpoint. It changes how much a visitor sees before scrolling, how product blocks stack, and how much of the header follows them down the page. The vendor describes the mobile layouts as behaving like an app. You are getting a second front end to check on every template you customise, and the toggle lets you keep it for a campaign period or run it permanently.

If you sell parts to people standing in a garage holding a phone, that switch is the reason to look at this theme before its builder.

Nineteen-plus homepages, three-plus mobile layouts

The vendor's headline count is 19+ homepages and 3+ mobile layouts, with index #17, #18 and #19 arriving in separate releases through 2023. Volume here is about starting points rather than variety for its own sake: an auto parts catalogue, a motorcycle accessories front page and a general equipment store want different first screens, and each demo gives you a section order to adapt instead of invent.

One-click demo import is listed as the mechanism, so the practical question is which demo's product blocks match your catalogue shape — grid density, whether brand filtering is prominent, how much room the slider takes. Choose on structure first; colours and type are theme option changes.

The merchandising details that matter for parts

A parts shopper often knows the number they need. The feature list names Ajax Live Search Pro, which searches products by keyword and by SKU — useful when a customer pastes a part number rather than typing a description. Live search sits alongside the standard catalogue tools rather than replacing WooCommerce search.

Beyond that, the vendor lists variation swatches and images for products, colour swatches shown in product listings, a featured video in the product gallery, a quick view lightbox, and image zoom. Bundle products are supported, which fits accessory kits and consumable bundles better than single items. Compare and wishlist are named as AJAX features, so an unregistered visitor can build a shortlist without page reloads.

Each of these is a vendor claim about supported functionality. Whether a swatch renders in a listing, or a bundle's add-to-cart notification behaves correctly, is something to check on your own staging site — the changelog shows add-to-cart notifications for product groups were still being fixed as recently as version 2.9.9.

Multi-vendor support means plugin compatibility, not a marketplace

The description names four multi-vendor plugins: Dokan MarketPlace, WC Vendors, MultivendorX and WCFM MarketPlace. Read that as a compatibility statement. The marketplace logic — vendor registration, commission splits, vendor dashboards, payout handling — belongs to whichever plugin you install and maintain separately.

So the decision is mostly about the plugin: which one your payment and shipping requirements point to, and who keeps it current. Autusin's contribution is that its templates and theme options declare support for all four, which you should confirm on a staging build with real vendor products rather than a demo import alone.

Where Elementor ends and the filter plugins begin

Elementor is listed under compatible-with and as "Elementor Page Builder 3.23.x Ready", and pages are built in it. What the changelog clarifies is a boundary shift: version 2.9.2 updated the header and footer to be editable with Elementor Free, and in the same release removed Elementor Pro and JetSmartFilters from the theme package.

That produces a discrepancy worth resolving before you plan the build. The full feature list still names JetSmartFilters 3.5.x as compatible, while the changelog says it left the package in January 2025, replaced by SWG Brand Filter hierarchical filtering. Elementor Pro, meanwhile, was listed in earlier releases as included at a given version but is no longer bundled — if a demo relies on Pro widgets, that licence is yours to arrange.

None of that breaks the theme. It does mean you should list which plugins your chosen demo actually needs and where each one comes from, rather than assuming the package supplies everything the feature list mentions.

What the vendor says comes with the theme

Under what's included, the description lists the theme package, a child theme, layered and organised PSD sources, and documentation. The child theme is the useful one day to day: customisations made there survive parent theme updates, and Autusin has shipped regular updates since 2018.

The PSD files cover design assets for the demo layouts rather than the built site itself. Beyond the package, the vendor points to a public forum and a ticket system for support, and states it works on WordPress 7.0.x and a long span of earlier versions, with Firefox, Safari, Opera, Chrome and Edge listed as browsers.

Two version lines that don't agree, and why that matters

The feature list says "WooCommerce 9.8.x Compatible!", while the 2.9.9 changelog entry — dated 17 June 2026, with the marketplace listing observed on 4 November 2026 — records an update to WooCommerce 10.8.0, WordPress 7.0 and Revolution Slider 6.7.57. The marketplace attributes, for their part, list WooCommerce compatibility for the 6.x through 9.x lines.

Feature lists in marketplace descriptions are rarely rewritten as often as changelogs, so treat the changelog as the more current record and the compatibility lists as declarations rather than test results. The practical move is to confirm the WooCommerce and PHP versions of your host against what the current release documents, and to exercise checkout, filtering and the mobile layout on a staging copy before launch. Autusin's release notes show steady maintenance — WooCommerce bumps, PHP 8.2 bug fixes, a High-Performance Order Storage compatibility update — but that is a maintenance record, not a guarantee about your stack.

Questions & answers