Author Archive

Owners can manager their booking resources the same way they already control listing. On plugin activation, Listeo Booking Plus will  automatically create a Manage Resources page and set correct content and template for that. In case it didn’t happen, here’s instruction

Setting up the page

1. Create a new page (e.g. “Manage Resources”).
2. Drop the shortcode in:

   [lbp_manage_resources]

3. Add the page to the owner’s dashboard menu (you can configure the dashboard menu under Listeo Core → Pages → Resource page).

What owners can do from this page

• Submit a new resource
• Edit any of their own resources.
• Duplicate a resource to spin up a near-identical one quickly.
• Import/Export iCal – import or export bookings to their personal calendar
• Pause a resource — temporarily takes it out of the booking pool without deleting it.
• Delete a resource permanently.

Each resource has its own availability calendar and its own iCal export / import URLs. This mirrors Listeo Core’s per-listing iCal flow — if you already use it for listings, the resource version will feel identical.

Each resource gets its own subscribe URL so external calendars (Google, Apple, Outlook, Airbnb, Booking.com) always see the right slice of the schedule.

Exporting a resource’s bookings

1. Open the Manage Resource page for your listing
2. Find the iCal Export section.
3. Copy the subscribe URL.
4. Paste it into Google Calendar (Other calendars → From URL), Apple Calendar (File → New Calendar Subscription), or any iCal-compatible app.

The feed updates every time the external app re-fetches it (the cadence is controlled by the receiving calendar — typically a few hours).

Importing external calendars into a resource

1. In the iCal Import section, click Add Calendar.
2. Enter a friendly name (e.g. “Airbnb — Apartment 4”) and the external .ics URL.
3. Save.

Listeo Booking Plus pulls events from each imported URL on a schedule and creates blocked bookings on the resource. Imported events are tagged so a later re-fetch can update or remove them cleanly without disturbing real bookings.

Conflict rules

• A booking from your site always wins — imported events never overwrite an existing booking.
• An imported event that overlaps with an existing import is updated, not duplicated.
• Removing an imported calendar removes only its events; manually-added bookings stay put.

If you run the same event every week, you don’t need to create 52 listings. Listeo Booking Plus generates occurrences from a single rule and lets you override any individual date without touching the rule itself.

Defining a recurrence rule

1. Edit an Event listing.
2. Scroll to the Recurrence meta box.
3. Pick a pattern: Daily, Weekly, Monthly, or a Custom rule.
4. For Weekly, pick the days of the week. For Monthly, pick the day-of-month or a Nth-weekday rule.
5. Set the start date and (optionally) an end date.
6. Save.

How occurrences are generated

A background cron job materialises future occurrences up to the Recurrence lookahead window – 12 months by default, configurable in Listeo → Settings → Booking. As time passes, the cron extends the window so there’s always ~12 months of bookable dates ahead.

You don’t need to “regenerate” anything manually — saving the listing triggers an immediate refresh of upcoming occurrences.

Per-occurrence overrides

Sometimes one specific date needs to be different — a higher price for New Year’s Eve, a smaller capacity because half the venue is being renovated, or just cancelling a single class because the instructor’s on holiday.

1. In the Occurrences panel on the listing edit screen, find the date you want to change.
2. Click Override.
3. Set the override price, override capacity, or Cancel this occurrence.
4. Save.

The recurrence rule itself stays unchanged — the override applies only to that one date. Remove the override and the date falls back to the rule’s defaults.

What customers see

The single-event page shows a date picker with all upcoming occurrences. Cancelled occurrences disappear; occurrences with overridden prices show the override price; sold-out occurrences are greyed out.

Listeo Booking Plus turns Listeo’s Event listing type into a real ticketing system. You can define multiple ticket types per event, set capacity per type, control sale rules, and (optionally) collect attendee details at checkout.

Defining ticket types

1. Edit an Event listing.
2. Scroll to the Ticket Types meta box.
3. Click Add ticket type for each tier — for example: Adult, Child, VIP, Early Bird.
4. For each tier set:
   • Label — what customers see (“Adult”, “VIP”).
   • Price — per-ticket price in your store currency.
   • Capacity — how many of this ticket type are available. Leave blank for “as many as the event capacity allows”.
   • Min & Max – set how many tickets user could buy at once.
   • Sales Start and Sales End date – when tickets will be available

How capacity works

Booking Plus respects two capacity limits at the same time: the per-ticket-type capacity (the cap you set on each tier) and the event total capacity (Core’s listing-level field). Whichever is reached first stops sales for that tier.

Example: an event with total capacity 100 and a “VIP — 20 tickets” tier. Once 20 VIP tickets are sold, the VIP tier shows as sold out even if total ticket sales are well below 100.

The front-end ticket selector

Customers see a quantity selector per ticket type. They can mix tiers in a single booking (2 Adult + 1 Child + 1 VIP), and the booking summary breaks each line out for transparency.

Collecting attendee names and emails

Toggle Collect attendee names and / or Collect attendee emails in Listeo Core  → Listeo Booking Plus Settings. When on, the confirmation step shows one name (and / or email) field per ticket. Names appear on the individual e-tickets; emails are stored against the booking so each attendee can be contacted directly.

Reservation holds

When a customer clicks “Book” and lands on the confirmation step, Booking Plus puts a temporary hold on the tickets they’ve selected. While the hold is active, those tickets are invisible to other customers — the inventory shows fewer seats, and the ticket selector won’t let anyone else buy them.

If the customer completes checkout, the hold becomes a real booking. If they abandon the page (or the timer runs out), the hold expires and the seats go back into inventory.

Configuration

• Reservation hold time (minutes) — Listeo → Settings → Booking. Default: 15.
• Raise it if your checkout requires a slow third-party step (a complex payment redirect, a manual approval).
• Lower it on high-demand events where seats need to recycle quickly when checkout is abandoned.

What happens when a hold expires

The customer doesn’t get an aggressive error — when they submit the form, the system re-checks availability and tells them politely that their hold expired and to pick again. No silent overselling.

Individual ticket codes

When Generate individual ticket codes is on (default), Booking Plus creates one unique scannable code per ticket — not per booking. A family that buys 4 tickets gets 4 codes.

Where customers see their codes

• In the booking confirmation email.
• On the booking detail page in their dashboard.
• Each code includes a QR for the door scanner.

Why per-ticket and not per-booking

Door scanning works ticket-by-ticket: each attendee can arrive separately, get their own code scanned, and the system marks just that ticket as used. With one code per booking, a single scan would either let the whole family in (no count) or block subsequent scans (annoying).

If you really do want per-booking codes (small private event, you trust the headcount), switch the setting off and the legacy single-code-per-booking behaviour comes back.

The booking popup is the customer-facing modal used by every booking type — Services, Rentals and Events. Booking Plus replaces Listeo Core’s inline booking widget with this multi-step popup whenever the listing is configured to use Booking Plus features (resources or ticket types).

The steps

Customising appearance

Three colors in Listeo → Settings → Booking → Booking Popup Appearance control the look:

• Popup sidebar — color — main sidebar background. Defaults to #2d2d32 (close to black).
• Popup sidebar — gradient end (optional) — set this for a gradient sidebar; leave blank for solid.
• Popup accent color — used for the dot before each section label, the active step number, the “Next” button, and selection highlights. Defaults to #3b82f6 (blue).

Values are injected as CSS custom properties before the popup paints — no flicker of the old color when the page loads.

Mobile behaviour

The popup goes full-screen on mobile and the multi-step navigation collapses to a top progress bar. Sidebar content moves to a collapsible header so the form always has the full screen width.

Overriding the templates in a child theme

Every step is a separate template file you can override (see  Customizing Templates):

• templates/booking/modal.php — the popup shell.
• templates/booking/modal-sidebar.php — the left sidebar.
• templates/booking/modal-step-datetime.php
• templates/booking/modal-step-resource.php
• templates/booking/modal-step-confirm.php
• templates/booking/modal-step-success.php

For Service listings,  Listeo Booking Plus adds two opt-in features that change how the booking widget interprets service selections.

Service durations

Off by default. Turn on with Enable service durations in Listeo Core → Booking.

When on, each bookable service on a listing gains a Duration field. Set a duration in minutes (e.g. 90 for a 90-minute massage), and when a customer picks that service the booking widget reserves enough consecutive slots to cover it.

Example with 30-minute slots:

• Customer picks a 90-min service starting at 10:00.
• Booking widget blocks 10:00, 10:30 and 11:00 — three consecutive slots.
• No other customer can book any of those three slots, even though only one was “selected”.

This is the right model whenever a service is longer than your underlying booking grid.

Individual Services

Off by default. Turn on with Enable Individual Services in Listeo Core → Booking.

When on, each service has an Individual service toggle. The rule:

• A customer can pick at most one Individual service per booking.
• They can stack as many non-Individual services as they like on top — these act as add-ons.

The model: an Individual service is “the appointment” (haircut, massage, consultation); non-Individual services are “the add-ons you can tack on” (scalp treatment, hot towel, extra 15 min). This matches how most service businesses actually quote work.

If you don’t sell anything that fits the “main + add-on” pattern, leave this off – the regular Listeo Core behaviour applies and customers can pick any combination.

Slot spans

When service durations are on, the underlying mechanism is called slot spans — the booking record itself stores the span (start slot + number of slots) so that conflict checks, the calendar and emails all see one logical booking spanning multiple slots rather than several separate ones.

You don’t configure slot spans directly — they’re how durations get expressed under the hood. The main effect for you is that the bookings admin shows one row per booking (not one per slot), which keeps the list readable.

Listeo Booking Plus extends Listeo Core’s pricing with repeatable fees — costs that scale with the booking instead of being a flat add-on.

What’s a repeatable fee?

Any cost that’s calculated per unit-of-something. Common examples:

• Per-guest fee — $5 per guest on a tour or event.
• Per-night cleaning fee — $25 per night on a rental.
• Per-attendee surcharge — VIP service fee charged per ticket.

Compare to a flat fee (Listeo Core’s existing feature), which is the same regardless of party size or length of stay.

Adding a repeatable fee

1. Edit the listing.
2. In the pricing / extras section, find Repeatable Fees.
3. Click Add fee and set:
   • Label (shown in the booking summary).
   • Amount per unit.
   • Unit — guest, night, ticket, hour, etc.
4. Save.