Cuddle Hub
A wellness e-commerce platform for a category where discretion is not a feature but the condition of the sale. Eight product categories, order tracking, cash on delivery, and a packaging flow designed around what the customer does not want anyone to see.
- E-commerce
- Order tracking
- Cash on delivery
- Discreet fulfilment
- Policy suite
01 — The Problem
A store where privacy is the purchase condition
Cuddle Hub is an intimate wellness retailer selling across India. It needed a full storefront: eight product categories, gift and offer collections, search, accounts, a cart, order tracking and cash on delivery.
Ordinary e-commerce, on the face of it. What makes it a different build is the thing sitting behind every one of those features.
In this category, discretion is not a reassurance you print on the homepage. It is the condition the customer buys under. If any part of the system leaks what was ordered — a delivery label, an email subject line, a line on a statement — the sale was a mistake from the customer’s point of view, no matter how good the product was.
That turns a marketing promise into an engineering requirement with a hard property: it has to hold at every point where the order touches the outside world, and those points are scattered across completely different parts of the system.
02 — The Approach
Design outward from the moment of delivery
Most storefronts are designed from the catalogue forward. This one is designed from the doorstep backward, because that is where it can fail in a way the customer will not forgive.
Treat discretion as a property of the whole order path
Discreet packaging is the visible part, and the part customers ask about. But the same requirement applies to everything the order emits on its way out — what a courier can read, what a notification says, what a shared device shows.
WhyPrivacy is not additive; it is a chain. Nine careful decisions and one careless one produce an indiscreet order, and the customer only ever experiences the careless one. Treating it as a single cross-cutting property rather than a checkbox on the packaging screen is the only version of this that actually holds.
Make order tracking self-service, deliberately
Track Order sits in the primary customer support column rather than behind a support request.
Why“Where is my parcel?” carries more anxiety here than in most retail, and the conventional answer — contact support and describe your order to a stranger — asks the customer to do the exact thing they came to this shop to avoid. Self-service tracking is a privacy feature wearing a logistics feature’s clothes.
Publish the full policy suite, not a summary
Shipping, cash on delivery, returns, refunds, cancellations, privacy, terms and a disclaimer are each published as their own document.
WhyThis is a trust-led purchase from a retailer most buyers have not used before. The policies are not legal furniture here — they are the part of the page a hesitant customer actually reads before deciding. And as the next section explains, several of them describe genuinely distinct flows rather than restating one another.
03 — Key Technical Challenges
Two problems worth solving properly
Cash on delivery breaks the shape of an order
In a prepaid store, checkout and payment are the same moment, and almost every downstream flow quietly depends on that. Cash on delivery pulls them apart: the order is confirmed on the site and the money arrives days later at a doorstep, from a courier, possibly not at all.
Everything after checkout inherits that gap. Cancelling an unpaid order is not the same operation as cancelling a paid one. A refund on an order that was never charged is a different thing again. Treat COD as a payment method toggle and those differences surface later as edge cases nobody modelled.
Payment is modelled as its own part of the order’s life rather than a property set at checkout, so an order can legitimately exist as confirmed-but-unpaid without the rest of the system treating that as a fault.
That is also why shipping, cancellation, return and refund are four separate published policies rather than one. They are four genuinely different flows, and writing them separately was a consequence of modelling them separately.
COD works as a first-class path rather than a special case bolted onto a prepaid assumption — which matters commercially, because in this category paying at the door is also the option that leaves nothing on a statement.
Merchandising a catalogue you cannot put on the doormat
A storefront has to help someone find the right product, which normally means showing it prominently and often. Here the same instinct works against the customer: browsing may happen on a shared phone, and the customer’s comfort depends on how much the interface volunteers.
Meanwhile the practical problem does not go away — a first-time buyer in an unfamiliar category needs structure and reassurance more than most, not less.
The navigation carries the weight instead. Eight clear categories plus gift and offer collections let someone move directly to what they want, and the store leads with the reassurance rather than the merchandise — discretion, privacy and support are stated in the header before a single product is.
Editorial content is positioned the same way, as guidance written for people rather than copy written for a catalogue.
The store reads as a considered retailer rather than a warehouse, which in a trust-led category is the difference between a browser and a customer.
04 — What We Built
A complete storefront, and the parts around it that earn trust
Storefront
- Eight product categories
- Gift shop and offer collections
- Search, accounts, cart and notifications
- Trends, deals and sale groupings
Orders
- Cash on delivery as a first-class path
- Self-service order tracking
- Discreet packaging through fulfilment
- Delivery across India
Trust surface
- Eight published policy documents
- Shipping, COD, return, refund and cancellation each stated separately
- Privacy, terms and disclaimer
Support
- Contact routes and any-time support line
- Editorial guidance written for customers
- Social presence linked from the footer
05 — The Result
Built, and being filled
The platform is built and in its final stage. The client’s team is loading the catalogue now, which is the last thing that has to happen before a store like this can open — and the reason there is no public address to send you to yet.
We would rather say that plainly than point you at something unfinished. When it launches, this page gets a link like every other case study here.
This is the one case study on this site you cannot go and check yet, so we have kept it to what the build actually contains — no framework name-dropping, no performance claims, and no numbers. Everything above is either visible in the screenshot or a decision taken during the build.
Selling something that needs handling with care?
We build commerce where trust is the hard requirement — and treat it as an engineering property rather than a badge in the footer.
Start a conversation