View and edit a customer
Current source defines the customer detail as an authenticated profile and related-data surface. It is separate from the contact snapshot stored on an individual order. This guide records fixed-source behavior only; it does not authorize opening or changing a live customer. For the distinct order surface, see Edit customer contact information.
Do not open a production record, copy personal data, enter a password or verification code, upload an image, inspect wallets or metadata, or use Update, Enable, Delete, Add, or event controls. GET and HEAD are not presumed safe, and an error is not proof that no effect occurred.
Reachability and detail reads
The Customers route and Users sidebar require level-0 administrator access, while the API separately authorizes each read and mutation. Selecting a row can reuse fields already returned by the list; opening a direct-ID detail or missing row triggers an authenticated user read. The detail can expose profile, verification, addresses, wallets, metadata, order relationships, push tokens, and other private fields.
Opening Custom fields, wallet, address, or order panels can cause additional authenticated reads. No list, customer, tab, field, or relationship was opened for this documentation.
Source-defined profile fields and validation
The profile form uses checkout-field configuration for visibility and required state. Current client source can expose names, contact data, timezone, phone and country code, password, profile image, and a shared user-type selector. Current API source validates only submitted fields and separately applies caller, record, and role restrictions.
Fixed API source includes these boundaries:
- names use the configured text rule; email and cellphone have uniqueness checks;
- password must contain at least eight characters;
- a changed cellphone needs a country calling code and can require provider-backed verification;
- changing verified cellphone or email data can clear its verified state;
- only an administrator can persist a role change, and a user cannot change its own level;
- a protected user cannot be disabled or unprotected.
These are source contracts, not proof of deployed validation or accepted data.
Persistent, session, upload, and outbound effects
The Update action submits accumulated form changes. Image changes can invoke an upload boundary before the user record is updated. Phone verification can call an external verification provider when configured. Plugin filters/actions and user-history recording can also run around a successful source path.
Current API source can migrate the account's session strategy, preserve or create a record for the current token, revoke other stored sessions, and write a session-revocation log when a password is changed. No credential, token, password, or session was inspected or changed.
The detail enabled switch submits immediately, outside the profile Update button. Confirmed Delete mutates identifiers, deletes the user, writes an audit log, and can invoke plugin actions. Custom fields reads metadata on open and exposes metadata create/delete requests. Optional wallet panels can read balances/events and expose value-changing event requests.
A customer-profile update does not establish that contact data already stored on an order changed. No propagation or reconciliation between those records was verified.
Privacy classification
Names, birth dates, addresses, locations, emails, phones, passwords, verification state or codes, images, metadata, wallet values/events, order relationships, push tokens, role, and session information are personal, financial-adjacent, credential, or secret-adjacent data. Do not reproduce any live value or implementation secret in documentation.
What remains unverified
Without immutable serving receipts and an approved synthetic PII-free identity with uploads, verification providers, sessions, wallets, metadata, orders, plugins, and all writes intercepted, this page does not claim deployed field availability, successful validation/update, session revocation, provider verification, upload completion, deletion, wallet effect, or safe retry.