Frame the case
Register terminal, session and operator.
Workflow blueprint
Touch Screen POS System Mauritius should keep its screen session visible
A page-specific review aid, not a universal product or compliance claim.
Use the touch checkout exception card to keep screen session, item, operator, tender response, correction, receipt and close connected for a Mauritius evidence review.
TL;DR - Use the touch checkout exception card to keep screen session, item, operator, tender response, correction, receipt and close connected for a Mauritius evidence review.
Trace the evidence
Trace item, modifier and tender.
Review the exception
Keep mis-tap, void and receipt retry.
Assign the next owner
Assign payment, accessibility and tax owners.
Page-specific decision aid
Touch checkout exception card
A screen session, item, operator, tender response, correction, receipt and close, source edition, timestamp, exception note and named review owner.
- ✓A tap is not a sale
- ✓A void keeps its reason
- ✓Receipt retry is not settlement
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Session and operator
- ✓Item and tender
- ✓Void and receipt
- ✓POS reviewer
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow