Case study

Naskia Handmade: E-commerce Platform

A custom e-commerce platform for a Nairobi artisan store: server-rendered storefront, AJAX cart and checkout, M-PESA and card payments, CMS-managed blog and local-SEO groundwork.

Client
Naskia Handmade
Industry
Retail · E-commerce
Screenshot of the Naskia Handmade: E-commerce Platform website

The live website, Naskia Handmade: open it here.

The challenge

Naskia Handmade sells African handmade products, ceramics, baskets, skincare, toys, from a physical store in Nairobi. The business needed to sell the same catalogue online without losing the storytelling that makes the brand work, and without taking on heavyweight platforms whose monthly costs and plugin sprawl would outweigh their benefit for a small catalogue.

The hard requirements were practical: Kenyan shoppers must be able to pay the way they actually pay (M-PESA first, cards second); product photography and stories had to stay central; and the owner had to manage products and articles herself, in plain language, without touching code.

Our approach

We chose a deliberately lean architecture: a custom PHP application with MySQL, server-rendered on every page so search engines and slow mobile connections both get complete HTML on the first response. No page builder, no JavaScript framework for rendering, interactivity lives only where it earns its place: the AJAX cart, live search and forms.

The CMS side was built around the owner's actual workflow: product records with specifications and photography, a blog with a safe structured editor, and category pages written to serve real search intent rather than filler.

Implementation

The storefront renders categories, products and articles server-side with clean URLs and per-page metadata. The cart is a lightweight client-side module with an AJAX checkout that creates the order server-side, then hands over to payment: M-PESA for most shoppers, card through a payment gateway for the rest. An IPN-style callback confirms payment status so orders reconcile automatically.

Product data, blog content, orders and media are managed through a custom admin with role checks, CSRF protection and validated uploads. The whole platform ships with sitemap, structured data and caching rules configured for shared hosting.

Technology and integrations

  • PHP (server-rendered MVC-style structure) and MySQL with PDO prepared statements
  • Vanilla JavaScript and AJAX for cart, search and forms
  • M-PESA and card payment integration with IPN reconciliation
  • Custom CMS: products, categories, blog, media library
  • SEO foundation: sitemap.xml, robots rules, structured data, clean URLs

Outcome

The store went live with the full catalogue under the owner's day-to-day control: she adds products, publishes articles and reviews orders without developer involvement. Payments reconcile through automated confirmation, and the platform runs comfortably on ordinary shared hosting, the running cost stays close to hosting plus SMS/payment transaction fees.

Lessons learnt

  • Server-rendering was the right default. Complete HTML on first response kept the site fast on mid-range phones and made SEO work straightforward: no framework needed to "solve" crawlability.
  • Payment is a workflow, not a button. The important engineering lived in reconciliation and failure states, not the checkout screen.
  • Editor training is part of the build. The CMS succeeds because content roles were designed around one non-technical owner, not a hypothetical marketing team.
  • Lean beats heavy for small catalogues. A focused custom platform costs less to run monthly than the plugin-stack alternative it replaced the need for.

Building something similar?

If your organisation faces a comparable challenge, we can apply the same engineering approach to your context, starting with a free consultation.

Start a conversation

Have an idea or a system to build?

Tell us about your project. We reply with practical advice and a clear way forward.

Start a project