EEntiko
Start a project
← Services

04 · Service

E-commerce

Indian retail is not a theme with a discount bar. People browse on a phone, ask on chat, pay on UPI or COD, and expect the brand to still feel expensive at checkout. We build the catalogue, the lookbook, the bag, the gateway, GST-ready invoices, and the warehouse screen — as software, not as twenty apps piled onto a template.

D2C labels, jewellery and fashion houses, nutrition and wellness, multi-SKU operators who have outgrown Instagram DM as an order book.

When this is not the work. If you need a brochure site with no cart, that is Website design. If you need a custom ERP with no storefront, that is Software development. If you want a theme installed this weekend with dummy products, we are the wrong studio.

Start this work
A website layout on a monitor, with the HTML beside it and a phone on the desk

What this usually fixes

Instagram is the store. DM is the order book.

It worked at twenty orders a week. At two hundred it is a fight. We put catalogue, pay, and fulfilment in software — and keep WhatsApp as a channel, not the database.

The theme looks like every other brand.

Checkout is a plugin. Product pages are a grid. We design selling surfaces as a set so the brand does not fall apart at pay.

Stock, GST, and the courier do not agree.

The site says in stock. The shelf does not. The invoice is a PDF someone types. We connect the ledger the warehouse will actually use.

Paid traffic lands on a slow phone page.

Images take three seconds. The bag janks. We treat Core Web Vitals as a launch gate on mid-range Android — not a later audit.

Pages and screens

What a buyer actually walks through — not a capability matrix.

Home and lookbook

Editorial selling. Campaigns. The first screen a stranger finishes on a train.

Collection and filter

The aisle. Facets that remember. Empty states that still sell.

Product

The page that has to earn the bag: photography, variants, trust, delivery promise.

Bag and checkout

UPI, cards, COD, address, the moment the brand is allowed to feel expensive.

Account, order, return

Where is my order. Exchange. The screens that save a support ticket.

Pack and admin

The 6pm view. Pick, pack, GST, courier. If the floor will not open it, it is not done.

What we build

Custom storefronts

Next.js (or Hydrogen) storefronts with your design system — not a theme every competitor also bought.

Headless commerce

Shopify, Medusa, Saleor, or a custom catalogue when the merchandising rules will not fit a box. The front is yours; the orders still reconcile.

Checkout for India

Razorpay, PayU, Cashfree, UPI, cards, netbanking, COD with the fraud rules you actually use. WhatsApp as a sales floor, not a widget.

Ops behind the order

Stock, returns, partial fulfilments, GST invoices, Shiprocket / Delhivery / your courier, and a packed-by-6pm view.

How deep this goes

Catalogue as a system

Variants, collections, editorial merchandising, 10k-SKU search, filters that remember. Merchandisers run it without a developer every Thursday.

  • Lookbooks and bundles that still add to a real cart
  • Inventory that does not lie between the site and the shelf
  • Multi-currency / multi-warehouse when the business has already grown into it

Payments, tax, fulfilment

Webhooks that idempotently mark paid. Refunds that hit the same ledger. GST invoices. Pincode-aware shipping. The unglamorous path from tap to packed bag.

  • COD, prepaid, partial, and failed-payment recovery
  • Courier APIs and tracking the customer can actually open
  • Admin that the person packing the bag will use

WhatsApp without making it the database

Enquire, abandoned bag, shipping updates — as events on a real order. Catalogues shared in chat still have a SKU. A person can pick up the thread without scrolling a hundred messages.

  • Abandoned-bag recovery that is not a blast to everyone
  • Order status a customer can tap, not a screenshot of an AWB
  • Staff still pack from the admin, not from a group chat

Performance on a phone

Product images that do not take three seconds. PDPs that do not jank. A bag you can edit with one thumb. Measured on mid-range Android, not only on a studio Mac.

  • Core Web Vitals as a launch gate
  • Schema for products and reviews where it is honest
  • Analytics that show funnel drop-off, not vanity sessions

Languages, platforms, tools

The names people search for belong on a service page, not in a footer buzzword strip. This is what we actually ship in.

Storefront

  • TypeScript
  • React
  • Next.js
  • Hydrogen
  • Liquid (when Shopify admin is the merch tool)

Commerce engines

  • Shopify
  • Medusa
  • Saleor
  • WooCommerce
  • Custom Node / PostgreSQL

Payments & ops

  • Razorpay
  • PayU
  • Cashfree
  • Stripe
  • Shiprocket
  • WhatsApp Business

Data

  • PostgreSQL
  • Redis
  • Object storage
  • GST-ready invoicing

What you walk away with

Selling surfaces

Home, collection, product, lookbook, bag, checkout — designed as a set so the brand does not fall apart at pay.

Connected ops

Payments, stock, shipping, and the staff screens. Tested with a real SKU, not lorem products.

Merch handover

How to add a collection, a sale, a sold-out state, without opening a ticket.

Launch week

The first failed payments and the first “where is my order” are part of the job.

How the work runs

A named owner, a written brief, and something you can click early. The longer studio sequence is on Approach.

  1. 01

    Assortment and journeys

    What you sell, who buys, which three paths matter. Everything else waits.

  2. 02

    Design the selling surfaces

    Reviewed as a set. Checkout is a designed page, not a plugin afterthought.

  3. 03

    Stock, pay, ship

    Gateways, tax, couriers. Tested on phones. Then we open the doors.

Questions we hear

Shopify or custom?+

Shopify when merchandising speed and app ecosystem win. Custom or headless when the catalogue, checkout, or ops will not fit. We will not custom-build you a worse Shopify.

Can you connect WhatsApp?+

Yes. Many stores use it as the sales floor: enquire, abandoned bag, order updates. It is a channel on top of a real order database — not the database.

Do you rebuild every year?+

No. We build a system you can merchandise. Redesigns happen when the brand changes, not when a theme expires.

Can you migrate from Shopify / WooCommerce?+

Yes, with a redirect map, a real stock take, and a quiet week of dual-running if the volume needs it. We will not flip DNS on a Friday night with live carts.

Jewellery, nutrition, fashion — do you understand variants?+

Yes. Size, metal, stone, flavour, bundle, made-to-order. The catalogue model is the product. If your merchandising will not fit a box, we say so before we pick an engine.

What about returns, COD fraud, and GST?+

COD rules you actually use, not a toggle. Refunds that hit the same ledger. GST invoices the accountant can file. This is ops, not a plugin list.

Do we need a mobile app as well as the store?+

Only if the customer will open it weekly. Most D2C brands should earn the store on the web first. If you need Android and iOS, that is Mobile apps — same studio — hanging off the same catalogue.

Other capabilities

If this is the work, send the brief.

Contact