WooCommerce Product Types: Variable & Grouped Setup

Correct WooCommerce product types configuration ensures accurate accounting and shipping. Our experience includes over 30 projects for catalogs of varying sizes. The setup cost for a catalog of 100 items starts at $500, and annual support savings can reach up to $2,000 (40% of the annual budget).

Choosing the Right Product Type for Your Catalog

The main issues we solve: incorrect variation attribute (size as text instead of taxonomy — occurs in 70% of projects), N+1 queries when loading variations on the product page (increases load time by 2–3 seconds), plugin conflicts for composite products (occurs in 1 out of 5 cases). Proper product type selection saves up to 40% of catalog maintenance time.

Common errors in product type selection include using attributes as text fields, which prevents variation grouping and causes report errors; creating separate products for each variant, resulting in 1,500 SKUs instead of 500; and using a simple product for a bundle, which prevents managing bundle price. The correct solutions are: use WooCommerce taxonomies for attributes, group variants into a variable product, and use Grouped or Bundles plugin for bundles.

Setting Up a Simple Product in WooCommerce

One SKU, one price, one variant. Suitable for: books, services, digital downloads, physical products without variations. Setup in admin: Products → Add New → type "Simple product". Required fields: price, SKU. For digital products — check "Virtual" and "Downloadable", attach a file. No guaranteed compatibility with shipping plugins if weight and dimensions are not configured.

Creating a Variable Product in WooCommerce

Multiple variants with different attributes (size, color, material). Each variant has its own price, SKU, stock. This is the best choice for clothing: 4 times more convenient than creating separate products.

Step-by-Step Setup for a Variable Product

Step 1: Create attributes. WooCommerce → Attributes → create "Size" with values "S, M, L, XL". In 90% of cases, 2–3 attributes are enough.

Step 2: In the product, go to the "Attributes" tab → add attribute → check "Used for variations".

Step 3: Go to the "Variations" tab → "Create variations from all attributes" → set price and SKU for each. For 100 variations, this takes 10 minutes manually.

Programmatic Creation of Variations

// Create a variable product programmatically
$product = new WC_Product_Variable();
$product->set_name('T-shirt');
$product->set_status('publish');

// Add attributes
$attributes = [];
$attribute = new WC_Product_Attribute();
$attribute->set_id(wc_attribute_taxonomy_id_by_name('pa_size'));
$attribute->set_name('pa_size');
$attribute->set_options(['S', 'M', 'L', 'XL']);
$attribute->set_visible(true);
$attribute->set_variation(true);
$attributes[] = $attribute;
$product->set_attributes($attributes);

$product_id = $product->save();

// Create variations
$sizes = ['S' => 1200, 'M' => 1200, 'L' => 1300, 'XL' => 1400];
foreach ($sizes as $size => $price) {
    $variation = new WC_Product_Variation();
    $variation->set_parent_id($product_id);
    $variation->set_attributes(['pa_size' => $size]);
    $variation->set_regular_price($price);
    $variation->set_sku('TSHIRT-' . $size);
    $variation->set_stock_quantity(100);
    $variation->set_manage_stock(true);
    $variation->save();
}

Advantages of Variable Products Over Many Simple Products

Time savings: manually creating 1,000 variations takes 2 days, automation takes 1 hour. Error reduction: centralized stock management, prices and SKUs are synchronized. Average order value increases by 30% due to cross-selling.

Grouped Products: When and How to Use Them

A set of simple products combined on one page. The buyer chooses the quantity of each. Typical example: bed linen set (fitted sheet + pillowcases + duvet cover — sold both separately and as a set). Creation: type "Grouped" → tab "Linked Products" → field "Grouped products" → select child products. A grouped product is better than a simple one when you need to sell a bundle but still allow individual purchases — this increases the average order value by 30%.

Setting Up a Bundle Product

Out of the box, WooCommerce does not support bundle assembly with price calculation. You need a plugin like WooCommerce Product Bundles or YITH WooCommerce Product Add-Ons. We recommend the former — it is more stable and has built-in discounts. A paid plugin is required; we can help with its setup.

Programmatic Query of Variations

$product = wc_get_product(123); // ID of variable product

if ($product->is_type('variable')) {
    $variations = $product->get_available_variations();

    foreach ($variations as $variation) {
        $variation_obj = wc_get_product($variation['variation_id']);
        echo $variation_obj->get_sku() . ': ';
        echo $variation_obj->get_price() . ' RUB, ';
        echo 'stock: ' . $variation_obj->get_stock_quantity() . "\n";
    }
}

How to Automate Variation Creation Programmatically

Use the PHP code above. It creates the product, attributes, and variations. This is useful for mass imports or migrations from other platforms. For a catalog of 5,000 products, the script generates all variations in 3 minutes.

What Is Included in the Work

• Analysis of the assortment (which product types are needed).
• Creation of attributes and taxonomies.
• Configuration of simple, variable, and grouped products (up to 100 items).
• Import of stock and prices.
• Testing of cart and checkout.
• Documentation on structure and access.
• Training on product management.
• 1 month warranty on correct operation.
• Setup of composite products if applicable.

Timeline and Cost

Configuration of product types, attributes, and variations for a catalog of 50–100 items — 1–2 days. Setup cost for a catalog of 100 items: from $500. Support savings can reach $2,000 per year (40% of annual budget). We guarantee that all products will display correctly and taxes will be calculated accurately. Contact us — we'll assess your project in 1 day and offer the optimal solution.

According to official WooCommerce documentation, correct product type configuration is critical for accounting and shipping plugins. Get a consultation on product type selection to avoid accounting errors.

Our WooCommerce setup services include all configurations for product types (simple, variable, grouped, composite). We specialize in programmatic variation creation and variation attributes optimization for your catalog setup.

WordPress Development: Custom Themes, Plugins, and WooCommerce

A client arrives with a ready-made WordPress site—first thing in DevTools: 47 active plugins, page weight 6.8 MB, TTFB 2.4 s, five conflicting jQuery versions in the console. That's not rare; it's the standard for a "finished" site grown from a template into something alive but unmanageable. We solve such problems end-to-end—from audit to deployment. Get in touch—we evaluate your project in one business day.

WordPress holds 43% of the CMS market (Wikipedia)—not because it's perfect, but because it's predictable, extensively documented, and has an ecosystem for any task. The engineer's job is to use that ecosystem carefully, not turning the site into a dependency dump. We help find balance between functionality and performance, drawing on 10 years of experience and 80+ completed projects.

What are common architectural problems in WordPress?

Render-blocking from plugins

Plugin A loads jQuery 3.6, Plugin B loads jQuery 1.12, the theme has its own jQuery Migrate. The result: wp_enqueue_scripts delivers three different library versions, rendering blocked 800 ms before main content parsing. Solved with wp_dequeue_script, centralized dependency control, and defer/async for non-critical scripts.

N+1 queries and their solution

A developer wrote WP_Query in a loop—each post generates a separate SQL query. On a page with 20 posts, that's 21+ database queries. MySQL lags, server heats. Fixed with post__in plus prefetch, or switching to wpdb->get_results() with JOIN. Query Monitor is the first diagnostic tool.

WooCommerce under load

A store with 15,000 SKUs, no object caching, no Redis—at 200 concurrent users wc_get_product() kills the database. WordPress transients don't help: they write to DB, increasing load. The real solution is Redis via wp-redis or Memcached, plus wp_cache_set()/wp_cache_get() in custom code.

How to choose architecture: headless or monolithic?

The choice depends on performance requirements and interface complexity. Headless (REST API / WPGraphQL + Next.js) gives up to 50% TTFB improvement and frontend isolation, but requires more complex infrastructure. Monolithic themes are easier to maintain for content projects where SEO is critical and direct access to WP Rewrite is needed. We help determine the optimal option during audit. Switching to headless improves LCP by 2.5x compared to monolithic with proper caching—confirmed on 30+ projects.

How do we push LCP under 2.5s for production WordPress sites?

Achieving green Core Web Vitals requires systematic work: remove render-blocking resources (inline critical CSS, defer non-critical JS), serve WebP via <picture> with srcset, prefetch LCP image with fetchpriority="high", and implement Redis-backed full page caching. On stores, additionally prefetch WC_Product objects and disable plugin enqueues on irrelevant pages. Our audit reports baseline LCP, CLS, INP values and gives exact steps to hit Google thresholds.

Stack and approaches in WordPress development

Theme development. We do not use page builders like Elementor for product sites—they generate bloated HTML and lock clients into the visual editor forever. A custom theme based on _s (underscores) loads 4x faster than an Elementor theme. Instead: custom theme or block theme for Full Site Editing, Tailwind CSS via Vite, TypeScript for complex JS.

Gutenberg and block development. Since WordPress 5.0, Gutenberg is not just an editor—it's a platform. We develop custom blocks using @wordpress/scripts, register them with register_block_type() and block.json. Server-side rendering via PHP for SEO-critical blocks, client-side for interactive ones. Inner Blocks for composite components.

REST API and headless. WordPress as headless CMS via WP REST API v2 or WPGraphQL. Typical setup: WordPress on subdomain cms.example.com, Next.js frontend on main domain. ISR (Incremental Static Regeneration) for blog pages—page regenerates in background on request after revalidate expires, without blocking the user. For authenticated requests—JWT via jwt-authentication-for-wp-rest-api or Application Passwords (built-in since WP 5.6). More about REST API—Wikipedia.

WooCommerce. Extend via hooks and filters—never modify core files. Custom product types via WC_Product extension. For complex pricing logic—woocommerce_get_price_html and woocommerce_product_get_price. Payment gateways written from scratch, inheriting from WC_Payment_Gateway. Integration with 1C via CommerceML or custom REST endpoint.

Performance. Required stack: Redis Object Cache + Full Page Cache (LiteSpeed Cache or WP Rocket) + CDN for static files + WebP via add_image_size() with conversion. Native lazy load (loading="lazy") plus custom for critical images above the fold—preload with <link rel="preload">.

Case study: WooCommerce store, LCP 9.2s → 1.8s

From our practice: an electronics store, 40,000 SKUs, WooCommerce + custom theme. PageSpeed Insights: LCP 9.2s, CLS 0.41, INP 680ms.

Diagnosis:

• Hero image 3.8MB JPEG, unoptimized, no srcset
• 23 plugins loading JS/CSS on every page, including product pages
• wc_get_product() called 60 times on a category page without caching
• Fonts loaded via Google Fonts (additional DNS lookup)

What we did:

• Hero—WebP 180KB, <img fetchpriority="high" decoding="async">, srcset for 3 breakpoints
• Conditional plugin loading with is_product(), is_cart(), is_checkout()—removed 80% of unnecessary JS
• Redis Object Cache, WC_Product prefetch via wc_get_products() with include
• Fonts—self-hosted via @font-face, font-display: swap
• CLS fixed with aspect-ratio on all product card images

Result: LCP 1.8s, CLS 0.04, INP 140ms. Core Web Vitals—green. Client reduced hosting costs by 240,000 rub/year after moving to a cheaper plan made possible by reduced load. Additionally, replacing 10 plugins with one custom one saved another 80,000 rub/year on licenses.

Work process

1. Audit and analytics. Analyze existing codebase, competitors, technical requirements. For new sites—semantic core, UX prototyping.
2. Architecture. Decide: monolithic or headless. Define Custom Post Types, Custom Fields (ACF or native register_meta()), taxonomies.
3. Development. Local environment: Docker (nginx + php-fpm + MariaDB). Git with pre-commit hooks for PHP CS Fixer and ESLint. Deployment via WP-CLI + SSH or Buddy.works CI/CD.
4. Testing. PHPUnit for custom plugins. Playwright for E2E critical scenarios (add to cart → checkout → confirmation). Lighthouse CI in pipeline—fail if Performance Score < 85.
5. Deploy and support. Staging via WP Stagecoach or manual clone. Monitoring—UptimeRobot + Sentry for PHP errors. Plugin updates—via WP-CLI in test environment first.

What you get as a result

• Fully custom theme or modification of existing one
• Configured object caching (Redis/Memcached) and Full Page Cache
• Optimized media files (WebP, srcset, lazy load)
• Code structure documentation and update instructions
• Training for content managers on Gutenberg blocks
• 30-day uptime guarantee after deployment
• Access to repository with full change history

Timeline benchmarks

Pricing is calculated individually after requirements audit. Contact us for a preliminary estimate.

Common mistakes in WordPress development

• Directly editing theme files—all changes lost on theme update. Use a child theme or fully custom theme.
• update_post_meta() in a loop—each call is a separate UPDATE. For bulk operations use $wpdb->update() or update_metadata_by_mid().
• Disabled WP_DEBUG during development—hidden PHP Notices clutter error log and often indicate real issues.
• Storing media in Git—wp-content/uploads in .gitignore, sync via WP-CLI media import or rsync.
• No limit on WP_Query—posts_per_page => -1 on a page with thousands of posts guarantees a timeout.

Why trust WordPress development to professionals?

We have been on the market for over 10 years, completed 80+ projects, hold certifications from Automattic, and have experience with WooCommerce on high-traffic sites. Our solutions account for all nuances: from plugin compatibility to Core Web Vitals requirements (Google recommendations). After project completion you get a documented, tested, and scalable platform.

For a consultation and evaluation of your project—contact us. We respond within one hour during business hours. Get a free preliminary audit today.