Skip to content

Case study / Online store

Trihutbaba

An online store for an agriculture supply shop in Nepal, in English and Nepali, with local payment methods and an admin area for the owner.

The problem

The Trihutbaba store sells farm machinery and tools, and needed a proper way to manage and sell them online.

What it had to do

  • Be simple to use, because its customers are farmers
  • Be readable in Nepali
  • Take the payment methods people in Nepal already have

What was built

A storefront in English and Nepali with products, categories, a cart and checkout, and an admin area where the owner manages products, categories, orders and customers.

Checkout supports eSewa, Khalti and cash on delivery. An order moves through pending, paid, processing, shipped and delivered.

It has not launched: there is no public address yet, so no real orders or payments have gone through it. Weather forecasts for farmers are planned.

My part

  • I started this on my own and am building it end to end.

Decisions that shaped it

  1. Two languages from the start

    Every page exists under an English and a Nepali address, with each language’s wording in its own file. Adding Nepali later would have meant touching every screen again.

  2. The browser is never trusted on price

    The order is created on the server first. When a payment comes back, the server checks its signature and the amount, asks the provider to confirm it, and refuses to mark an order paid twice.

The outcome

The storefront, admin area and payment code are in the public repository. It is still in progress and has not launched.

What you can check

Code

The whole project, including the payment routes and both languages.

Open: Code, Trihutbaba (opens in a new tab)
Not live

There is no public address yet, so there is nothing to click through.

Have something like this in mind?

Tell me what you are building. You get a written scope and a fixed price before any work starts.