Core Operations
Staff checkout for real service-business workflows.
Adjust the final bill, add services or products, record payment, generate receipts, and keep completed sales connected to bookings, customers, and reports.
Owner
Staff-managed
Starts from
Booking or customer
Output
Receipt and history
Not
Self-checkout
Operational console
Staff checkout for real service-business workflows.
Move from appointment to final bill, payment, receipt, and customer history without losing context.
Let staff adjust the final bill when the actual service differs from the original booking.
Keep money-related changes controlled, visible, and tenant-scoped where supported.
The gap
What breaks at the counter
01
The booking is not the final bill
The actual service, products, packages, or credits may change before payment.
02
Payments lose operational context
Payment method, amount, receipt, customer, and booking should stay connected.
03
Completed sales are edited silently
Corrections, voids, refunds, and unpaid balances need controlled visibility where supported.
04
Reports lack source records
Sales and payment reporting depends on clean checkout and receipt history.
Core capabilities
What staff checkout handles
The systems that work together to turn every message into a trackable outcome.
Booking to bill
Start from the booked service and adjust the final bill.
- Keep booking, customer, sale, and receipt connected.
- Change final items before completion where supported.
Services and products
Add what actually happened during checkout.
- Add extra services or retail products.
- Include packages or credit top-ups where supported.
Payments and settlement
Record how the customer paid at the counter.
- Record payment method and amount.
- Support split or mixed settlement where implemented.
Receipts and customer history
Create a durable checkout outcome.
- Generate receipts after checkout.
- Update customer history with completed sales and receipts.
Corrections and audit visibility
Keep money records controlled after completion.
- Completed sales should not be silently edited.
- Voids, refunds, corrections, and unpaid balances should be visible where supported.
AI assist boundary
AI can support context, not money mutation.
- AI should not complete checkout, change payments, issue receipts, or apply discounts.
- Authorized staff action owns checkout.
How it runs
From appointment to locked sale
Open checkout
Staff start from a booking or customer workflow.
Adjust bill
Services, products, packages, credits, or changes are added where supported.
Record payment
Payment method and amount are recorded before completion.
Issue receipt
The completed sale updates receipts, customer history, and reports.
Every step is tracked, every outcome logged — nothing disappears.
The result
Checkout reflects what actually happened.
Staff control the final bill instead of forcing the original booking to be the sale.
Payments, receipts, customer history, and reports stay connected.
Completed money records are handled through controlled correction paths where supported.
Checkout is staff-managed, not customer self-checkout or ecommerce checkout.
Built for your business
See how it works in your industry
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.