Custom Post Types, Taxonomies and Fields for Avada Builder is a WordPress add-on that extends three existing Avada Builder elements — Blog, Portfolio and Recent Posts — so they can display any custom post type, taxonomy, term or custom field instead of only standard blog posts. It is aimed at site builders who already use Avada and want their own structured content, such as events, properties, team members or listings, rendered in the same layouts the theme already provides. The plugin sells on CodeCanyon for $25 and has recorded 2,617 sales.
Avada’s native Blog, Portfolio and Recent Posts elements are tied to WordPress’s built-in post types. That is fine for a standard blog, but it becomes a problem the moment a project needs a “Property” or “Event” post type with its own taxonomy and custom fields. The usual answer is a separate plugin plus custom template work, which means rebuilding layouts that already exist in Avada. This add-on takes a narrower approach: it leaves the original elements untouched and adds parallel versions that accept custom content.
What the plugin actually adds to Avada Builder
Three new elements appear in the Avada Builder element list once the plugin is active: Blog CPT, Portfolio CPT and Recent Posts CPT. Each mirrors the behaviour of its original counterpart, including the layout choices — Large, Medium, Grid, Alternative, Carousel and Grid with Text — and the styling controls that come with them. Nothing about the visual output changes; only the source of the content does.
The most consequential addition is query control. Blog CPT and Portfolio CPT can be ordered by a custom field rather than by date, which matters for content where chronology is not the point. A property listing sorted by price, or a team page sorted alphabetically by surname, becomes a configuration task rather than a development one.
Filtering is handled through taxonomies and terms. The plugin reads the custom taxonomies registered on the site and shows only those linked to the selected post type, which reduces the guesswork of matching a taxonomy to the wrong content type. Both include and exclude modes are supported, so an element can either pull a specific set of terms or display everything except them.
Blog CPT and Recent Posts CPT go further and accept two taxonomies and two custom fields at once. In practice that means a card layout can display a category label and a secondary attribute — a location, a price band, a date — without touching template files. The plugin also builds dropdown lists of installed post types, registered custom fields and available taxonomies inside the element settings, so the configuration is done through selection rather than by typing slugs from memory.
Where this fits, and where it does not
The clearest fit is an Avada site that already relies on custom post types and wants to keep using Avada’s design system. Directory-style projects are the obvious case: real estate listings, event calendars, staff directories, product catalogues, course schedules or portfolio archives for non-standard content. Any project where the client expects to add entries through the WordPress admin and see them appear in a styled grid without developer involvement.
It also suits agencies maintaining several Avada sites. Because the elements behave like the originals, a layout built for one project can be reused on another with a different post type, which shortens the build for repeat work.
It is the wrong choice in two situations. First, if the site does not use Avada Builder, the plugin has nothing to extend — it is not a general-purpose custom fields or post type solution. Second, if the project needs front-end submission, complex relational fields, or a full custom fields framework with its own API, this add-on will not cover that ground. It displays custom content inside Avada elements; it does not create the post types or the fields themselves. Those must already exist, registered either by hand or by another plugin.
Strengths and limitations
Strengths
- Reuses Avada’s existing element layouts and styling controls, so there is no separate design language to learn or maintain.
- Ordering by custom field is built in, which covers a common requirement that Avada’s native elements do not handle.
- Taxonomy and term dropdowns are filtered to the selected post type, cutting down on misconfiguration.
- Include and exclude filtering modes give reasonable control over what appears in each element.
- Support for two taxonomies and two custom fields per element in Blog CPT and Recent Posts CPT.
- Compatibility is declared across WordPress 5.0 through 6.9 and Avada 7.x, with source files included.
- Automatic updates are handled through a purchase code entered on the plugin’s license page.
Limitations
- The rating sits at 3.97 out of 5 across 31 reviews, which is below what most buyers would expect from a plugin at this price point and sales volume.
- Installation is not a single zip. The download contains separate packages matched to Avada major versions, and the correct one must be chosen manually — a step that will trip up buyers who install the first zip they see.
- The plugin depends entirely on Avada Builder. If the theme is ever replaced, the elements disappear and any layout built with them has to be rebuilt.
- It does not register post types, taxonomies or fields. Those are prerequisites, so the total cost and complexity of a project is higher than the $25 price suggests.
- Vendor support is stated as a response within two business days, which is slower than the same-day expectations many buyers now hold.
- Browser compatibility is declared as far back as Internet Explorer 9, a claim that says little about how the elements behave in current browsers and is not evidence of testing depth.
How it compares with the alternatives
There are three broad routes to the same outcome. The first is a general custom fields plugin paired with a page builder that has its own dynamic content features. That route is more flexible and works outside Avada, but it means rebuilding layouts from scratch and accepting a second design system alongside the theme’s.
The second is custom development: registering the post types and writing template files or shortcodes that query them. This gives complete control and no dependency on a third-party add-on, but it costs developer time on every change and puts the client’s ability to edit layouts out of reach.
The third is this plugin. It wins on effort and consistency for Avada sites specifically, because it produces output that matches the theme’s existing elements exactly. It loses on portability and scope. A buyer comparing options should weigh how committed the project is to Avada: the stronger that commitment, the better this add-on looks. Where the theme choice is still open, a theme-agnostic approach is the safer investment.
Frequently Asked Questions
Does this plugin work without Avada Builder?
No. It extends three Avada Builder elements and has no function outside the theme. The plugin does not create its own shortcodes, blocks or templates that would work in another builder or in the default WordPress editor. Buyers using Elementor, Divi, Bricks or the block editor should look elsewhere.
Does it create custom post types and custom fields?
No, it only displays them. The custom post types, taxonomies and custom fields must already be registered on the site, either through code or another plugin. This add-on reads what is registered and makes it available to Avada’s Blog, Portfolio and Recent Posts elements. Buyers should confirm their content structures exist before purchasing.
Can the elements be sorted by a custom field instead of the publish date?
Yes. Blog CPT and Portfolio CPT can be ordered by a custom field, which is useful for listings where date order is meaningless, such as properties sorted by price or staff sorted by name. The field must be registered and populated for the ordering to produce sensible results.
How are updates delivered after purchase?
Updates are handled through the plugin’s license page. After activation, the buyer enters the CodeCanyon purchase code, which enables automatic updates from the WordPress dashboard. The vendor does not state whether the license is tied to a single site or can be reused across multiple installations, so that detail is worth confirming before buying for an agency with several Avada sites.
Verdict
This add-on is worth buying for one specific situation: an Avada site that already has custom post types and taxonomies registered, and needs them displayed in Avada’s own layouts without writing templates. For that buyer, the plugin removes a genuine piece of development work at a low price, and the field-based ordering and taxonomy filtering cover the requirements that come up most often. It is not the right purchase for anyone not running Avada, anyone expecting the plugin to create their content structures, or anyone who needs front-end submission and relational data. The 3.97 rating and the manual, version-matched installation are both reasons to read the documentation and recent reviews before committing, particularly on a client project with a fixed deadline. AmunetBiz has kept the plugin current with recent WordPress releases, which is a reasonable signal for a product of this size.
