Personalization should use declared customer context
Useful personalization starts with information the customer has provided or allowed the business to remember, such as stated preferences, viewed products, wishlist choices, or prior conversation context where the installation permits it. It should not infer sensitive traits or invent a preference that the available data does not support.
Make consent, purpose, and control visible
The merchant is responsible for configuring an appropriate consent path and visitor-facing disclosure for its business and jurisdiction. Customers should be able to understand what is remembered and which experience it affects. Do not claim universal legal compliance without a review of the actual implementation.
Keep personalized answers tied to approved facts
A remembered preference can narrow a recommendation, but price, stock, compatibility, fit, ingredients, delivery eligibility, and policy conditions still need current store data. Ask a clarifying question when the preference or catalog record is incomplete.
Measure relevance without assuming an uplift
Track preference opt-in, recommendation engagement, corrections, unresolved requests, and operator handoffs against the previous workflow. The business effect depends on audience, catalog, traffic, consent design, and merchandising quality.
