# A Store Has to Explain Itself Before Checkout

_Published 2026-09-07._

A catalogue answers “what can I buy?” It does not necessarily answer “why does this exist, and is this the right place to start?”

Happy U was a wellness brand with journals and curated boxes. The store had to sell products, but the first screen needed to explain the practice before it asked for a transaction.

## Story before SKU

The visitor can arrive from paid traffic, read the brand story, explore the Allyship path, and only then reach the catalogue. The store and the story are not separate websites. They are stages of one decision.

Locale is part of the same system. Arabic is content, URL, and direction. RTL is not a late CSS mirror applied after the English layout is done.

## Checkout is a boundary

Telr owns the payment interaction in AED. The application must keep the order state honest when a payment is declined, delayed, or held. “The button returned” is not the same thing as “the order is paid.”

The policy set is part of the launch: terms, privacy, cookies, delivery, refund, return, and cancellation information have to be present when the merchant is reviewed.

The [Happy U case study](/work/happy-u) also shows the less visible handoff. GCLID and related identifiers are captured at arrival and carried into WhatsApp so a later conversation does not become an untraceable second funnel.

The store is not just where the payment happens. It is where the brand explains what the payment means.