Setup
First steps
Access
First-Day Checklist
Use this checklist when launching AWRA for a new organization, branch, team, module, or user group.
The first day should prove that users can log in, see the right menus, complete safe test workflows, understand support paths, and avoid accidental changes to live records. Start small, fix setup issues early, and expand once the core workflow feels clear.
For Each User
- User can log in with their own account.
- User has completed profile basics and MFA if required.
- User sees the correct dashboard, role path, branch, warehouse, and menus.
- User knows which pages they should use and which pages they should avoid.
- User knows who to contact for access, workflow, scanner, report, or billing questions.
For Organization Admins
- Company profile, logo, currency, time zone, tax details, and contact details are correct.
- Branches, warehouses, locations, and departments are named clearly.
- Roles are assigned by job function, not convenience.
- Support contacts and escalation paths are known by team leads.
- Billing or plan status is understood by the responsible admin.
- Users who should not be live yet are not invited or are paused.
For Operations Teams
| Team | First-Day Test | What To Confirm |
|---|---|---|
| Inventory | Create or review one test item, then test a check-in, checkout, count, transfer, or adjustment. | Correct warehouse, quantity, unit, category, status, and report effect. |
| Procurement | Create one request and follow it through approval or review. | Approver receives it, status changes make sense, and comments are visible. |
| Sales/POS | Create one quotation, invoice, POS sale, receipt, or return depending on rollout scope. | Customer, tax, payment, receipt, and stock effect look correct. |
| Finance | Review one report, payment, tax view, or sync status if enabled. | Dates, filters, totals, and export behavior are understandable. |
| Warehouse/mobile | Open mobile or scanner flow if used. | Device, login, scan, offline expectation, and sync behavior are understood. |
Stop And Fix Before Going Wider If
- Users cannot log in or do not see required menus.
- Branches, warehouses, item names, vendor names, or customer names are confusing.
- Approvals route to the wrong person or nobody receives the task.
- Stock appears in the wrong warehouse or quantity changes are unclear.
- Finance reports, receipts, invoices, or sync checks do not match expectations.
Launch tip: Keep a shared list of first-day issues with owner, module, record number, urgency, and next action. This makes support and training much faster.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.