Using the Dashboard
The dashboard is the landing page after sign-in. It is your command center for the state of the integration across all Pedro's Chicken stores.
Getting there
After signing in you are redirected to /pckzra/dashboard. You can return at any time from the portal navigation.
What the dashboard shows
The dashboard aggregates the live state of the middleware:
| Area | What it tells you |
|---|---|
| Store summary | Total, active and inactive store counts. A store must be active to submit invoices. |
| Transaction statistics | Total, successful and failed API transactions, with a success rate. Filterable by store and date range. |
| Volume by store | Transaction counts per store — the quickest way to spot a store that has gone quiet or is erroring. |
| Recent failures | Failed transactions (default: last 7 days) with links into the full request/response detail. |
Navigation
| Portal page | URL | Purpose |
|---|---|---|
| Dashboard | /pckzra/dashboard | Overview statistics and health snapshot |
| Stores | /pckzra/stores | List, search, add, edit, activate/deactivate stores — see Managing stores |
| Reports | /pckzra/reports | Transaction and conversion reports — see Reports |
| Logout | /pckzra/logout | End your session |
Daily operating routine
A recommended daily check for operations staff:
- Check the success rate. A healthy system is near 100%. A sudden drop means a systemic problem (Chrilan outage, network, or a configuration change).
- Scan volume by store. A store showing zero transactions during trading hours usually means a local POS/network issue, not a middleware issue.
- Open the failed transactions list. Each failure keeps the full request and response — most issues can be diagnosed without server access. See Troubleshooting for the error catalog.
- Confirm menu sync is running for stores that recently changed their menu — see Menu sync setup.
Tip
Every transaction carries a transaction ID (UUID) that flows through the entire request lifecycle. When a store reports a failed sale, ask for the approximate time and store name, find the transaction in Reports, and you will see the exact payload the POS sent and the exact error returned.
Related guides
- Managing stores — register and configure stores
- Reports & transaction history — deep dive into the reporting screens
- Monitoring & health checks — machine-level monitoring beyond the portal