Set the shop case
Record store, lane, device, operator, catalogue and market assumptions.
Workflow blueprint
A merchant POS system needs a tender and close story, not only a product list
A page-specific review aid, not a universal product or compliance claim.
Keep the store scenario, operator action, terminal response, receipt, return and reconciliation question in a dated card.
TL;DR — Keep the store scenario, operator action, terminal response, receipt, return and reconciliation question in a dated card.
Exercise the tender
Capture success, timeout, retry, duplicate, receipt and customer message.
Test the return
Keep return, reversal, stock question and approval distinct.
Review the close
Assign tax, payment, security, export, support and reconciliation owners.
Page-specific decision aid
Merchant lane tender card
A shop, terminal, operator, item edition, response code, receipt, return, close batch, support case and open question.
- ✓Payment response is not settlement
- ✓Returns keep their reason
- ✓Provider claims stay dated
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.
- ✓Store and terminal identity
- ✓Item and operator source
- ✓Tender and return evidence
- ✓Close and local owner
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