Scobe ecosystem · WordPress

Appointment and business management for WordPress.

Two distinct products for appointment businesses: a focused free plugin and a commercial system for everyday operations.

Scobe Booking Services Center showing service and category management with demonstration figures.
Scobe Booking · Services Center · existing demo screenshot. Figures are demonstration data.

The operational problem

Taking a booking is only one part of running a service business. Staff availability, customer history, session packages and collections all need to stay connected to the appointment.

Lite gives businesses a self-contained starting point. Pro extends the workflow into customer, staff, package and finance management, with delivery for hosted WordPress and Scobe Desktop.

What the product does

  • Scobe Booking Lite: public booking, calendar, staff, services and manual payment records.
  • Scobe Booking Pro: appointments, customer history, staff permissions, packages, collections and expenses.
  • Hosted booking on a business’s own WordPress site, with its data in its own database.
Free · Standalone

Scobe Booking Lite

Booking, availability and daily appointment management. Manual collections record payments made elsewhere.

Commercial · Shared core

Scobe Booking Pro

A broader business workflow: staff permissions, customer history, session packages and financial operations.

  1. 01
    LiteIndependent free plugin
  2. 02
    ProCommercial business workflows
  3. 03
    DeliveryHosted WordPress + Desktop

Engineering decisions

A genuine standalone Lite product

Lite has its own codebase and data tables. Businesses can use it independently; the free product does not carry the commercial product’s feature code.

Shared business logic, distinct delivery

Pro powers both hosted WordPress and the Desktop runtime. Product boundaries matter: a public booking page belongs on a hosted site, while local backup and restore belong to Desktop.

Correctness beyond the happy path

Permissions, appointment status changes and repeated payment events need explicit behavior. Regression coverage targets those boundaries, including preventing duplicate receipts for the same recorded payment.

Reliability and maintenance

  • Capability and request-validation checks on administrative actions.
  • 2,154 unit tests, run on six PHP versions (7.4 to 8.4) before every release.
  • About 4,000 browser checks that use the product the way a salon does, spread over twelve demo sites in parallel.
  • An update rehearsal on a copy of real customer data: table checksums and columns are compared before and after.
  • Tests for permission transitions, notification freshness and update-package integrity.
  • Separate release packaging checks keep development and demo files out of customer archives.
  • Independent review: the author and the reviewer of the code are separate, and a release needs evidence from test output.

Testing and delivery

Pro combines a PHP unit suite with browser regression workflows. CI checks PHP syntax across four PHP versions and verifies archive hygiene. Hosted Pro receives signed updates inside WordPress; Lite has a separate WordPress.org distribution path.

Next case study / 02

Scobe Desktop

Continue exploring

05Contact

Get in touch

For questions about my work or to discuss a project, you can reach me by email.

[email protected]

github.com/ozgurbariserol