Keep the customer relationship connected to the sale.

Search · profile

Find the person, then read the record behind the name.

Searchable customer records can be created, opened, and updated with contact, address, marketing-consent, tier, wallet, first-visit, and last-visit context. The profile keeps those fields beside the sale relationship instead of scattering them across register notes.

Customer statistics provide rolling relationship context for an authorized operator. The merchant remains responsible for what it collects, why it collects it, and which roles can use it.

History · statistics · wallet

Move from the profile into what happened at the register.

Purchase history keeps completed transaction context available from the customer record. Visit and purchase statistics help staff understand the relationship, while permission-gated wallet transaction history exposes the value movements an authorized operator needs to review.

History does not replace the original transaction. Use checkout and transaction control to inspect the sale, tender, receipt, and qualified return path, and use reporting for broader customer comparisons.

Merge · lifecycle

Resolve duplicate identity without inventing a second relationship.

An authorized duplicate merge joins customer identity with an audit record of the action. Archive removes a customer from the active working set without deleting the relationship history; restore returns that same record to active use.

Export · anonymize

Separate portability from irreversible privacy action.

Permission-gated export packages the selected customer's profile and purchase history for authorized use. Anonymization is a different, irreversible permission-gated action: it removes identifying profile data while retaining sales records needed for the operating history.

The two controls are intentionally distinct. An operator should confirm the customer, the requested action, and the assigned permission before proceeding.

Support-assisted migration

Move customer data through a support-assisted import path.

Customer import is support-assisted rather than a merchant-run upload. LiftedPOS support can review the source structure, field mapping, consent context, duplicate strategy, and import result with the merchant before the migrated records become operating data.

For a real migration, bring a representative export and the rules that define identity, consent, tiers, and existing balances to the implementation conversation.