The weekly calendar and searchable list expose the same client-visit record.
See the visit in a calendar or work it from a focused list
Review the current week in the weekly calendar, or filter and search the displayed appointment list. The record carries customer details, service, assigned staff member, date, time, duration, status, and working notes so the visit is more than a colored block.
Name the operating state before the visit reaches checkout
Appointments can move through pending, confirmed, in progress, completed, cancelled, and no-show states. That shared vocabulary helps the desk and the service team understand whether a visit still needs confirmation, is actively underway, or should no longer consume attention.
Protect an active provider's time
The server rejects overlapping time windows for the same assigned staff member when the existing appointment is still active. Cancelled and no-show records release the slot; pending, confirmed, in-progress, and completed records remain part of the overlap decision.
Choose today's appointment or Walk-in before checkout
The checkout flow can begin from today's appointment or a Walk-in choice while keeping booking context visible. Selecting an appointment attempts to move it to In Progress; a successful sale attempts to move it to Completed. The visible booking state is the current handoff; verify any completed-sale appointment reporting needed during rollout.
Keep appointments and workforce scheduling distinct
Appointment allocation answers which client visit is assigned to which provider and time. Workforce scheduling answers when an employee is planned to work; clock and timesheet records capture what was worked. Seeing them together is useful, but one does not silently replace the other.
Use competing visits to prove provider protection
Create a test service and two overlapping visits for the same provider. Confirm the active conflict, then move one record through cancelled and no-show states to verify that those states release the slot. Inspect the weekly calendar, searchable list, notes, customer relationship, and service context. Separately compare the employee schedule so client allocation and planned work hours remain understandable. Include a completed visit in the overlap drill so its behavior is explicit. Record who can edit, cancel, complete, and remove appointments in the rollout procedure.
Inspect in the live demo
Create an appointment, test an employee overlap, move the visit state, and follow its customer context. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.