the auction is the tax
guwahati tea auction centre sets the price for around half of india's tea. it is a clearing market — efficient, public, and brutally commodity. a garden producing premium first-flush leaves earns the auction price. the brand that retails the same leaves earns four to eight times that.
halmari, esah, ketley gold are visible because they crossed that gap. the eight hundred other estates in assam have the same leaf and a fraction of the margin. the only thing standing between them and the higher number is a digital layer.
what the d2c stack actually is
four moving parts. a storefront that ships in india and abroad — shopify or custom next.js, payments via razorpay and stripe, product pages multilingual in english, hindi, and where it matters japanese or german. an inventory system that tracks every lot to its flush, garden, and plucking date. a subscription engine for monthly tea boxes, single-estate clubs, and gift subscriptions — billing, dunning, pause and skip flows that hold customers between flushes.
a customer-support layer that lives on whatsapp, the website, and instagram, handles brewing questions and order status in three languages, and escalates to a human when the question deserves one. and a small ops backend so you can see daily sales, returns, and channel-mix on one screen.
what changes for the customer
the customer pays in their own currency, sees provenance on the product page — lot number, flush, garden coordinates — gets shipment updates by whatsapp, and asks brewing questions without writing an email. for a tea estate manager, that means returning customers, predictable subscription revenue, and a brand the next generation will inherit instead of an auction lot number.
the timeline
we build this in eight to twelve weeks. the first two weeks are research and stack decisions — your tea, your customers, your unit economics. weeks three through ten are shipping: storefront, inventory, subscriptions, customer support. the last two weeks are handover — documentation, runbook, training your team to operate it without us.
after handover, the system is yours. we are available for the first thirty days at no extra cost. the codebase is plain and the documentation is paste-able, so your own team can take it forward from there.