An internal control surface for stations, workers, customers, transactions, complaints and offers.

Nine pages

An inventory drawn from the design spec.

• LoginEmail-based sign-in; silent token refresh; access-denied state on stale or missing role.
• OverviewAt-a-glance counters and recent activity; the reference page for localization.
• StationsStation roster; per-station configuration; live status indicators.
• WorkersWorker roster; per-station assignment; credential reset.
• CustomersCustomer search; masked identity surfaces; complaint history.
• TransactionsCursor pagination; server-side filters; URL-encoded filter state.
• ComplaintsTriage queue; internal notes that never appear in customer-facing resolution fields.
• AuditAppend-only audit-event surface with actor, time, action, object, reason, result, reference.
• OffersDraft / publish / archive lifecycle; multilingual; station-scoped.

Roles and permissions

RBAC-aware navigation; minimum necessary disclosure.

Admin, customer service and finance roles each see only their own pages. Silent token refresh; access-denied states on stale or missing permissions. The dashboard never calculates a balance or derives loyalty state client-side — every read goes through the server.

That decision is what lets the same surface serve head office, regional managers and customer-service agents without ever exposing a full customer record by mistake.

Arabic-first rendering

Arabic is primary, English is secondary — honestly disclosed.

Seven protected pages currently ship with hardcoded English headings in the Arabic locale. The fix path is documented work-in-progress, not a hidden flaw; the platform’s accessibility review covers both locales and the issue is named as a follow-up rather than glossed.

Critical workflows

Six daily flows, with reversal as the audit-by-design example.

Customer lookup, transaction search, manual adjustment, reversal, rewards & offers, and audit. Reversal never edits the original transaction — it posts a new opposite ledger entry. Manual adjustments require a reason. The audit-event surface captures actor, time, action, object, reason, result and reference.

• Customer lookupSearch by phone, name or voucher. The dashboard returns only what each role is allowed to see — no full customer record by accident.
• Transaction searchCursor pagination over the ledger. Filters are server-side and URL-encoded so a view is shareable and replayable for the same role.
• Manual adjustmentUsed to correct the human-error case. The adjustment posts as a new ledger entry with a reason and never edits the original.
• ReversalUsed to correct a real error. The reversal posts an opposite ledger entry — never a delete or undo of the original record.
• Rewards & offersOffers are drafted, published and archived in Arabic and English, scoped by station and role. Head office sees what was published, when, and to whom.
• AuditEvery privileged action is captured as an audit-event with reason and reference — the trail a fuel-company compliance team asks for.

Real visual proof

What the page can show today.

Screen gallery will be added in the next review phase.

What this page cannot show

Dashboard is live and used internally; no live screenshots published.

• Production tenant data is not exposed.
• Credentials and tokens are not shown.
• No live manager dashboard screenshots are published with this case study.

Other product studies

Move between the three products.

• Customer app

  21 screens designed in Arabic-first RTL; five are still placeholders.

  Preparing for store release — no store listing yet.

  Read the customer app study

• Worker app

  Android station operations; scanner-led; 14 screens with server-authoritative hand-offs.

  No production-station deployment or POS hardware qualification yet.

  Read the worker app study

← Back to the Glitre Loyalty Platform overview