WooCommerce Setup for Your WordPress Online Store

Note: When a WooCommerce WooCommerce store starts selling, owners often face unexpected issues: slow checkout, incorrect tax calculation, shipping difficulties. In 70% of cases, the root cause is suboptimal settings. Over 5 years, we've set up 50+ stores and know how to avoid common mistakes. Once a client with an electronics store came to us: selecting a variable product took 8 seconds. The cause was N+1 database queries when loading attributes. We solved it by caching meta-data via transients and disabling unnecessary plugins. Order WooCommerce setup – and your store will be ready to launch in 2-3 days.

Why WooCommerce Requires Refinement?

Out of the box, the plugin provides a catalog, cart, checkout, and basic analytics. But for the Russian market, it's a skeleton, not a finished store. No patronymic field, no VAT rates of 10/20%, no popular payments (YooKassa, Sberbank), no shipping with free threshold. Everything has to be configured. Unlike Easy Digital Downloads (digital goods only), WooCommerce handles any product type but requires customization for specific business. Additionally, the standard checkout is not adapted for legal entities – it needs an INN and KPP block. Also, the default installation is not optimized for Core Web Vitals – many scripts hurt LCP and CLS. We configure async loading of resources and defer scripts not needed for initial rendering.

How to Properly Configure Taxes and Shipping in WooCommerce?

Tax rates and shipping zones are the foundation of correct store operation. We set them programmatically to avoid manual entry and errors. For Russia, two VAT rates are important: 20% and 10% (for discounted goods). Shipping is configured with a free threshold and fixed cost. For multi-regional trade – zones by federal districts with different rates.

Installation and Configuration

wp plugin install woocommerce --activate
wp wc tool run install_pages --user=1
wp option update woocommerce_default_country "RU"
wp option update woocommerce_currency "RUB"
wp option update woocommerce_currency_pos "right_space"
wp option update woocommerce_price_thousand_sep " "
wp option update woocommerce_price_decimal_sep ","
wp option update woocommerce_calc_taxes "yes"

Tax Rates for Russia

Programmatically add VAT rates 20% and 10%:

$tax_rates = [
    [
        'country'  => 'RU',
        'rate'     => '20.0000',
        'name'     => 'VAT 20%',
        'priority' => 1,
        'compound' => false,
        'shipping' => true,
        'class'    => '',
    ],
    [
        'country'  => 'RU',
        'rate'     => '10.0000',
        'name'     => 'VAT 10%',
        'priority' => 1,
        'compound' => false,
        'shipping' => false,
        'class'    => 'reduced-rate',
    ],
];
foreach ($tax_rates as $rate) {
    WC_Tax::_insert_tax_rate($rate);
}

Important: For correct tax calculation, ensure WooCommerce setting "Calculate taxes based on store address" is enabled.

Shipping Setup

Create a "Russia" zone with fixed cost 350 rubles and free shipping from 5000 rubles:

$zone = new WC_Shipping_Zone();
$zone->set_zone_name('Russia');
$zone->add_location('RU', 'country');
$zone->save();

$zone->add_shipping_method('flat_rate');
$zone->save();

update_option("woocommerce_flat_rate_{$instance_id}_settings", [
    'enabled'      => 'yes',
    'title'        => 'Shipping within Russia',
    'cost'         => '350',
    'free_min_amount' => '5000',
]);

For multi-regional stores, you can add zones by federal districts with different rates.

Custom Checkout Fields

Add patronymic and INN via hook:

add_filter('woocommerce_checkout_fields', function (array $fields): array {
    $fields['billing']['billing_patronymic'] = [
        'label'       => 'Patronymic',
        'placeholder' => 'Ivanovna',
        'required'    => false,
        'class'       => ['form-row-last'],
        'priority'    => 25,
    ];
    $fields['billing']['billing_inn'] = [
        'label'    => 'INN',
        'required' => false,
        'class'    => ['form-row-wide', 'legal-field'],
        'priority' => 90,
    ];
    return $fields;
});

add_action('woocommerce_checkout_update_order_meta', function (int $order_id): void {
    if (!empty($_POST['billing_patronymic'])) {
        update_post_meta($order_id, '_billing_patronymic', sanitize_text_field($_POST['billing_patronymic']));
    }
    if (!empty($_POST['billing_inn'])) {
        update_post_meta($order_id, '_billing_inn', sanitize_text_field($_POST['billing_inn']));
    }
});

Payment Gateway Integration (Example)

Implement a custom gateway based on WC_Payment_Gateway. In the callback, verify HMAC-SHA256 signature:

class WC_My_Gateway extends WC_Payment_Gateway {
    // ... full implementation in codebase
}
add_filter('woocommerce_payment_gateways', function (array $gateways): array {
    $gateways[] = 'WC_My_Gateway';
    return $gateways;
});

For popular gateways (YooKassa, Tinkoff), use ready plugins – faster and more reliable.

How to Choose a Payment Gateway for Russia?

How to Improve WooCommerce Performance?

To speed up page loading, we use a combination: page cache (Varnish or Nginx FastCGI Cache), Redis object caching, disabling WooCommerce scripts on pages where they are not needed (e.g., homepage). Also disable unnecessary emoji and oEmbed. This reduces TTFB and improves LCP. For checkout, we apply lazy loading of scripts that do not affect functionality.

Common WooCommerce Configuration Errors

What's Included in Turnkey Setup?

Turnkey setup includes: installation and initial configuration of WooCommerce, setting up tax rates (VAT 20/10% and others), shipping zones and methods (fixed, by amount, courier), custom checkout fields (patronymic, INN, comment), integration of 1-2 payment gateways, email notifications for managers and clients, testing all order scenarios, setup documentation, and admin training.

Why Is Our WooCommerce Setup More Advantageous?

WooCommerce is 1.5 times easier to configure than Magento, and loads twice as fast on typical hosting. But most importantly, we provide a 30-day warranty on all work. If an error is discovered after launch (e.g., incorrect VAT calculation), we fix it for free. In 5 years, we have never violated this warranty. Get a free consultation for your project – no cost.

Timeline and Cost

Basic setup with one gateway and standard shipping: 2-3 days. Complex setup (up to 3 gateways, custom checkout, 1C integration): 5-8 days. Cost is individually calculated after an audit of the current state. Contact us to evaluate your project.

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.