Stage 1 · Framework

Every message HomeKode sends, in one place.

Thirty post-action templates across the order journey and the returns lifecycle — each one written for email and WhatsApp, each one carrying the root cause back to the customer in plain language. 🕊️

Templates authored3017 order journey · 13 returns & refunds
Root-cause reasons52Shown to the customer, never hidden
Channels per trigger2Email ✉️ Email and
How a message gets sent
  • 👩‍💼 An agent takes an action in Shopify — that is the only trigger.
  • 🔔 Shopify fires a webhook to a Cloudflare Worker (HMAC-verified).
  • 🧩 The Worker pulls order and customer data from Shopify, logistics from Dobesell, ticket context from Freshdesk.
  • 📝 The matching template is filled, in the customer's language and tone.
  • 📤 It goes out on both channels, and every send is written to an audit log.
Build roadmap
  • ✅ Module 1 — Framework, template library, Preview Studio (this page)
  • ⏳ Module 2 — Cloudflare Pages + Supabase deploy, sign-in, roles
  • ⏳ Module 3 — Shopify custom app, webhooks, HMAC verification
  • ⏳ Module 4 — Email sending: ESP + SPF, DKIM, DMARC on homekode.com
  • ⏳ Module 5 — Live Website Updates poller (cron + diff engine)
  • ⏳ Module 6 — WhatsApp Business Platform + Meta template submission
Credentials are only ever requested at the module that needs them. Nothing here holds a key. 🔐
Stage 4 · Preview

Preview Studio

Pick the source, the template and the channel — then see exactly what lands on the customer's phone or in their inbox, before a single message goes out. 👀

Where each property comes from
Sample record
order#57668 · 17 May 2026
customerNadine Finge
itemGraciell Warm Terracotta Bench
total1,450.00 AED
marketDubai, UAE 🇦🇪
Stage 2 · Part one

Order journey

Seventeen moments between checkout and the doorstep. The ones that carry bad news carry a reason with them — a customer who knows why is a customer who waits. 🧭

Stage 2 · Part two

Returns, refunds & replacements

Thirteen stages from "I'd like to return this" to money back in the account — every message naming the piece and the reason it's going back. 🔄

Reason codes accepted on a request
Stage 1 · Reading A — store feed

Live website updates

What changed on homekode.com — new arrivals, price moves, stock swings, collection updates — polled and refreshed without you asking. 📡

 Change feed
refresh in 20s
How the feed is wired
  • ⏱️ A Cloudflare Worker cron polls homekode.com/products.json and the collection endpoints.
  • 🗃️ Each poll is snapshotted to Supabase.
  • 🔍 The next poll is diffed against the last one, so the feed shows change events, not a product list.
  • 🏷️ Events detected: new arrival, price drop, price increase, back in stock, sold out, collection updated.
  • 🔄 The page re-renders on its own — no manual refresh.
Verified 23 Aug 2026: the endpoint returns live product JSON with title, handle, updated_at, images and variants carrying price, compare_at_price, available — everything the diff engine needs. The feed below is sample data until Module 5 goes live. ✅
Stage 1 · Integrations

Data sources

Three systems, one message. Every property on every template resolves back to exactly one of them — no guessing, no duplicated truth. 🔌

🛍️ Shopify

System of record and the only trigger. Orders, customers, payments, fulfilment status, totals and VAT, addresses.

Needed at Module 3
Custom app · Admin API token · webhooks: orders/create, orders/updated, orders/cancelled, fulfilments, refunds
🚚 Dobesell

The back-office command centre. AWB and courier telemetry, timestamps, delivery attempts, fulfilment-model routing, invoices, FC receipt.

Needed at Module 3
API base URL · auth method · endpoint docs for AWB, timestamps, fulfilment model, invoices
🎧 Freshdesk

Customer conversation context. Ticket ID and status, reason code captured by the agent, agent notes, CSAT hooks.

Needed at Module 3
API key · domain · ticket field IDs for reason code
Full property map
Stage 3 · Integrations

API connections

One slot for every credential, waiting for IT. Paste it, save it, test it — the app tells you straight away whether it works. 🔑

⚠️ This page is the preview, not the vault

Nothing typed here is stored, sent, or remembered — this preview has nowhere to put it. Paste real credentials only into the deployed app, where each one is encrypted with AES-256-GCM before it touches the database and can never be read back out. Try the flow here with anything you like. 🧪

Slots waiting17Filled as IT hands each one over
Needed next10Module 3 · Shopify, Dobesell, Freshdesk
Readable back0Write-only by design 🔒
Stage 1 · Non-negotiables

Security & delivery

This app will send real messages to real customers. That's a responsibility, so the guardrails come before the features. 🔐

Security posture
  • 🗝️ No key ever reaches the browser. All secrets live in Cloudflare Worker environment bindings.
  • ✍️ Every Shopify webhook is HMAC-verified before it's trusted.
  • 🔁 Sends are idempotent — one action, one message, even if a webhook is delivered twice.
  • 👤 Sign-in required, with roles: Owner (you), Editor, Viewer.
  • 🧾 An audit log of every message: who, what, when, to whom, on which channel, and the result.
  • 🛑 A global kill switch that stops all outbound sending in one click.
  • 🧪 A dry-run mode that renders and logs a send without dispatching it.
  • 🙈 Customer data is rendered, never stored beyond what the audit log needs.
Deliverability & compliance
  • 📧 SPF, DKIM and DMARC on homekode.com — without these, mail goes to spam.
  • 💬 WhatsApp templates must be pre-approved by Meta; free-form text outside a 24-hour customer-initiated window is not permitted.
  • 🌍 Written for a multi-national Middle East audience: plain English, no idioms, no slang, AED, UAE address format.
  • ⏰ Send windows respect customer care hours, 9am–9pm, seven days a week.
  • 🔕 A customer who opts out of WhatsApp still receives email.
Outstanding items are credential handovers, not decisions. Each is requested only at its own module. Nothing is blocked today. ✅