← All work
Product/Catalogue SaaS/2023 — 2024/Live

Product Share

Catalogue SaaS for Instagram and WhatsApp sellers — upload products once, get a branded storefront link, and take enquiries on WhatsApp instead of re-sending the same photos in DMs.

Next.jsTypeScriptFirestoreCloudflare R2Razorpay
Duoph TechnologiesVisit live ↗
01

The problem

A boutique with 150 dresses and six thousand Instagram followers answers the same DM all day: price, colours, size M, send designs. The seller re-sends the same photos by hand, dozens of times. A full ecommerce build is far too heavy for them, and a WhatsApp catalogue is far too thin — so Product Share sits in the gap: one link that holds the whole range.

02

Who uses it

3 groups

Instagram-first sellers

One link to drop in a bio or a reply, instead of re-sending the same photos and prices every day.

Their customers

Browse the real range — sizes, colours, prices, availability — and ask about one item without making an account.

Sellers who are growing

To know which products people actually open, and where the traffic came from — which Instagram never tells them.

03

Workflow

6 stages
01Seller signs up
02Add products
03Publish storefront
04Share one link
05Customer browses
06WhatsApp enquiry
01 · OnboardTriggerSeller signs up and picks a storefront nameSystemFirebase Auth (Google), store record with a unique slugOutputA live address like productshare.in/luna, in under five minutes
02 · UploadTriggerSeller adds a productSystemDashboard form plus an image pipeline on uploadOutputProduct with variants, sizes, colours and pricing; images resized to four widths
03 · PublishTriggerSeller publishes the catalogueSystemNext.js storefront routes per store, category and productOutputA public catalogue that Google can index, not a page hidden behind an app
04 · ShareTriggerSeller shares the link or prints the QR codeSystemBio link, stories, packaging, visiting cards, shop counterOutputCustomers land on the full range — no login, no app, no email
05 · EnquireTriggerCustomer taps Enquire on a productSystemwa.me deep link with the message pre-composedOutputWhatsApp opens already saying which product, SKU and price
06 · MeasureTriggerEvery view, tap and share on the storefrontSystemCustom event pipeline over store and product activityOutputStore views, product views, WhatsApp clicks and traffic source per seller
04

How it was built

7 parts

One link instead of a DM thread

The whole product is built around a single shareable address per seller. Every design decision follows from that: the storefront has to load fast on a phone, read well from an Instagram bio, and show the entire range without the customer signing up for anything.

Storefronts Google can read

Each store, category and product is a real rendered route rather than a client-side shell. That makes catalogues findable outside Instagram, which turns every seller's storefront into its own small source of traffic.

An image pipeline, not raw uploads

Sellers upload straight from their phones, so originals arrive at five to ten megabytes. Each upload is resized into thumbnail, card and product widths with the original kept aside, and served from object storage behind a CDN. On mobile data this is the difference between a catalogue that opens and one that gets closed.

WhatsApp without the WhatsApp API

Enquiries are wa.me deep links carrying a pre-composed message with the product name, SKU and price. No API onboarding, no per-message cost, and it works from the first day a seller publishes. The business API is a later problem, not a launch blocker.

Subscription billing

Razorpay subscriptions with webhook-driven entitlement: activation, renewal, cancellation and failed payment each move the store's plan state. Product limits and branding removal are enforced from that state on the server rather than hidden in the dashboard UI.

A free tier that markets itself

Free stores are capped and carry a Powered by Product Share line. Every free catalogue shared into a WhatsApp group is a link back, which makes the cheapest plan the acquisition channel.

Deliberately not a cart

Checkout, delivery and order management were left out on purpose. Adding them turns the product into a small, worse Shopify. Catalogue, sharing, WhatsApp and analytics is a complete thing to sell on its own — and it is what the customer actually asked for.

05

What it is built with

Application

  • Next.js
  • TypeScript
  • Tailwind CSS
  • shadcn/ui

Platform

  • Firebase Auth
  • Firestore
  • Vercel

Media

  • Cloudflare R2
  • CDN
  • Multi-size processing
  • next/image

Billing & comms

  • Razorpay subscriptions
  • Webhooks
  • wa.me deep links
  • QR catalogue
06

Outcome