1 min read
MyBookaro creates several custom tables. All use the WordPress table prefix (e.g. wp_bookaro_*).
Lite tables #
| Table | Purpose |
|---|---|
{prefix}bookaro_bookings | Core booking records: id, listing_id, service_id, customer_id, provider_id, status, dates, notes. |
{prefix}bookaro_provider_availability | Weekly availability flags: provider_id, weekday (0–6), is_open. |
{prefix}bookaro_provider_timeslots | Time slot templates: provider_id, weekday, start_time, end_time, interval_m. |
{prefix}bookaro_provider_exceptions | Date-based exceptions: provider_id, date, is_open, optional custom hours. |
{prefix}bookaro_notification_logs | Email send history: booking_id, channel, template_key, status, error_message. |
Pro tables #
{prefix}bookaro_chat_threads | Booking-scoped chat thread headers + last_read state per role. |
{prefix}bookaro_chat_messages | Chat messages: thread_id, user_id, user_role, content, created_at. |
{prefix}bookaro_staff | Provider-managed staff roster. |
{prefix}bookaro_custom_profiles | Custom form profile data: data_json, visibility, share_token + expiry. |
{prefix}bookaro_export_log | CSV export audit log: type, purpose code, range, filters_json, IP, user agent. |
Schema migrations #
Schema changes happen on plugin upgrade via dbDelta(). The plugin tracks the schema version in the bookaro_db_version option.
Indexes #
Tables have indexes on provider_id, customer_id, booking_date, status for fast lookup. Custom queries on these columns should be performant.
Cleanup on uninstall #
By default, uninstall does not drop tables. Enable “Delete all MyBookaro data on uninstall” in Settings → General to opt in to full cleanup.
