Core Bookings 0.10.0 is out. Customers can now use Find next available appointment to see dates with openings and jump to the next available slot.

I've also added a customer workspace and a searchable Operations view, so you can find booking history or failed jobs without digging through the latest activity.

• Customers: review booking and payment history, or adjust unused pack credits with a recorded reason.
• Safer schedule edits: preview the effect on upcoming bookings. Revision checks catch stale forms before they overwrite newer settings.
• Staff availability: give staff permission to manage their own hours and time off.
• Payment recovery: fixes cover balance-checkout retries and reminder schedules after a balance payment.
• Appearance: Default UI provides the built-in design. No UI Style removes the plugin's customer-facing styles while the admin screens stay styled.

The appearance switch is under Bookings > Settings > General > Appearance. Saved block colors and spacing stay intact when styling is disabled.

You can try the updated Core Bookings demo with fictional details. Email and payments are disabled there.

The update is available through WordPress's Plugins screen with an active license. Core Bookings is still in beta, so I'd back up and try a booking on staging before updating a site that takes real appointments.

If something breaks, reply here with the service type and the steps that led to it.

I've released Core Bookings 0.9.0. You can now give each scheduled group session its own seat limit instead of using the same capacity for every time.

For example, a service can have a default of 6 seats, with 4 at 10:00 and 12 at 14:00. Changing one session doesn't change the others.

• Blank uses the default. Clear an override to return that session to the service's normal capacity.
• Zero closes an empty session. It won't appear among the available booking times.
• Existing reservations are protected. A lower limit can't undercut confirmed bookings or active payment, approval and waitlist holds.
• Customers see seats left. The booking form limits their quantity to the selected session's remaining places.
• The checks apply throughout the booking. Rescheduling, payment confirmation, waitlist claims and imports all use the relevant session limit.

There's a new hands-on seat-limit demo where you can try the whole workflow:

1. Compare the live table of custom, default and closed sessions.
2. Try the last available place in the 4-seat session, or book 8 places in the 12-seat session.
3. Open the workshop settings in the demo workspace and change an individual limit.
4. Reschedule or cancel your test booking, then reload the table to see the seats return.

After each daily reset, the 10:00 session starts with 3 sample seats reserved. The demo resets at midnight IST, with its dates and seat limits advancing together. Please use made-up details; payments and outbound email are disabled.

You can update from WordPress Dashboard > Updates with your Core Bookings license active. Core Bookings is still in beta, so I recommend checking your setup on staging first.

If you run into a booking rule that doesn't behave as expected, reply here with the steps and I'll look into it.

I've released Core Bookings 0.8.0 with more control over scheduling, checkout and reminder emails.

The biggest change is optional overlap between services. You can allow a full-day service and a short consultation to share the same staff member's time. The rule works in either booking order, while bookings within each service still follow their capacity limits. External calendar events continue to block availability.

Here's what else is included:

• Native FluentCart checkout: a booking and selected extras can share a single order. FluentCart works on its own; GT Extensions for FluentCart is optional and can enhance the checkout.
• Embedded Stripe payments: customers can pay inside the booking view using Stripe's Payment Element. Hosted Stripe Checkout remains available.
• Brevo reminder templates: schedule up to 5 reminders and choose a different Brevo template for each step. For example, you could send different messages 48 hours, 24 hours and 2 hours before an appointment. WordPress mail remains the default.
• Turnstile protection: optional security checks cover new bookings, waitlist requests and email sign-in requests.
• Developer extensions: registered customer metadata, REST access and booking lifecycle hooks give you more room to build a custom frontend or connect another system.

Core Bookings continues to support guest bookings and optional Core Forms intake. FluentCart's own account-creation settings apply when you use its checkout.

A couple of limits to keep in mind: FluentCart bookings currently collect full payment; deposits and session packs continue through Stripe. Partial refunds on orders containing bookings and other items need manual allocation review.

You can update from WordPress Dashboard > Updates with your Core Bookings license active. Core Bookings is still in beta, so I recommend testing your payment and email connections on staging first.

The hosted demo is available for trying the scheduling and admin workflow. Payments and outbound email are disabled there.

If something breaks after updating, reply here with the steps that led to it and I'll look into it.