Bring the customer relationship into the store.

Define how a customer chooses to identify themselves or join the relationship. Depending on the implementation, the journey may use a programme identifier, QR code, web form, mobile touchpoint or a supported store registration process.

Make the purpose and benefit understandable. Asking for more information is not an experience improvement unless the customer receives something useful and the collection is appropriate.

Customer 360 can connect the agreed identity and information. The method must distinguish a known customer from an anonymous store visitor.

A staff member may need to check a benefit, help with a programme question or understand a relevant customer request. Provide the information required for that task without exposing an unrestricted customer history.

Where a store portal forms part of the solution, define its users, permitted actions and relationship to the POS or other operational systems. A convenient interface should not bypass transaction rules or create competing records.

The store workflow needs to work during busy periods and handle missing information clearly. Test it with the people who will use it, not only in an office demonstration.

Customer Engagement supports relevant communications, while Loyalty Program supports the agreed benefit and redemption rules. Their usefulness in the store depends on the connected systems and the customer journey.

Clarify where an offer is valid, how eligibility is checked and how a redemption is confirmed. A displayed coupon is not proof that the POS will accept it. Exceptions need a clear owner and customer explanation.

A programme can encourage repeat visits, but the proposition should remain understandable. Complexity that makes redemption difficult can undermine the intended experience.

The existing in-store approach includes QR codes, triggered campaigns, kiosks, store portals and mobile experiences. Select the elements that solve the actual problem; they are not all mandatory parts of every project.

Location-based experiences require suitable technical signals and permissions. They should not be presented as invisible identification of everyone entering a store.

A useful first implementation could be a QR-led registration journey linked to the customer programme, with a tested store process for the next action. Any hardware, app or POS integration is scoped explicitly.

After the appropriate event is recorded, a configured journey can support relevant follow-up. That might be useful programme information, a request for feedback or a later engagement initiative based on the customer's activity.

Keep the message consistent with the in-store promise and the customer's communication preferences. An AI agent can support selected preparation or execution tasks where approved, but it must use the actual programme and campaign rules.

Look at registration completion, successful use of benefits, repeat visits where identifiable, support requests and customer feedback. Distinguish measured transactions from proxies such as code scans or message clicks.

The review should identify where the process adds value and where it creates friction. Customer feedback and store-team experience can help improve the journey alongside the available behavioural data.

Pobuca's everest case describes work on a loyalty scheme and an omnichannel member experience. Its challenges include bringing physical-store and online-order data together, creating a unified customer profile and using behaviour to define relevant customer groups.

Read the customer story

Book a discovery meeting