bisco/azionelab
1
0
Fork 0
generated from bisco/codex-bootstrap
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(operations): improve reservation and check-in flows

Browse Source
This commit is contained in:
bisco
2026-04-29 19:23:42 +02:00
parent 6c5b5d99bc
commit 5cad1871e7
10 changed files with 627 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/booking-flow.md
View File

@@ -101,6 +101,19 @@ The QR code must not contain:
The token remains opaque throughout the flow. The QR code must not expose visitor name, email address, phone number, notes, or other personal data.
## Manual Reservations In Admin
Staff can also create a reservation manually from Django admin for a specific performance.
This operational flow should still follow the same backend rules as the public booking flow:
1. staff selects the performance and enters guest contact details and party size;
2. the backend validates booking availability and capacity;
3. the backend creates a `pending` reservation;
4. the backend creates the normal confirmation token;
5. the backend sends the standard confirmation email;
6. the guest still confirms through the email link before the reservation becomes confirmed and usable for check-in.
## Duplicate Check-In
If the same QR code is scanned again: