Follow a shopper across sites.

DOTFLY explains and links the existing journey. Store owns understanding and Little Discovery; YR owns Points and Moments. Their signed handoff code exists. These links open a new tab and do not execute that handoff.

A · Product — EASIS on Sureka Store

  1. DOTFLY butterfly QR

    The existing product QR leads to Sureka Store. Real example: EASIS Soft Bar, SKU 7800718. No new QR or redirect is created here.

    Explained here
  2. Sureka Store understanding + Little Discovery

    A Little Bit / More / Fun and Little Discovery already belong to Store. Open that experience rather than a copy in DOTFLY.

    Opens existing applicationOpen (opens in a new tab)
  3. Signed Discovery Ticket → YR

    Store signs the ticket; YR has receiving, verification and single-use protection code. Implementation exists on both sides. The complete production journey has not been verified here.

    Source code implemented
  4. YR Points & Moments · optional

    YR owns points, Moments and redemption. This link opens YR normally; DOTFLY does not issue a ticket or award anything.

    Opens existing applicationOpen (opens in a new tab)

Status & evidence

  • Sureka Store EASIS page responds (SKU link redirects to the EASIS product page).
  • yourradiant.se homepage responds.
  • No Moment, Fika Moment or Care Moment page on yourradiant.se could be verified — only the homepage is linked.
  • Store: answer checking and signed Discovery Ticket issuance are implemented in source code.
  • YR: ticket verification, single-use protection and points-credit handling are implemented in source code.
  • Production receipt, actual points credit and Moment redemption have not been verified end to end here.
  • DOTFLY’s independent API is not connected; these navigation links send no ticket, answers or identity.
  • No QR codes for Moments exist in DOTFLY.

Links checked 28 Oct 2026.

What still needs verification

  • Verify the existing Store → YR production journey with approval: ticket receipt, one-time handling, points credit and redemption.
  • Confirm actual deployment and configuration separately from the source-code evidence; do not assume absent code.
  • If this independent hub is connected later, agree read-only access and consent boundaries first. No new reward system is needed.
  • Confirm Moment-specific destinations before adding deep links. No credentials, publishing or external changes are part of this showcase.