WooCommerce Bookings Setup: Calendar, Resources, Sync

A client launches an equipment rental service — a week later, two people have booked the same item for the same time. Sound familiar? We encounter these cases constantly. WooCommerce Bookings is a plugin that turns a regular product into a bookable resource with schedules, availability, and rules. It solves double bookings and manual slot coordination. But without proper setup, it will add headaches rather than order. Over our work, we've configured WooCommerce Bookings for more than 50 projects — from beauty salons to equipment rentals. The average time saved on managing bookings after implementation is up to 10 hours per week, reducing personnel costs by 30–40%. In one project with 15 resources and 20 slots per day, manual coordination took 5 hours per week, after automation — 20 minutes. That's 15 times faster. Our experience ensures your booking system works without glitches. Get a consultation for your scenario.

Model and Booking Types

Bookings works with three entities:

• Bookable product — product with configured slots and prices
• Booking — a specific record: who, when, which product, status
• Resource — additional resource tied to the product (e.g., specific master or room)

Data is stored in wp_posts (type wc_booking) and wp_postmeta. Availability schedule is in the meta field _wc_booking_availability. The plugin supports up to 20 availability rules per product.

Booking Types

For daily rental: duration = 1 day, min duration = 1, max duration = 14. Cost multiplies by number of nights.

Configuring Availability Rules: How to Avoid Mistakes?

Availability is configured through a set of rules with priorities:

Rule 1: All days → Bookable (low priority)
Rule 2: Saturday, Sunday → Not bookable
Rule 3: 31 December → Not bookable (holiday)
Rule 4: Monday 09:00–18:00 → Bookable

Rules are processed in descending priority order. Filter via hook:

add_filter( 'wc_bookings_product_is_available', function( $is_available, $start, $end, $qty, $product ) {
    // custom logic: check external calendar, CRM, etc.
    return $is_available;
}, 10, 5 );

We often use this hook for integration with external systems — for example, to not sell slots if there is already a record in CRM. According to official documentation, the hook allows extending the standard availability check logic.

Why Resources Are Critical for Services?

Resources are independently available units of one product. Example: "Haircut" service with resources "Master Anna" and "Master Sergey". Each resource has its own schedule and can add a markup to the cost. Without resources, a client could book the same haircut from two masters simultaneously — a disaster. We always set has_resources = true for services where distribution matters. The parameter has_persons: true enables selecting number of people, min_persons / max_persons limit the range. Price can be recalculated per person. In one project we built a booking system for saunas: resources — different steam rooms, persons — number of guests. Everything worked without conflicts.

Integration and Notifications

Google Calendar Sync

Bookings supports two-way sync with Google Calendar via the official add-on WooCommerce Bookings — Google Calendar. The scheme:

1. New booking → creates event in Google Calendar via Calendar API
2. Event in Google Calendar → on next sync blocks slot in Bookings

Requires Google Cloud Console: project, OAuth 2.0 credentials, Calendar API enabled. Sync runs via WP-Cron every 15 minutes or manually from settings:

// Force sync
 do_action( 'wc-booking-gcal-sync' );

Notifications

The plugin adds several email types in WooCommerce → Emails:

• New Booking — to manager on creation
• Booking Confirmed — to customer on confirmation
• Booking Reminder — to customer N hours before start (configurable, default 24 hours)
• Booking Cancelled — on cancellation

Reminders are implemented via Action Scheduler — tasks are scheduled at booking confirmation.

Custom Fields

// Add master selection field before booking
add_filter( 'woocommerce_booking_form_fields', function( $fields, $product ) {
    $fields['preferred_master'] = [
        'type'    => 'select',
        'label'   => 'Preferred Master',
        'options' => [ '' => 'Any', 'anna' => 'Anna', 'sergey' => 'Sergey' ],
    ];
    return $fields;
}, 10, 2 );

Common Problems and Solutions

• Slots not appearing on the frontend — most often timezone mismatch: WordPress is set to UTC, while availability rules are set in local time. Check: Settings → General → Timezone should match client expectations.
• Double booking of one slot — has_resources or capacity not configured. Without resources and with booking_duration_type = fixed, explicitly set qty = 1 (max bookings per slot).

Setup Process and Timeline

Setup of one service product with simple schedule takes 1 business day. Multiple resources, Google Calendar, custom fields, date-based pricing logic — 3–4 days.

What's Included?

• Configuration of products and availability rules for your business
• Integration with Google Calendar and external systems
• Custom fields and notifications
• Full documentation and staff training
• Warranty on all work and post-launch support

Contact us for an accurate estimate of your project. Get a consultation for your scenario.

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.