A custom post type is a way of telling WordPress that some of your content is different enough from a blog post or a page to deserve its own structure — its own fields, its own URL pattern, its own admin screens. A plugin is a piece of code somebody else wrote that drops a feature into your site without you having to build it. Both can run a product catalog. They are not the same thing, and the choice between them is one of the most consequential decisions a small business will make about its website.
I once inherited a catalog of 200 outdoor-gear products from a Santa Fe retailer that was running on a popular catalog plugin. Pages took six seconds to load. Filtering by size returned the wrong results half the time. The owner had been told the plugin was “what everybody uses,” and so it was — until the catalog grew past a certain point and the plugin started losing the fight with the database. Switching to a custom post type cut the page-load time in half on the first deploy.
That story is more common than you might expect, and it usually starts with the same well-meaning shortcut.
The “default to a plugin” trap
The temptation to reach for a plugin is real. Plugins are fast to install, free or cheap, and require no developer. For a brand-new catalog with five products and a one-person team, a good plugin is often the right call. The trap is treating that decision as permanent. The plugin that fits ten products rarely fits a hundred, and the cost of switching later is much higher than the cost of choosing well the first time.
The hidden costs come in three flavors. The first is performance. A general-purpose catalog plugin loads code, styles, and database queries for features your site does not use, and pays the page-load tax on every visit. The second is data lock-in. Plugin-specific custom fields live in tables and formats only that plugin understands; migrating off later is rarely a one-click affair. The third is the ceiling. Every plugin has one — a point past which it cannot do what you need without a workaround that someone, eventually, will have to maintain.
The case for custom post types
A custom post type is built for your business, not for the average customer of a plugin author. That has four practical consequences.
- Control over the data model. Your products have whatever fields they actually need — material, finish, lead time, minimum order quantity — and nothing they do not.
- Performance. No plugin overhead, no unused features loading on every page. The catalog is as fast as your hosting allows.
- Custom URL structure. Products live at sensible URLs you choose, like
/strapping/woven-polyester/, not at whatever the plugin decided. - Longevity. A well-built custom post type will outlive any specific plugin and survives theme changes when registered correctly.
The cost is up-front: a developer has to build it. The win is that you stop paying a tax on every page load and stop hitting a ceiling every time the catalog grows.
When a plugin is genuinely the right call
Custom post types are not always the answer. A plugin is the right call when:
- The catalog is small (rough guideline: under twenty-five products)
- The product structure is simple — name, photo, description, price — and unlikely to need new fields
- There is no internal developer or budget for one
- The catalog is a temporary or experimental piece of the site
- The owner needs to launch in days, not weeks
If two or more of those are true, start with a plugin. You can always migrate later. The key is to make that “later” decision deliberately, not by accident the day the site falls over.
How big does a catalog have to be before custom post types make sense?
The honest answer is that catalog size is the wrong question. Complexity is the real one. A catalog of forty products with three custom fields and one taxonomy can run beautifully on a plugin. A catalog of fifteen products that need ten custom fields, two taxonomies, related-product relationships, and a custom search filter is already past the point where a plugin will save you time. As a rough rule of thumb: if you find yourself shopping for a plugin add-on to fix a limitation of the plugin you already installed, the answer is probably a custom post type.
What this looks like in real work
The clearest example from my own work is the Gilpin EZO website, a WordPress site built for a specialty packaging manufacturer that distributes easy-open ends, closures, and food containers across six continents and forty countries. The product content is organized through custom post types and a clean information architecture designed specifically for the way their global customers search — by product type, by application, by market. No off-the-shelf catalog plugin could have handled that structure without extensive workarounds. The custom approach made the site faster, easier to maintain, and durable enough to grow with the business. That is the kind of project where custom development pays back inside the first year.
A four-question decision framework
If you are about to commit to one approach or the other, walk through these in order:
- How many products will be in the catalog within twenty-four months? Not today — two years from now. Plan for that, not for the launch number.
- How many distinct fields does each product need? Count them honestly. Above six or seven, plugins start straining.
- Does the catalog need filtering, faceted search, or cross-product relationships? If yes, custom post types are almost always the better long-term call.
- Who will maintain the site in two years? If the answer is “an in-house team or a recurring developer,” custom is fine. If the answer is “nobody, ideally,” a well-chosen plugin lowers the floor.
Two yes answers usually point at custom. Three or four make it the obvious choice.
If you are weighing this for your own site
Patrick Iverson has been building custom WordPress sites and product catalogs for businesses across New Mexico and the United States since 2003 — including the kind of large, complex catalogs where a plugin would be the wrong tool from day one. If you are not sure which side of the line your project sits on, we are happy to look at what you have, what you are planning, and tell you honestly which path will cost less over the life of the site. No deck required. Just bring the product list and a sense of where the business is headed.