Categories and attributes are set up in wp-admin under Products > Categories and Products > Attributes. Catalog performance depends on how you structure those plus the PHP and cache settings on your WooCommerce hosting account. Most catalog problems trace back to one of three things: unclear category structure, a plugin or import script hitting PHP limits, or attribute setup that doesn't match how you actually filter and vary products.
Setting up product categories
Go to Products > Categories in wp-admin. Each category gets a name, a slug, an optional parent (for nesting, like Shirts > Men's), and an optional image and description used on the category archive page.
- Keep the tree shallow. Two levels is usually enough: a top-level department and a subcategory. Three or more levels makes navigation and breadcrumbs confusing for customers.
- Assign every product to at least one category before publishing. Uncategorized products fall into WooCommerce's default "Uncategorized" bucket and won't show up where customers expect.
- Categories are separate from attributes (like size or color) and tags. Use categories for "what kind of product is this," attributes for variations within a product, and tags sparingly for cross-cutting labels.
Products, variations, and attributes
A simple product has one price and one SKU. A variable product uses attributes (Size, Color) to generate variations, each with its own price, stock, and SKU. Define attributes under Products > Attributes if you want them reusable across multiple products (recommended for anything with more than a handful of items), or define them per-product under the Attributes tab if they're one-off. A common mistake is adding an attribute to a product but forgetting to check "Used for variations," then wondering why no variations appear on the Variations tab. Both steps are required.
Bulk imports and PHP limits
Importing a large catalog via Products > Import (CSV) or a migration plugin can hit PHP upload and execution limits on bigger files. These aren't set from the PHP Version tile in the portal, which only controls which PHP version (7.4 through 8.3) runs your site. To raise the actual limits, open cPanel from your hosting service and go to Software > MultiPHP INI Editor. Select your domain, switch to Editor mode, and raise the relevant PHP limits, then re-run the import. If an import still times out on a very large catalog, split the CSV into smaller batches rather than pushing the limits indefinitely.
Keeping the catalog fast
Category and product archive pages are some of the heaviest pages on a store because they run product queries, price range calculations, and stock checks on every load. Your account already runs on the same speed stack as every Flashcloud site: LiteSpeed with LSCache for full-page caching, plus a Redis object cache that memorizes repeated database lookups so category pages don't re-run the same queries on every visit. A few catalog-specific habits help beyond that baseline:
- Don't create attributes or categories you don't use. Every one adds rows WooCommerce has to filter through on archive and shop pages.
- Compress product images before upload. Large galleries are one of the more common causes of a slow shop page, and it's a fix that pays off regardless of hosting.
- Cart and checkout pages typically stay out of full-page caching so customers see their own live cart, while category and product pages are what get cached.
For broader store performance questions, from heavy plugins to database cleanup, see running a WooCommerce store.
Before changing a live catalog
Bulk edits, category restructuring, and attribute changes on a live store can break product URLs or hide items from search unexpectedly. Test structural changes on a copy first, and take a fresh backup before running any large import or bulk edit. If something goes sideways on the live site, open a ticket from the portal's Support section; a real person will help you sort it out.