Core Operations

A catalog built for service-business operations.

Manage services, products, packages, credit top-ups, prices, member prices, and categories so bookings and staff checkout stay consistent.

Items

Services and products

Pricing

Base and member

Use

Booking and checkout

Not

Public storefront

Runbook · Customer Operations
LIVE

Operational console

A catalog built for service-business operations.

1

Keep services, products, packages, and prices connected to the daily workflow.

2

Separate operational resources from the items the business sells or delivers.

3

Support booking and checkout without presenting Catalog as a public ecommerce storefront.

The gap

What breaks without a catalog foundation

01

Price lists are rebuilt at checkout

Staff should not manually recreate services, products, packages, and prices for each bill.

02

Bookable and sellable get mixed

Some items are services, some are products, some are packages, and some can be booked and sold.

03

Resources become catalog items

Rooms, chairs, machines, and staff are operational capacity, not sellable catalog entries.

04

History changes after edits

Old receipts need sale snapshots so later catalog edits do not rewrite the past.

Core capabilities

What Catalog organizes

The systems that work together to turn every message into a trackable outcome.

Services and bookable items

Create services that can be booked, charged, or both.

  • Keep service duration and booking needs separate from checkout details.
  • Connect booked services to the final bill without locking the bill forever.

Products and packages

Support real counter sales beyond appointments.

  • Add retail products for staff checkout.
  • Define prepaid packages or sessions where supported.

Credit top-ups

Keep paid and promotional value clear where supported.

  • Track credit top-up products.
  • Separate promo or free value from paid credit where supported.

Categories and prices

Make item organization and price control explicit.

  • Group items by category or subcategory.
  • Store base price and member price where supported.

Checkout snapshots

Preserve what was sold at the time of sale.

  • Keep receipts accurate after catalog edits.
  • Support reporting by service, product, package, or category.

AI assist boundary

AI can use catalog information where enabled.

  • AI should not invent prices.
  • AI should not expose internal pricing or select unsupported items without validation.

How it runs

From catalog item to receipt

01

Item defined

Services, products, packages, credits, and prices are organized in Catalog.

02

Item used

Bookable items support appointments; sellable items support staff checkout.

03

Bill adjusted

Staff can add or adjust items during checkout where supported.

04

Snapshot preserved

Receipt and reporting records keep the item state from the sale.

Every step is tracked, every outcome logged — nothing disappears.

The result

Items and pricing stay operationally consistent.

01Items

Services, products, packages, credits, and prices live in one operational catalog.

02Prices

Staff understand what can be booked, sold, or both.

03Bill

Checkout uses structured items instead of manual price-list reconstruction.

04History

Catalog supports operations without becoming a public ecommerce storefront.

Ready to see how Runbook would work for your business?

We’ll walk you through the workflow, show how enquiries move from message to action, and help you evaluate the best starting setup.