If you run a service-based WordPress site with WooCommerce, you’ve likely hit this frustrating wall: you already have your service prices set on WooCommerce products, and now your booking plugin wants you to enter them again in a completely different place. Every time a price changes, you update it in two spots. And then you forget one. And then a customer sees the wrong price.
This is one of the most common pain points with WooCommerce bookings setups — and it’s exactly what Baza Booking Calendar solves with its custom metadata integration.
The Problem: Duplicate Price Management in WooCommerce Booking Setups
Most WooCommerce booking plugins treat pricing as their own isolated system. You configure a price inside the booking plugin, and it has nothing to do with your actual WooCommerce product price. This creates real operational headaches:
- Studio or venue rental prices stored in WooCommerce products
- Service rates managed in ACF (Advanced Custom Fields)
- Pricing tables built in custom post type meta fields
- Minimum booking durations enforced differently per service
With a traditional booking plugin, none of that matters — you’re duplicating data manually and hoping it stays in sync.
The Solution: Pull Prices Directly from WooCommerce Product Meta
Baza Booking Calendar takes a different approach. Instead of maintaining its own isolated price field, it can read the price directly from any custom metadata field attached to the service post — including the standard WooCommerce _regular_price field.
Display the Price from Custom Meta Data
In the service settings, enable Display the price from the custom meta data and enter the meta key you want to pull from. For WooCommerce products this is _regular_price. For ACF fields it’s whatever key name you defined. For any other custom meta — just use that field’s key.

Once enabled, the booking calendar automatically displays the price from that meta field. When you update the WooCommerce product price, the booking calendar reflects it instantly — no double entry, no sync issues.
There’s also a Final Price field that applies a percentage increase on top of the meta price. This is useful when your WooCommerce product represents a base cost and the booking service has an additional markup.
Supported Price Sources
- WooCommerce product price — meta key
_regular_price - WooCommerce sale price — meta key
_sale_price - ACF number or text field — use the field name you defined in ACF
- Any custom post meta field — any meta key from your theme or plugin
Minimum Booking Hours from Custom Metadata
The same meta-driven logic applies to minimum booking duration. Instead of hardcoding a minimum number of hours per service, you can point the calendar to a metadata field that already stores this value.
Enable Display the minimum number of hours or time slots from custom metadata and enter the meta key — for example _minimum_amount. The calendar will enforce that minimum automatically based on whatever value is stored in that field for each individual service.
This is especially useful when:
- Different services have different minimum durations managed in a spreadsheet or external system synced to meta fields
- You use ACF to let editors control minimum booking time per venue without touching plugin settings
- You manage dozens of services and want one centralized field to control minimums
Real-World Use Cases
Photography Studios and Creative Spaces
A photo studio sells hourly rentals as WooCommerce products with variable pricing by room. Baza Booking Calendar reads _regular_price from each product and displays it in the booking calendar automatically. The studio owner updates WooCommerce — the booking form updates itself.
Rental Services with ACF Pricing Sheets
An equipment rental company uses ACF to store hourly rates and minimum rental durations per item. The booking calendar reads both fields directly — no separate booking plugin configuration needed per item.
Multi-Service Venues
A co-working space with 15 different rooms manages all pricing in WooCommerce. Instead of configuring 15 services separately in a booking plugin, they set one meta key and all 15 services pull their prices automatically.
How This Compares to Other WooCommerce Booking Plugins
The official WooCommerce Bookings plugin ($249/year) and most alternatives like PluginHive or YITH Bookings manage pricing internally with no native way to sync from existing WooCommerce product meta. You configure pricing separately in the booking product settings, which means maintaining two separate price sources for every service.
Baza Booking Calendar was built for WordPress sites that already have a data structure — WooCommerce products, ACF fields, custom post types — and need a booking layer that respects that structure rather than replacing it.
Setup in 3 Steps
- Open any service in Baza Booking Calendar and scroll to Settings
- Enable Display the price from the custom meta data and enter your meta key (e.g.
_regular_price) - Optionally enable Display the minimum number of hours from custom metadata and enter the meta key for minimum duration
That’s it. The calendar reads both values automatically from that point forward.
Frequently Asked Questions
The meta key _regular_price is stored at the product level. For variable products, you would point to the specific variation meta or use an ACF field that stores the consolidated price for booking purposes.
Yes. The Final Price field accepts a percentage increase that gets applied on top of the meta price automatically.
The calendar falls back to the price configured directly in the service settings. No broken displays — the fallback is always safe.
Yes. ACF stores field values as standard WordPress post meta. Use the ACF field name (not the field key starting with field_) as the meta key in the Baza Booking Calendar settings.