POSCustomers

Review customer Khata and loyalty context

Customer context helps staff confirm credit status, outstanding balance, available loyalty points, and eligibility before checkout. Find the customer, review Khata status and outstanding balance, and review loyalty points when enabled. 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

Find the customer.
Review Khata status and outstanding balance.
Review loyalty points when enabled.
Link the record to the order and follow checkout eligibility messages.

Expected result

The customer view shows current Khata and loyalty values that reconcile with linked posted transactions. 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

The workflow stops while staff find the customer, before they can review Khata status and outstanding balance.

Verify these conditions before another test: An authenticated POS session assigned to the intended branch. The correct customer record or minimum details needed to create one are available. Return to /customers without changing user, branch, or record. Try the blocked step once; if it remains unavailable, stop and provide Support the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Record the visible response when staff find the customer.

The profile, consent, Khata, loyalty, or linked-order state does not match one customer after the final checkpoint: Link the record to the order and follow checkout eligibility messages.

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. When no single result can be proved, pause and provide Support the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Confirm from the records whether staff could link the record to the order and follow checkout eligibility messages.

Find and review customers
Customers supports branch-scoped search and detail review for customer identity, contact, Khata, loyalty, and order use.Create or edit a customer
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.