Record customer consent and guardian confirmation
Customer data collection requires the relevant privacy consent, and records for minors require guardian confirmation before save. Explain why the requested customer data is needed, record the applicable consent choice, and for a minor, obtain and record guardian confirmation. 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
- Explain why the requested customer data is needed.
- Record the applicable consent choice.
- For a minor, obtain and record guardian confirmation.
- Save only when validation passes.
Expected result
The applicable consent choice and guardian or minor handling remain recorded with the customer context. 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
Staff cannot explain why the requested customer data is needed because the control is missing, disabled, or rejected before they record the applicable consent choice.
First confirm the following access and record state: An authenticated POS session assigned to the intended branch. The correct customer record or minimum details needed to create one are available. Check those conditions on /customers and repeat only the blocked step once. Preserve the screen and ask Support to review the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Keep evidence of the result when staff explain why the requested customer data is needed.
The profile, consent, Khata, loyalty, or linked-order state does not match one customer after the final checkpoint: Save only when validation passes.
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. If those records still disagree, stop and send Support the safe customer reference, branch, affected field/balance, status, and time; remove unnecessary customer data. Before another attempt, establish whether staff could save only when validation passes.
Related articles
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.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