One dashboard over every store, and the messages that bring customers back.
Hifn's merchants ran on different engines — Shopify, Wix, custom builds — and had no single view of them, and no reliable way to re-engage customers after checkout. As their in-house fullstack developer I built two things: a unified commerce dashboard across those engines, and a distributed WhatsApp retention system that ran on its own, in the background, at scale.
The problem
Every store engine has its own API, its own data shape, and its own idea of what an order is. Stitching three of them into one dashboard means normalising all of that without slowing down as catalogues grow. The retention side was harder: WhatsApp campaigns need to fire on schedule for thousands of customers, survive rate limits and failures, and never double-send — which is a distributed-systems problem dressed up as a marketing feature.
What I built
How it works
Results
Running it
I left Hifn in January 2024 and their team took both systems on. It was the first place I built the queue-backed, retry-safe shape I now reach for by default — the same pattern that later became Doota's inbound path on Cloudflare. It is on this list as background rather than client work: I was on staff, and Hifn owns the code.
Related
I take on a small number of projects at a time.
Tell me what you're building and where it hurts. I'll say honestly whether I'm the right person for it.