Vehica

The field system decides what your inventory can be

According to the marketplace description, Vehica offers six custom field types: Taxonomy, Text, Number, Price, Gallery and Embed. Taxonomy is the one that carries make, model and body type; Embed is what makes a video tour part of the listing rather than a link in the description. The vendor says you can create unlimited fields of those types, and that every field is searchable and filterable.

The more consequential part is how fields relate. Vehica supports field relationships, so Make can be wired to Model and Body Type to features, and "relevant fields" let one install present a different field set depending on the vehicle — cars, trucks, motorcycles or boats. Conditional logic then adjusts submission forms as a seller makes selections. That combination is what separates a mixed inventory from a car-only catalogue: a motorcycle listing does not have to carry a door count, and a boat does not have to pretend to have mileage.

If your site sells one category of vehicle with a fixed set of attributes, you will use a fraction of this. If you host several vehicle types under one roof and want each to feel purpose-built, the field model is the feature to evaluate first — and the one to test in a staging install before committing to a data structure that listings will be built on.

Instant search is the consumer of those fields

The vendor describes search results that update after each selection without reloading the page, showing how many vehicles match as the visitor narrows the set. Filtering covers make, model, year, price, mileage and any custom field you created, with sorting by relevance, date and price also listed.

Three search form variants — labelled V1, V2 and SearchListing — are provided, and the search widgets are configured inside the page builder. The practical reading: search forms are layout components you place and arrange, while the filter behaviour follows the field definitions you set up. A field that is not marked filterable will not appear as a filter, so the field panel and the search form have to be planned together rather than in sequence.

The vendor also claims speed and usability advantages over "most other themes" on the market. There is no comparative testing in the evidence behind this description, so treat it as a vendor claim rather than a measured result; the no-reload behaviour itself is the part that is concretely specified.

Where the 106 widgets actually go

Vehica's widget count is large enough to be meaningless on its own, but the vendor breaks it down by page type, which makes it useful. Thirty-eight general widgets cover search forms, car grids, tabbed carousels, sliders, maps, a loan calculator, testimonials and contact forms. Thirty-eight more belong to the single vehicle listing page: galleries, attributes, price, features, contact owner and related vehicles. Thirteen cover user and dealer profiles, fourteen cover the blog, and two cover archives, with layout templates on top.

That distribution tells you where the design work sits. A listing detail page and a seller profile are treated as first-class page types with their own component sets, not as generic content templates. Elementor Pro is described as supported but not required, and the vendor says every page template can be edited in Elementor without code. Gutenberg Optimized is listed as Yes in the marketplace attributes observed on 3 November 2026, but Elementor is the editing route the vendor documents.

The seller's side: submission, roles and contact

Front-end submission is where a listing platform either works or does not. The vendor describes a submission form carrying photo galleries, attachments, location fields and all custom fields, with optional moderation and automated email notifications for new submissions, approvals and expirations. A user panel lets sellers manage, edit and renew their own listings without entering the WordPress admin, and anti-spam protection is listed for listing quality.

Two seller roles sit underneath: Private Seller and Business Seller, described as having different capabilities. That distinction is what lets you price or gate features by seller type instead of applying one rule to everyone. Registration can run through Google or Facebook social login, and contact between buyer and seller happens through a direct messaging system, a WhatsApp button on listings and profiles, and a displayed phone number.

One boundary worth noting: the vendor describes the roles as different in capabilities but does not enumerate exactly which permissions differ. Confirm the split you need — submission limits, featured placement, moderation bypass — in the theme's settings rather than assuming it.

Charging for listings, and what each payment route costs you

Listing packages are configurable by price, duration, featured period and category, and free packages or time-limited promotions are supported for growth. Three payment routes are described: WooCommerce payment gateways, which bring card processing, PayPal, bank transfer and the wider gateway catalogue; a direct Stripe integration; and a direct PayPal integration.

These are not equivalent choices in operation. WooCommerce adds a shop engine and its own order and tax logic to your site; direct Stripe and PayPal skip that layer but mean the theme, not WooCommerce, is handling the transaction flow. If you already run WooCommerce for merchandise, using its gateways keeps one payment stack. If listings are the only thing you sell, the direct routes are the leaner option — provided the gateway accounts you have access to are ones the theme's integrations cover.

Listing pages, galleries and the localisation controls

The vehicle detail page carries four gallery styles, per the vendor, alongside compare vehicles across inventory fields, saved favorites and a loan calculator widget for monthly payment estimates. Related vehicle carousels and dealer information sit on the same page, which is the usual shape of an automotive listing page rather than a distinguishing choice — the gallery count and the compare/favorites pair are the parts that change how a buyer browses a large inventory.

Localisation is handled in the theme panel rather than through a translation plugin: the vendor says all texts and URL slugs can be translated there, currencies can be switched and several currencies supported at once via a currency switcher widget, and number formats and metric systems adjusted per region. For a dealer operating in one country this is convenience. For a marketplace spanning regions, the currency switcher is the detail that matters, since it lets one inventory display prices in more than one currency instead of duplicating listings.

What the evidence establishes, and what it does not

Everything above comes from the vendor's ThemeForest description and the marketplace attributes observed on 3 November 2026, not from installing or running the theme here. The declared WordPress support runs from 5.0.x to 7.0.x, there is a listed compatibility set of Elementor, Elementor Pro, Contact Form 7 and Facebook, and the demo is offered at tangiblewp.com/vehica with a live preview on the marketplace. Browsers named are Chrome, Firefox, Safari, Opera and Edge.

Two vendor statements deserve separate treatment. XML/CSV vehicle import is described as working with the free WP All Import plugin — an integration, so that plugin is part of your setup rather than something bundled. And the search-engine comparison to other themes is marketing phrasing without a published method. The features that decide a purchase here are checkable in a staging install: field relationships across vehicle types, whether instant search stays responsive on your inventory size, and whether the seller roles match the permissions you intend to sell.

Questions & answers