POS Document Flow
POS session Open/Close and transaction Pending, Completed, Voided, Refunded lifecycles.
POS Document Flow
Point of Sale uses session and transaction statuses. Row Actions are primarily icon buttons and dialogs, not a full MudMenu Submit/Approve pattern.
Hub: Target Document Flow. Overview: Point of Sale.
Sessions
#Statuses
Open, Closed
| UI control | Behavior |
|---|---|
| Open Session | Opens register session dialog |
| Close Session | Closes open session |
| X-Report / Open Register / Refresh | Session operations |
Transactions
#Statuses
Pending, Completed, Voided, Refunded
Transaction lifecycle — sale, void, refund
flowchart TB Start((Sale)) --> Pending[Pending] Pending -->|Complete sale| Completed[Completed] Completed -->|Void| Voided[Voided] Completed -->|Refund| Refunded[Refunded] class Start egkStart class Pending egkDraft class Completed egkSuccess class Voided,Refunded egkTerminal
| UI control | Gate |
|---|---|
| View detail | Always |
| Void | When CanVoid(row) |
| Print receipt | When printable |
Actions menu: Not implemented as a MudMenuItem list on the transactions grid — void/print use inline icon buttons and dialogs.
#Post-action sync
After void/close/open, lists refresh. Failed void leaves prior status (Completed).