Frame the case
Register store, terminal and item edition.
Workflow blueprint
Point of Sale Systems Mauritius should keep its item visible
A page-specific review aid, not a universal product or compliance claim.
Use the sale-to-close evidence card to keep item, price, terminal, tender response, void, return, receipt and close connected for a Mauritius evidence review.
TL;DR — Use the sale-to-close evidence card to keep item, price, terminal, tender response, void, return, receipt and close connected for a Mauritius evidence review.
Trace the evidence
Trace tender, retry, decline and receipt.
Review the exception
Keep void, return and close evidence separate.
Assign the next owner
Assign payment, tax, inventory and reconciliation owners.
Page-specific decision aid
Sale-to-close evidence card
A item, price, terminal, tender response, void, return, receipt and close, source edition, timestamp, exception note and named review owner.
- ✓Authorisation is not settlement
- ✓A receipt is not inventory proof
- ✓A retry keeps its identity
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.
- ✓Terminal and item source
- ✓Tender and retry history
- ✓Void and return reason
- ✓Close 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