VariPOS Documentation
Read module-by-module like an operations story. Every scene tells what to do, what to check, and what outcome to expect.
Support
Troubleshooting, Known Patterns, and FAQ
When issues happen during busy hours, this chapter gives practical recovery steps.
Scene 1: Troubleshooting, Known Patterns, and FAQ – Scene 1
Rapid diagnosis playbook for common errors in production usage.
Step 1
Verify signing config, package ID, and correct google-services.json file.
Step 2
Rebuild release artifact after Firebase SHA updates.
Step 3
For device-specific install failures, retest with clean install and fresh build.
Scene 2: Troubleshooting, Known Patterns, and FAQ – Scene 2
Rapid diagnosis playbook for common errors in production usage.
Step 1
Check date/FY filters first across all report surfaces.
Step 2
Verify void/cancelled entries are treated as expected in the report context.
Step 3
Reconcile source records from list screens before escalation.
Scene 3: Troubleshooting, Known Patterns, and FAQ – Scene 3
Rapid diagnosis playbook for common errors in production usage.
Step 1
Validate correction date policy and FY open/closed state.
Step 2
Check compliance status flags and filing metadata.
Step 3
Use audit entries to track blocked or adjusted operations.