Find and review customers
Customers supports branch-scoped search and detail review for customer identity, contact, Khata, loyalty, and order use. Open Customers, search using the available customer fields, and open the correct customer. Collect only necessary customer data and verify consent, identity, credit, and loyalty context before saving or charging.
Before you start
- An authenticated POS session assigned to the intended branch.
- The correct customer record or minimum details needed to create one are available.
Steps
- Open Customers.
- Search using the available customer fields.
- Open the correct customer.
- Review the record before linking it to an order.
Expected result
Search returns the intended branch-accessible customer without exposing unrelated customer records. Do not create a duplicate customer or repeat a balance-changing action while the first result is uncertain.
Permissions
- Customer access follows the assigned customer capability; Khata, loyalty, consent, and editing controls require their corresponding permission and branch context.
Troubleshooting
When staff open Customers, POS blocks progress before they can search using the available customer fields.
A safe retry starts by confirming: An authenticated POS session assigned to the intended branch. The correct customer record or minimum details needed to create one are available. Reopen /customers once and read the exact validation or configuration message. If the control remains unavailable, stop and give Support the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Capture the displayed state produced when staff open Customers.
The profile, consent, Khata, loyalty, or linked-order state does not match one customer after the final checkpoint: Review the record before linking it to an order.
Compare the selected profile, contact identifier, consent, Khata balance, loyalty state, and linked order. Search for the customer again before retrying; do not create a duplicate profile or repeat an unresolved balance action. Do not repeat the action if the records conflict; ask Support to review the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Check the saved state after staff review the record before linking it to an order.
Related articles
Customer forms validate name, phone, email, country, city, consent, and minor or guardian requirements before saving.Record customer consent and guardian confirmation
Customer data collection requires the relevant privacy consent, and records for minors require guardian confirmation before save.Review customer Khata and loyalty context
Customer context helps staff confirm credit status, outstanding balance, available loyalty points, and eligibility before checkout.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback