BookFlow Layman-friendly documentation
Ctrl+K
BookFlow V1 Overview
BookFlow operating guide

Understand the whole booking platform without reading code.

BookFlow is a multi-tenant booking system for service businesses. This guide explains signup checkout, tenant creation, customer dashboard, wallet payments, vendor admin operations, programs, website pages, integrations, and system proof using screenshots and simple examples from Nimbus Wellness Studio.

Quick Start Links

Public Platform

Platform home Plans Directory Create workspace Login Customer dashboard Demo mailbox Demo readiness

Nimbus Tenant

Storefront Booking page Vendor admin Website pages Integrations
Note for developers: Before changing seeded demo, builder, integration, or membership flows, open Developer Notes for the safe reset paths, implementation map, and test commands.
Buyer-ready docs: Use Install And Seed, Demo Flow, What BookFlow Is, and Developer Notes when validating a fresh install. Release support and licensing notes should stay with the private source package, not the public docs copy.

Demo Credentials

User type Email Password What to open first
Demo admin admin@ovion.tech Demo@12345 Nimbus vendor admin
Staff examples avery.stone@nimbuswellness.test, lina.park@nimbuswellness.test Demo@12345 Operational admin pages allowed by role
Customer examples Seeded customers use @customer.test emails Demo@12345 Customer portal

Storefront Reseed With Media

Use this command when Nimbus needs a complete fresh storefront: tenant media, rich metadata, homepage builder blocks, website pages, drafts, and revision snapshots. 

php artisan bookflow:storefront-reseed

The full flow is covered in Storefront And Website and Storefront And Customer Reference.

Seeded Nimbus storefront hero image
Homepage hero media copied into the Nimbus vendor media library.
Seeded Nimbus treatment room image
Treatment room media used by service and collage builder sections.
Seeded Nimbus consultation image
Consultation image used by about and lookbook page sections.

Big Picture

The easiest way to understand BookFlow is to separate it into three layers. The platform sells and hosts the SaaS. Each vendor tenant runs a business workspace. Customers use public booking pages, wallet payments, support handoff, and the central customer portal.

Platform->Plans and tenants->Vendor workspace->Storefront and admin->Customer booking and portal

Platform

Owns plans, signup, sandbox subscription checkout, directory, global login, customer dashboard, and the portal entry point.

Vendor Tenant

Owns services, staff, locations, resources, bookings, website pages, payments, no-show controls, reports, programs, AI operations, and integrations.

Customer

Books from the storefront, pays from a signed payment page or wallet, manages bookings from the portal, and comes back through rebooking actions.

Core Screenshots

BookFlow platform home page
The platform home explains the product and routes buyers to plans, directory, login, or signup.
Nimbus storefront home page
The tenant storefront is the public customer entry point for services, staff, booking, programs, and trust pages.
Nimbus vendor dashboard
The vendor dashboard gives the business a workspace view across bookings, revenue, operations, and alerts.
BookFlow customer portal
The customer portal shows next best actions like pay, rebook, review, use benefits, and ask for help.

How Things Connect

Thing user sees Connected system Why it matters
Service card on storefront Vendor admin -> Services Changing duration, price, deposit, or active state changes what customers can book next.
Available slot Availability engine The slot exists only if location, staff, resource, working hours, time off, and existing bookings allow it.
Payment balance Invoice and receipt records Payments update booking balance, receipt history, customer portal status, and revenue reports.
Wallet top-up Customer wallet checkout session Sandbox approval updates wallet balance, ledger, notifications, demo mailbox, and future payment options.
FAQ, privacy, terms, contact Website pages CMS Vendors edit these once; storefront header/footer and booking agreement links read the published pages.
CRM lead conversion Integrations -> Lead Intake A synced external lead becomes a real BookFlow booking with an external mapping record.

Recommended Reading Order

  1. Read What BookFlow Is for the simple product model.
  2. Open Demo Flow and follow the exact Nimbus walkthrough.
  3. Use Platform Owner to understand signup checkout, tenant creation, directory proof, dashboard, and demo mailbox.
  4. Use Customer Journey to understand booking, wallet top-ups, payment, portal, review, support, and rebooking.
  5. Use Vendor Admin to understand how the business manages operations, no-shows, calendar sync, staff mobile, AI work, and scheduled reports.
  6. Use module pages when you need details about bookings, payments, programs, integrations, or permissions.
  7. Use the Screen Reference pages when you need every field, KPI, chart, table column, action, and connection explained.

Workflow Playbooks

Use these pages when someone asks what happens after an integration event, membership benefit, payment, support request, or complete demo step.

Hub

Workflow Playbook Hub

One entry point for integrations, memberships, and the complete demo scenario.

Open hub
Integrations

Integration Manual

Provider-by-provider cause/effect: connect, run, map, local result, proof screen, and next action.

Open manual
Membership

Benefits Manual

Plan rules, wallet, booking benefit snapshot, payment ledger, usage ledger, and reports.

Open benefits manual
Demo

Complete Demo Script

Presenter-ready act map with persona, action, result, visible proof, and narration.

Open script

Screen Reference

The Screen Reference is the detailed manual layer. It is written for support staff, vendor trainers, QA testers, and non-technical buyers who need to know exactly what every visible field, chart, table column, and button means.

Platform Screens

Home, plans, directory, signup, and login with every signup field explained.

Open reference

Storefront And Customer

Storefront booking, trust pages, payment page, customer portal, reviews, wallet, and support.

Open reference

Vendor Admin Indexes

Dashboard, bookings, calendar, services, staff, locations, resources, and website indexes.

Open reference

Vendor Admin Forms

Create/edit forms for bookings, services, staff, locations, resources, website pages, homepage, and settings.

Open reference

Analytics And Retention

Programs, receptionist, insights, reports, retention queues, review loops, and wallet examples.

Open reference

Integrations And Settings

Connector health, connector fields, lead conversion, activity logs, contracts, mappings, permissions, and notifications.

Open reference

Workflow Playbooks

Visual hub for integration workflows, membership benefits, and the complete demo scenario with annotated screenshots and proof trails.

Open playbook hub
Next: What BookFlow Is ->