MyBookaro

Free WordPress appointment booking and scheduling plugin with multi-provider dashboards. Works on single-business sites, MyListing directories, Listeo, Listdom, ListingPro, and any custom directory CPT.

MyBookaro is a provider-based booking engine for WordPress. It is strongest on MyListing Directory sites, fully supports a real Single Business no-listing path, and also supports guided Generic Directory setups where you intentionally control provider mapping, services, and placement.
Lite covers booking requests, availability, dashboards, reminders, and diagnostics. Pro adds WooCommerce payments, Google Calendar + iCal sync, booking chat, SMS/webhooks, reports, and exports.
Generic Directory is a guided lane and requires intentional mapping/services/placement decisions; it is not a universal automatic adapter for every theme.
Booking chat is Pro only: MyListing Directory uses native MyListing messaging, while Generic Directory and Single Business use MyBookaro booking chat with an active, valid Pro license.

MyBookaro is an independent plugin compatible with MyListing and is not affiliated with or endorsed by 27collective.

MyListing, Listeo, Listdom, ListingPro, and WooCommerce are trademarks of their respective owners. MyBookaro is independent and is not affiliated with, endorsed by, or sponsored by any of them; their names are used only to describe compatibility.

Getting started

• Run MyBookaro > Setup Wizard.
• Choose your lane first: MyListing Directory, Single Business, or guided Generic Directory.
• MyListing Directory: keep Integration Mode on Auto-detect/MyListing Directory, confirm sidebar booking entry, and set the repeater class.
• Single Business: no listings required. Set Default Provider, assign booking/services/dashboard pages, place booking UI on normal pages, then test one booking.
• Generic Directory (guided): choose provider mapping + services model, assign pages, place booking UI, then run lane diagnostics before launch.
• In MyBookaro > Settings > Email, enable reminder and review invite emails if you want automated follow-ups.
• Complete the lane-aware checklist in MyBookaro > Getting Started.
• Review the operational summary in MyBookaro > Getting Started so you can see current safeguards and launch defaults before go-live.
• Before opening support requests, review the operational summary first, then run MyBookaro > System Status, copy the masked support snapshot, and attach the Support Bundle JSON only when deeper diagnostics are needed.

Official product lanes

MyBookaro officially supports these lanes:

• MyListing Directory (strongest lane): fastest launch and lowest support risk.
• Single Business (real no-listing lane): provider-first booking for service businesses on normal pages.

• Generic Directory (supported guided lane): flexible for custom directory setups with intentional mapping/services/placement decisions.

• MyListing Directory | Provider mapping: Listing owner/provider from MyListing listing context | Services model: MyListing repeater services | Placement model: Directory listing template (sidebar booking entry) or shortcode/block placement | Dashboards/pages needed: Provider and customer dashboards (or WooCommerce My Account mode).

• Single Business | Provider mapping: Default Provider (provider-first, no listing requirement) | Services model: Provider Only by default (Admin Only/Hybrid optional) | Placement model: Normal pages or shortcode/block placement | Dashboards/pages needed: Booking page, services page, provider dashboard page, and customer dashboard page.
• Generic Directory | Provider mapping: Listing Author or Listing Meta Key | Services model: Provider Only, Admin Catalog Only, or Hybrid | Placement model: Directory templates, normal pages, shortcode/block only, or CSS selector insertion | Dashboards/pages needed: Booking page and dashboard pages when using shortcode dashboard mode.

Generic Directory presets

For Generic Directory lanes, Setup Wizard includes guided presets:
* Provider-Owned Directory (Listing Author + Provider Only)
* Editorial + Meta Key Directory (Meta Key + Provider Only)
* Shared Catalog Directory (Listing Author + Admin Catalog Only)
* Legacy installs may still run as Generic Directory (legacy compatibility profile active). This stays inside the Generic Directory lane and is not a separate site type.

MyListing repeater setup

To read services from MyListing repeater rows, set Row CSS Class to mybookaro_services in MyListing > Listing Type > Repeater. You can change the class/prefix in MyBookaro > Settings > General.

Lite features

• Booking requests flow for MyListing Directory listings and Single Business pages (request-to-book)
• Provider availability management (weekly schedule, timeslots, date exceptions)
• Provider and customer dashboards
• Booking workflows and status updates
• Email notifications with template toggles (new booking/status, 24h + 1h reminders, review invites)
• Getting Started onboarding, operational summary, and setup checklists
• System Status diagnostics page with masked copy/share summaries, launch-readiness checks, and support bundle export
• Blocks and shortcodes for booking entry points and dashboards

Lite and Pro comparison

• MyListing Directory – Included in Lite, strongest lane, fastest launch
• Single Business – Included in Lite, real no-listing lane
• Generic Directory – Included in Lite, guided lane for custom directory setups
• Core request-to-book, availability, dashboards, reminders, and diagnostics – Included in Lite (also in Pro)
• WooCommerce payments – Pro only
• Google Calendar + iCal – Pro only (iCal does not boot in Lite tabs/dashboards)
• Booking chat – Pro only; MyListing uses native MyListing messaging, Generic + Single Business use MyBookaro chat with an active, valid Pro license
• Staff – Pro only; manual roster + assignment workflow (no customer-selected staff and no automatic routing/dispatch)
• Reports / exports / webhooks / SMS – Pro only
• In Lite, any Pro tabs or Pro fields shown in Settings are disabled read-only previews and do not save settings.
• Full Pro functionality requires the separate MyBookaro Pro plugin installed with a valid license key.

Notifications, reminders, and review invites

• Reminder emails (reminder_24h, reminder_1h) are queued when a booking is approved.
• Reminder emails send only for future reminder times.
• Review invite emails are queued after a booking is completed.
• Scheduled reminder/review invite delivery runs through WordPress Cron.

Compatibility

• Compatible with MyListing
• Works with the MyListing theme
• Provider mapping supports MyListing listing owners
• Official support lanes: MyListing Directory, Single Business, and guided Generic Directory.
• Generic Directory is guided, not automatic universal theme compatibility.
• WooCommerce is optional and only required for WooCommerce My Account UI mode

Blocks and shortcodes

Blocks (Gutenberg):
* MyBookaro: Booking Button (bookaro/booking-button)
* MyBookaro: Booking Form (bookaro/booking-form)
* MyBookaro: Provider Dashboard (bookaro/provider-dashboard)
* MyBookaro: Customer Dashboard (bookaro/customer-dashboard)
* MyBookaro: Services Cards (bookaro/services-cards)

Shortcodes (examples):
* [bookaro_booking_button listing_id="123" provider_id="45" service_label="Consultation" price="49"]
* [bookaro_booking_form listing_id="123" auto_open="true"]
* [bookaro_services_cards listing_id="123" columns="3" show_price="1" show_duration="1"]
* [bookaro_provider_dashboard]
* [bookaro_customer_dashboard]

Data and privacy

MyBookaro stores booking and availability data in your WordPress database so booking workflows can run.

Data types include:
* Booking records (listing, provider, customer, dates, status, notes)
* Provider availability rules, timeslots, and exceptions
* Notification logs for delivery diagnostics

By default, uninstall keeps data. To remove all plugin data, enable “Delete all MyBookaro data on uninstall” before uninstalling.

Source code

The compiled JavaScript bundles in mybookaro/dist/*.js are produced from the Vue.js source files shipped in mybookaro/assets/*.vue and mybookaro/assets/components/**/*.vue. To rebuild from source: install Node.js + npm, run npm install inside the plugin directory, then npm run build:lite. Build configuration is in the vite.*.config.js files in the plugin root.