Blessed Collections
A storefront that takes mobile money and reports where the sale came from — instrumented at build time, not bolted on.
A retail client needed a real storefront rather than a generic template — one that could take mobile money natively and, unlike most stores launched in this market, could actually say which channel produced a given sale.
- 01
A Next.js storefront (Blessed Collections) backed by a multi-tenant ecommerce schema: shops, categories, products, guest checkout, orders and payments.
- 02
A Redis-based cart rather than a database table, and guest-only checkout with a tracking number for order lookup — no forced account creation to buy something.
- 03
M-Pesa accepted through two separate channels — paybill and till — kept as distinct payment paths rather than merged into one, since the underlying flows genuinely differ.
- 04
Google Tag Manager, GA4, Meta Pixel and TikTok Pixel wired in at build time, so every session and sale is attributable from launch day rather than retrofitted later.
Real interfaces, not mockups.
Measurement as a build requirement, not an add-on
Most storefronts in this market ship first and get instrumented later, if at all — by which point months of channel data are simply gone. Here, the tracking layer was part of the initial schema and checkout flow: every purchase event fires to four destinations at the moment it happens, so channel attribution exists from the store's first sale rather than starting whenever someone remembers to add it.
analytics channels wired in at launch
M-Pesa channels behind one checkout
Something similar to build?
Tell us what you run today and where the manual work sits.