Skip to main content
WorkServicesAboutCareers

Dreaming as a Service.

© 2026 USERHOOD. ALL_RIGHTS_RESERVED.
Navigation
HomeWorkServicesAboutCareers
Contact
hello@userhood.inWhatsAppLinkedInInstagram
Legal
PrivacyTerms
Back to selected work

An entire commerce engine. Unmistakably Tirch.

TIRCH

A fashion label’s personality shouldn’t end at the campaign. Tirch carries it through the shop, the bag and the account, with a complete commerce system behind the experience.

Visit tirch.in
Tirch's live storefront hero for the Ghungroo Break tee
Tirch shop catalogue showing three product worlds and collection hierarchy
Live product // Storefront + commerce engine
Surface
Brand storefront + customer account
Delivery
Product, brand, design, engineering
Platform
Cloudflare Workers + D1
Engine
Catalogue → quote → account → order

How could the whole shopping experience feel as considered as the clothes?

Screens show the captured product and its commerce flows. Payment and launch readiness are noted separately; no unverified sales or conversion results are claimed.

The brand has a place to live, and a system to run on.

Campaigns, collections and product pages connect to a bag, checkout quotes, customer accounts and order handling. The experience has its own character, with the necessary commerce rules behind it.

10
products in the catalogue

Captured product snapshot

3
collections

After Hours, Meme Fest, and Pujo ’26

0
passwords in the customer flow

OTP-based account identity

1
authoritative source of price

Server-rebuilt checkout quote

Every step of shopping has to belong together.

The product page, bag, checkout and account each have a job. Here is how they connect, and where the system checks the details.

01 // Merchandising
System signal
10 products

One catalogue

Collections have their own character, while products, links and shop rules stay connected.

3 collectionsCaptured product snapshot
02 // Customer selection
System signal
M · 01

A bag that remembers

Keep the chosen product, size and quantity together. Check the current price again when the shopper proceeds.

Size + quantityDisplay state only
03 // Commerce authority
System signal
₹2,499

A checked total

The server checks each product and calculates the total using the current catalogue and order rules.

Catalogue repricedOrder rules applied
04 // Private lifecycle
System signal
OTP → order

A personal account

A code-based sign-in connects a customer to their addresses, order history and updates without another password to remember.

Private account stateServer-led lifecycle
What the shopper chooses
  • Selected product
  • Chosen size
  • Quantity
  • Display-price snapshot
What the server checks
  • Whether a product is live
  • Authoritative price
  • Promotions and delivery rules
  • Order and payment state
CatalogueLive
Customer accountsReady
Checkout quotingServer-led
Production paymentsGated

What needed a closer look.

A shopper moves from an image to a product, a size, a price and an order. Tirch needed that journey to feel like one brand, with reliable information at every step.

Give the brand room to express itself without compromising pricing, customer privacy or the accuracy of an order.

The choices behind the product.

What needed attention, how the product handles it, and why that matters to the person using it.

  1. Make the price trustworthy.

    The problem
    A price saved in the browser can be out of date or changed.
    The choice
    Check each item and calculate the total again on the server before checkout.
    Why it matters
    The quote reflects the current product and pricing rules.
    Tirch product page with price, material, fit, size choice, and delivery promises
    Tirch shopping bag showing selected product, size, quantity, subtotal, and checkout handoff
    Live product // Product to bag

  2. Keep shopping open and personal details private.

    The problem
    Fast public shopping and private customer data have incompatible cache and security needs.
    The choice
    Prerender merchandising; keep OTP sessions, profiles, addresses, and orders server-led.
    Why it matters
    The storefront stays fast without treating private account state as public content.
    Tirch passwordless account sign-in separating public shopping from private customer state
    Live product // Private account boundary

  3. Give each collection character without losing the brand.

    The problem
    Different campaigns can make a shop feel like several unrelated brands.
    The choice
    Give collections their own expression within shared naming, navigation and product rules.
    Why it matters
    The ranges can feel different while still belonging to Tirch.

  4. Only promise what is ready.

    The problem
    A visually finished storefront can imply stock, payment, and fulfilment readiness that does not exist.
    The choice
    Keep concept pieces separate, leave missing facts missing, verify webhook paths, and gate payment.
    Why it matters
    The engine fails closed until every public promise can be kept.

What went into it.

  • Brand and responsive storefront system
  • Catalogue, collections, product detail, bag, and merchandising rules
  • Server-authoritative checkout quoting
  • OTP identity, sessions, profiles, addresses, and order history
  • Order lifecycle, payment-webhook boundary, and transactional email
  • Cloudflare Worker, D1, analytics, and image pipeline
  • Accessibility, metadata, performance, and regression guardrails

The live product and implementation support these product and engineering claims. They do not establish commercial launch, enabled payment, revenue, conversion improvement, or tracked inventory because those states are intentionally gated or not yet evidenced.

Give us something to think about.

The product you want to exist. The problem you can’t leave alone. Start there.