Case study — clinical skincare online storeSilomin

An online shop for a skincare brand that sells straight to its customers instead of through a marketplace.

Client
Silomin
Year
2026
Industry
Clinical skincare
Live at
silomin.com
What we did
The whole store — storefront, product catalogue, checkout and order flow, and the admin panel behind it.
Built with
  • React
  • TypeScript
  • Supabase
  • Razorpay
  • Shiprocket

01The brief

What they needed

Silomin is a clinical skincare brand. It wanted to sell straight to its customers from a store of its own, rather than through a marketplace that owns the customer relationship and takes a share of every sale.

That meant building everything a marketplace normally provides — the catalogue, payments, shipping, order updates and the tools to run it all — and making it feel like a premium brand rather than a template with a logo on it.

We wanted a store that felt like our brand, not a template with our logo on it. Bitbew built the whole thing — checkout, shipping, the admin we use every day — and explained every decision in plain language along the way.

SilominClinical skincare brand

02The live site

As it is today

This is silomin.com scrolling from the top of its home page — the real thing, not a mockup.

silomin.com
Silomin — the live site, scrolling from the top of the home page

03What we built

Piece by piece

01

Storefront and catalogue

Product pages for the range, with stock levels that show when something is running low or has sold out.

02

Checkout with Razorpay

Online payment through Razorpay, coupon codes and free shipping, in as few steps as a phone screen allows.

03

Shipping and tracking

Fulfilment through Shiprocket, and an order-tracking page so customers can check on a parcel without having to ask.

04

Accounts and reviews

Customer sign-in, order history and product reviews.

05

Admin panel

The brand’s side of the store: orders, stock, products, coupons and customers in one place, with CSV exports.

04Decisions

The choices worth explaining

The parts of the build that were a decision rather than a default, and why.

  1. 01

    A custom store, not a template

    The brand wanted control of its checkout, its customer data and how the products are presented, without monthly app fees stacking up.

  2. 02

    Supabase underneath

    Database, sign-in and file storage in one place, set up in the client’s own account, so the data belongs to the brand.

  3. 03

    Stock treated as real

    Low-stock and sold-out states are part of the catalogue, so what a customer sees matches what is actually on the shelf.

Next step

Tell us what you sell

A link to your Instagram or your current shop is plenty. We will come back with how we would set the store up, and what it would take.

Message us on WhatsAppBook a free 30-minute call

Calls 9 am – 9 pm IST · Mon–Fri