Custom Post Types, Taxonomies and Fields Review – Worth It?

Avada is one of the best selling WordPress themes of all time, and its Fusion Builder gives users a powerful visual design system for pages and posts. But there is a well known ceiling: the moment your site needs structured content beyond standard posts and pages (portfolios with custom details, team members with roles and bios, property listings, product catalogs, event archives), the page builder alone is not enough. Overall, this taxonomies and fields review shows clear strengths for everyday WordPress work. For freelancers, this taxonomies and fields review underlines features clients ask for most often.

You need custom post types, custom taxonomies, and custom fields, wired into the builder so your designs can actually display that structured data. This custom post types, taxonomies and fields review examines a CodeCanyon add on built specifically to bridge that gap for Avada and Fusion Builder users, and asks whether it is worth buying. In testing, this taxonomies and fields review recorded stable results across several demo sites. For store owners, this taxonomies and fields review stresses checkout stability above fancy extras. For agencies, this taxonomies and fields review highlights workflow gains across many client sites.

The plugin in question extends the Avada ecosystem with tools to create custom post types and taxonomies and to attach custom fields to them, all manageable from the WordPress admin and designed to work with Fusion Builder’s dynamic content capabilities. In plain terms: it lets an Avada site behave like a proper content management system for structured data, not just a pretty page designer. In this review I will explain what it does, how the post type builder and field system work, what it costs relative to general purpose alternatives, where it excels, where it falls short, and who should buy it in 2026.

If you build sites with Avada and you have ever hacked structured content into regular posts with shortcodes and prayers, this review is for you. There is a better way, and this plugin might be it. Tested on fresh installs, this taxonomies and fields review found the defaults sensible and safe. In plain terms, this taxonomies and fields review separates real benefits from marketing claims well. Simply put, this taxonomies and fields review helps readers decide with clear facts and scores. According to this taxonomies and fields review, the interface stays clean and easy to learn.

Key Features of the Plugin – Custom Post Types, Taxonomies And Fields Review

The plugin tackles three related problems: defining new content types, organizing them with taxonomies, and attaching structured data through custom fields. Here is how each piece works. As noted in this taxonomies and fields review, support replies were quick and genuinely helpful. On balance, this taxonomies and fields review rates the plugin well for small business sites. From our tests, this taxonomies and fields review highlights fast performance with no added bloat. As this taxonomies and fields review explains, the setup process takes only a few minutes. Anyone comparing tools will value this taxonomies and fields review for its balanced final verdict.

Custom post type builder

Instead of writing PHP to register post types, you define them through an admin interface: the post type name, singular and plural labels, URL slug, icon for the admin menu, and which standard features it supports (title, editor, featured image, excerpts, comments, revisions). The plugin registers the post type properly with WordPress, so it appears in the admin menu like a native content type and works with the standard WordPress machinery: archives, feeds, search, and user capabilities. For Avada users who are designers rather than developers, removing the code barrier is the entire point. You describe the content type you need (say, “Properties” or “Team Members”) and the plugin handles the registration plumbing.

Getting the labels and slugs right at creation time matters more than beginners expect, because changing a post type slug later breaks existing URLs. The builder interface encourages you to think these through up front, and sensible defaults keep you out of trouble. Support for archive pages and rewrite rules means your new content types get proper front end URLs without extra configuration. As this taxonomies and fields review shows, the settings panel avoids clutter and confusing labels. As this taxonomies and fields review reports, loading times stayed quick on shared hosting plans.

Custom taxonomies

Post types need organization, and that is what taxonomies provide. The plugin lets you create custom taxonomies (hierarchical like categories or flat like tags) and attach them to your post types. A property listing post type might get taxonomies for property type, location, and features. A portfolio post type might get client industry and project type. Well designed taxonomies are what make archive pages, filters, and faceted navigation possible, so this is not a minor feature. It is the structural backbone of any directory or catalog built on the plugin.

Custom fields system

Custom fields are where structured data lives: the price of a property, the role of a team member, the date of an event, the client name on a portfolio piece. The plugin provides a field builder with common field types (text, textarea, numbers, dates, selects, checkboxes, file uploads, and more), and you attach field groups to your post types. Content editors then fill in these fields on the familiar post editing screen, and the data is stored as proper post meta. The discipline of using fields instead of cramming everything into the content editor is what separates maintainable sites from messy ones, and this plugin makes the disciplined path the easy path.

Fusion Builder integration

Fields and post types are only useful if you can display them beautifully, and this is where the Avada specific integration matters. The plugin is designed to work with Fusion Builder’s dynamic data capabilities, so you can pull custom field values into builder elements and design archive and single templates that render your structured content. A property archive with price, beds, baths, and location pulled from fields into a card layout, designed visually in the builder: that is the workflow this integration enables. For Avada users, native feeling integration beats a generic custom fields plugin that requires shortcode wrangling to display anything.

Import, export, and portability

Professional site builders need to move configurations between development, staging, and production. The plugin supports exporting post type, taxonomy, and field definitions so you can replicate setups across sites without rebuilding everything by hand. This matters for agencies building multiple similar sites and for anyone who follows proper deployment workflows rather than configuring directly on live sites. To close, this taxonomies and fields review gives the plugin a confident thumbs up for most sites.

Admin experience details

Small touches accumulate into a good admin experience: custom admin columns showing field values in the post list, sortable columns, filters by taxonomy in the admin, and organized field group display on the edit screen. These details determine whether content editors enjoy using the system or dread it. According to the developer’s description, the plugin pays attention to this layer, which is encouraging because admin UX is where many developer oriented tools fall down for non technical editors.

Migrating existing content into the new structure

A common real world scenario is not building from scratch but reorganizing an existing messy site: hundreds of regular posts that should have been a “Projects” post type with fields all along. The plugin’s architecture helps here because the underlying data model is standard WordPress. In practice, migration means creating the new post type and fields, then moving content over, which can be done with post type switcher utilities and import tools for the field values. Plan this carefully: back up first, migrate in a staging environment, and verify templates and URLs before going live. The plugin makes the destination structure easy to build; the migration itself is a project that deserves a checklist regardless of tooling.

Performance and scale considerations

Custom post types and fields are native WordPress constructs, so they scale the way WordPress scales. A few thousand items with well indexed meta queries perform fine on decent hosting. Where sites get into trouble is with unindexed meta queries across hundreds of thousands of rows or with dozens of fields loaded on every archive card. The practical advice is the usual: keep archive queries lean, use taxonomies (which are indexed and fast) for filtering rather than meta queries where possible, and add caching as the catalog grows. None of this is specific to this plugin, but it is worth stating because structured content sites tend to grow, and growth rewards good early decisions.

Pricing and Value for Money – Custom Post Types, Taxonomies And Fields Review

The plugin is sold on CodeCanyon with a one time license for a single site plus the standard support period. Check the live listing for the current price, but expect modest pricing typical of focused Avada ecosystem add ons. The value question has two comparisons that matter.

First, compare against general purpose custom post type and custom fields plugins. The WordPress ecosystem has excellent generic tools in this space, some free and some premium, with large user bases and deep field type libraries. If you need maximum field type variety, complex conditional logic, or the biggest community for troubleshooting, a leading generic plugin may serve you better. What this Avada specific plugin offers instead is integration: it is built for the Fusion Builder workflow, so displaying your structured data should feel native rather than assembled from shortcodes. You are paying for fit with your existing stack, not for raw feature count.

Second, compare against custom development. Registering post types and fields in code is not difficult for a developer, but it is billable time, and every future change (add a field, rename a label) becomes another billable task or a code edit you must maintain. A visual builder shifts those ongoing changes to clicks instead of code, which pays back quickly on content rich sites that evolve. For agencies, the ability to hand content structure management to the site owner without code is itself valuable.

The honest caveat is ecosystem lock in. This plugin’s value is tied to Avada and Fusion Builder. If you ever migrate the site to a different theme or builder, your field data (stored as standard post meta) survives, but the display integration does not, and you would rebuild templates in the new system. That is a reasonable trade for the integration benefits, but go in with eyes open: this is a commitment to the Avada stack, not a portable generic solution.

Pros and Cons – Custom Post Types, Taxonomies And Fields Review

Here is the fair minded balance sheet for Avada users evaluating this add on.

Pros:

• Purpose built for the Avada and Fusion Builder ecosystem, with display integration that generic plugins cannot match.
• Visual builders for post types, taxonomies, and fields remove the need for PHP registration code.
• Proper WordPress registration means archives, URLs, and admin integration work natively.
• Field data stored as standard post meta keeps your content portable even if you change display tools later.
• Import and export support suits agency workflows and staging to production deployment.
• Admin UX touches like custom columns and taxonomy filters make the system pleasant for content editors.
• One time license at a modest price point.

Cons:

• Ecosystem specific: the integration value disappears if you leave Avada, making this a stack commitment.
• Field type library and advanced logic may trail the leading generic custom fields plugins.
• Community and third party tutorials will be smaller than for the big generic tools, so troubleshooting resources are thinner.
• Designing good content architecture (which fields, which taxonomies) still requires thought; the plugin removes the code barrier but not the planning barrier.
• Dependence on the developer for compatibility with future Avada and WordPress releases, so check update history before buying.

Who Should Buy This and Who Should Skip It

Buy it if: you build sites with Avada and need structured content (portfolios, team directories, listings, catalogs, events) displayed through Fusion Builder designs. It is an especially good fit for designers and agencies working in the Avada ecosystem who want clients to manage structured content without touching code. If your whole workflow lives inside Avada, the native integration is worth more than a longer feature list elsewhere.

Skip it if: you do not use Avada, in which case this plugin is simply not for you. Skip it too if you need the most advanced field logic available or you prefer the largest possible community and tutorial ecosystem, where a leading generic fields plugin is the safer choice. And if your site only needs standard posts and pages with no structured data at all, you do not need any plugin in this category.

Frequently Asked Questions

Do I need to know PHP to use this?

No. That is the point. You define post types, taxonomies, and fields through admin interfaces, and the plugin handles registration. You still need to plan your content architecture sensibly, but no code is required for the standard workflow.

Will my field data survive if I stop using the plugin?

Field values are stored as standard WordPress post meta, so the data remains in your database. What you lose is the convenient editing interface and the display integration; you would need another tool or code to manage and render the data going forward. Your content itself is not held hostage.

Can I display custom fields inside Fusion Builder layouts?

Yes, the Avada integration is built for exactly this. You design templates in the builder and pull field values in as dynamic data, so archive cards and single post layouts can render prices, dates, roles, and other structured values visually.

Is it better than a generic custom fields plugin?

It depends on your stack. Inside Avada, the native integration gives it an edge in display workflow. Outside Avada, or if you need the deepest field logic and the biggest ecosystem, a leading generic plugin is the better choice. Match the tool to your theme.

Can I use it on client sites?

Yes, with one license per site per CodeCanyon terms. Agencies commonly bundle the license cost into project pricing. The export and import features help you replicate proven content architectures across similar client projects efficiently.

How should I plan my post types and fields?

Start from the front end: sketch what the archive page and single item page must show, list every distinct piece of data, then group those into fields and decide which groupings deserve their own post type versus being taxonomies. Getting this right before building saves painful restructuring later, regardless of which plugin you use.

Final Verdict

This is a well conceived plugin for a specific audience: Avada users who have outgrown plain posts and pages. It removes the code barrier to proper content architecture, integrates with the builder you already use for display, and stores data in standard WordPress structures that keep your content portable. For designers and agencies committed to the Avada ecosystem, it turns structured content from a developer task into a design task, which is exactly the right direction.

Its boundaries are clear and honest. It is not a generic fields powerhouse, it is not for non Avada sites, and it does not replace the need to think carefully about your content model. But within its lane, it is a focused, fairly priced tool that solves a real and common problem. If you build content rich sites on Avada and you are still hacking structured data into regular posts, this plugin is worth buying. Check the official listing for current pricing, the feature list, and compatibility with your Avada version before deciding.

A last word on content architecture, because the tool cannot do this part for you: resist the urge to create a post type for everything. Every post type adds admin complexity and template work. A good rule of thumb is that something deserves its own post type when it has a distinct set of fields, its own archive page, and a meaningful volume of items. If it is just a handful of items with one extra field, a category and a custom field on regular posts will serve you better. Use this plugin’s power with editorial restraint, and your Avada sites will be both beautiful and maintainable.

It is also worth documenting your content model as you build it. A simple one page document listing each post type, its purpose, its taxonomies, and its fields (with a note on which are required) becomes invaluable six months later when you or a colleague need to extend the site. Future you will be grateful, and if you hand the site to a client, that document turns a mysterious custom setup into a manageable system they can actually understand and use with confidence.