Wedding Registry and Gift Platform — India Deep-Dive

The wedding registry and gifting workflow in India is entirely manual and fragmented, distributed across three actors:

The couple and their family — list-making is done on paper, WhatsApp broadcast lists, or Google Sheets. The bride's side and groom's side each maintain separate lists. Items range from kitchen appliances and cash envelopes (shagun) to gold, electronics, and travel packages. The couple receives gifts they may not need or want; duplicates are common. Tracking who gave what for thank-you notes is done by memory or last-minute WhatsApp queries.

The wedding planner (where one exists) — in Tier 1 and some Tier 2 cities, planners coordinate guest logistics but do not manage the gift registry. They may maintain an Excel sheet of gift lists passed from the family, but this is not a structured registry. Planners charge ₹50,000–₹5,00,000+ per event and are not incentivized to push registry tools.

The informal broker / "wedding consultant" — in smaller cities and towns, a local联系人 (contact person) coordinates between the couple's family and guests, often collecting cash gifts and delivering them. They operate on trust, take a 2–5% cut, and keep no digital record. This role exists because no digital tool bridges the gap between guests who want to give meaningfully and families who need coordination.

Where time and money leak:

• Couples spend 40–80 hours managing gift lists across WhatsApp, phone calls, and notebooks
• Duplicate gifts cost ₹5,000–₹30,000 per wedding in unnecessary exchanges or donated items
• Untracked shagun collections mean families lose visibility on who gave what, complicating thank-you notes and future social obligations
• Guests in other cities or countries have no reliable way to contribute toward high-ticket items ( Appliances, honeymoons, home down payments)
• No digital record exists for the thank-you note obligation cycle — Indian weddings create long-term social debt that is currently managed through memory and informal notes

Who profits from it staying manual:

• Informal brokers and wedding consultants — their role depends on information asymmetry and manual coordination. A digital registry removes their information monopoly.
• WhatsApp — the platform benefits from the coordination traffic but has no business model around it.
• Families who benefit from opaque gift flows — in some cases, manual tracking allows selective memory about what was given, which serves social purposes.

Who is hurt by the manual system:

• The couple — they receive unwanted items, spend time on coordination, and feel social pressure around thank-you note obligations
• Out-of-town and international guests — they want to give meaningfully but have no reliable channel to coordinate large gifts or contributions
• Wedding planners — an uncoordinated gifting process reflects poorly on them and creates last-minute chaos they must manage anyway
• Families in joint or extended-family arrangements — multiple household contributions are impossible to track fairly without a shared system

Who would pay to change it:

• Couples in the 25–35 age bracket in urban India, especially those with significant out-of-town or international guest lists, would pay ₹2,000–₹10,000 for a structured registry if the process is genuinely simpler than WhatsApp
• Wedding planners at the mid-to-premium tier (₹1 lakh+ engagements) would pay per-event licensing for a white-labeled registry tool, as it differentiates their service
• Families hosting large joint weddings (100–500+ guests) where gift coordination is genuinely complex

The resistance point:

Indian wedding gifting is deeply embedded in social ritual. Cash (shagun) in a decorative envelope is the default gift in most of India outside metro elite circles. A registry that doesn't account for cash will be dismissed by the majority. The wedge must accommodate shagun as a first-class item, not treat it as an edge case.

The narrow product / service / agent:

A WhatsApp-native wedding gifting coordination agent — not a website or an app. The couple (or their wedding planner) adds the agent to a WhatsApp group. The agent:

• Maintains a shared gift list visible to all group members
• Accepts natural-language inputs ("Ravi auntie gave us a kitchen set" or "we received ₹5,000 from Rahul's office")
• Sends a clean summary to the couple after the wedding: who gave what, what remains untracked, and a draft thank-you note template per guest
• For cash gifts, generates a shareable payment link (UPI) that auto-logs the giver's name when the couple confirms receipt

What it does on Day One:

• A wedding planner or couple adds the bot to a WhatsApp group
• They send a list of expected guests and high-level gift categories (cash, physical, wishlist items)
• The bot maintains the running list; any group member can query "what has been gifted so far" or "who is giving the microwave"
• After the wedding, the couple gets a summary export as a WhatsApp message with a downloadable CSV
• The thank-you note drafting is done via a follow-up WhatsApp message from the bot: "Here's your draft message for Aunt Meera who gave ₹3,000. [Approve / Edit / Send]"

Who pays and how much:

• SHAPE: per event — ₹2,500 for a basic package (gift list + summary + 50 thank-you drafts), ₹8,000 for a premium package (white-labeled for planners, unlimited guests, multi-event support for sangeet/mehendi/wedding/reception)
• Secondary: ₹500/month per wedding planner for a dashboard showing all their events' gifting data — enables upsell of other services
• Not: per-seat (guests don't pay), per-order (no e-commerce component on Day One)

Why WhatsApp first:

No app download for guests. The couple's WhatsApp group is the distribution channel. The agent lives where the coordination already happens. This dramatically reduces the friction that killed every "wedding registry app" in India — guests won't install a new app to RSVP a gift.

In India:

• Bridal shagun / gift registry services — these are largely wedding planner add-ons, not standalone products. No dominant digital-native brand exists in this space
• Amazon Wedding Registry — exists globally; India adoption is minimal and limited to urban couples already shopping on Amazon. Not WhatsApp-native, not built for Indian gifting norms (cash, gold, shagun)
• NoPassword, Happily, and similar wedding registry startups — operated in the US/UK market; no verified India operations as of 2026

Globally (for reference, not India):

• Zola (US) — the category leader;combines registry, wedding website, and guest management. Built for US norms (honeyfund, experiences). Not adapted to Indian market
• Blueprint / Guide — smaller US players
• Prezenty — Polish and European market

Unverified — I cannot confirm Indian-specific wedding registry startups with active products. The space appears underserved in India, but the absence of players may reflect structural barriers (cash gifting norms, WhatsApp dependency, no app-download willingness), not just market opportunity.

Fact 1: Indian couples and families will not use a digital gift list — they rely entirely on WhatsApp broadcast and trust, and any third-party tool breaks that trust.

• How to check cheaply: Interview 10 couples who married in the last 2 years in Tier 1 and Tier 2 cities. Ask: "How did you track who gave what? Was any digital tool used?" If 7+ out of 10 used only WhatsApp or paper, this fact is confirmed and the idea is structurally weak. Budget: ₹3,000 (small incentives for interviews). Pass mark: at least 4 out of 10 had tried some form of digital tracking.

Fact 2: The shagun (cash gift) norm cannot be integrated into a digital registry without making the whole system feel transactional and inappropriate.

• How to check cheaply: Show 10 couples (or their parents) a prototype WhatsApp message that reads: "Ravi auntie has sent ₹2,000 via UPI for your wedding. Confirm receipt?" Ask: "Does this feel normal or does it feel weird?" If 6+ out of 10 say it feels weird or transactional, the cultural barrier is real. Budget: ₹1,500. Pass mark: majority comfortable with the framing.

Fact 3: Wedding planners will not pay for a per-event tool that requires them to learn and sell a new product to resistant clients.

• How to check cheaply: Talk to 5 wedding planners in your target city. Show them the product concept. Ask: "Would you pay ₹2,500 per event for this? Would you use it with your clients?" If zero planners say yes, the B2B channel is broken. Budget: ₹1,000. Pass mark: at least 2 out of 5 say they would trial it with one client.

Budget: ₹12,000

• WhatsApp Business API setup (Twilio or Gupshup): ₹0 (development tier)
• Bot development (2 weeks, part-time developer or Claude Code session): ₹0 internal
• Test events: target 5 real weddings from personal network
• Interview compensation for falsification checks: ₹4,500
• UPI payment link integration (Razorpay or CRED): ₹0 (no charges at this scale)
• Misc (域 forwarding, landing page): ₹7,500 (hosting + small design)

Pass mark:

• At least 3 out of 5 couples complete the post-wedding summary and say they would use it again
• At least 3 out of 5 couples share the bot or list with at least 5 guests
• Zero complaints about the WhatsApp interface feeling intrusive or transactional
• At least 1 wedding planner agrees to a paid pilot at ₹2,500

What NOT to build before the test: A website, an app, a dashboard, any e-commerce integration, or a multi-language version. The test is only: does the WhatsApp agent solve one real problem for one real wedding?

AGENCIFY first, PRODUCTIZE second, AI-FY is premature.

The Indian wedding gifting coordination problem is a service problem before it is a product problem — couples don't need a new app, they need someone to handle the WhatsApp chaos. An agency model (a managed WhatsApp coordination service run by a small team with AI tooling) is the fastest path to revenue and learning. Productize only after 10+ paid events have validated the exact workflow couples follow, the exact WhatsApp templates that work, and the exact price point that converts. The AI agent (a fully autonomous WhatsApp wedding coordinator) is a Phase 3 move, not a Day One bet — theLLM reliability requirements for social/ritual interactions are not yet good enough to trust without human review on every message.

Availability confirmed against the .in registry (RDAP) on 2026-09-22. Prices and ownership read from our own intelligence tables. Nothing here is estimated.

Single-word, available now

• desireds.in — available
• registrys.in — available
• desired.co.in — available
• desireds.co.in — available
• registrys.co.in — available
• registries.co.in — available

Also available (compound)

• desiredhub.in
• desiredmart.in
• desiredkart.in
• desiredmandi.in
• desiredbazaar.in

Listed for sale

• mywedding.in · price not listed on afternic · seller holds 55 domains

Taken and developed — do not chase

• registry.in · entropy 7.09
• mywedding.in · entropy 4.62
• myweddings.in · entropy 4.64

---

Generated 2026-09-22 22:40 UTC. Topic from our research queue; no market-size figure appears here unless a source is named. The domain block above is read from our own intelligence tables and confirmed at the .in registry (RDAP); the model wrote the analysis, not the domain facts.