When the catalogue is the salesperson — a product master that sells for a diamond wholesaler
How Yukti AI built Shinelabb a single product master and a catalogue engine that turns any selection of designs into a shareable, live-priced link or PDF — with a buy-now flow, per-catalogue analytics, and a theme engine that runs two brands from one system.
Shinelabb is a lab-grown and natural diamond wholesaler. Client catalogues were built by hand, priced manually, and once sent, told the sales team nothing. Yukti AI built a product master of every design — SKU, collection, gold weight, diamond carat and count, making charges, photos, stock — with prices computed live from the gold rate, and a catalogue builder that generates a no-login client link (like, buy-now, order request) and a branded PDF from the same selection, plus analytics on opens, likes, buys and conversion by staff member. One system, two brands (Shinelabb and Diamera).
Quick facts
| Client | Shinelabb (running two brands: Shinelabb and Diamera) |
|---|---|
| Location | Surat, Gujarat |
| Industry | Diamond & jewellery — lab-grown and natural, wholesale |
| Core challenge | Client catalogues built by hand and priced manually; once sent, no signal on what the client looked at or liked |
| Solution | Custom product master + shareable client-catalogue engine with analytics |
| Modules | Products Master, Catalogue Builder, Public Catalogue page, Buy-Now / order requests, Catalogues dashboard, Catalogue Analytics, Pricing Engine, Brand Theme engine, PDF export |
| Live pricing | Every design priced by a function off the current gold rate — shared links reflect rate changes automatically |
| Catalogue | 76 designs with real photography, SKU, collection, gold weight, diamond carat / count, making charges, stock, tags |
| Multi-brand | Shinelabb and Diamera — colours, logo, UPI ID and PDF branding switch per catalogue |
| Stack | Vite + React + TypeScript, Tailwind CSS, jsPDF, qrcode |
| Result | A catalogue in minutes, always correctly priced, with opens / likes / buys / conversion tracked per catalogue and per salesperson |
For a diamond wholesaler, the catalogue does the selling
Shinelabb sells to retailers and trade buyers. A buyer rarely visits — the deal starts with a catalogue of designs, sent over WhatsApp or email, and the buyer picks from it. The catalogue is the shop window. So the quality of that catalogue — how fast it goes out, whether the prices are right, whether it is tailored to what this buyer actually stocks — is the difference between a reply and silence.
Two things make a wholesale jewellery catalogue hard to keep good. First, price moves daily — every design's price depends on the current gold rate, so a catalogue built last week is quoting last week's prices. Second, a sent catalogue is a black box — the sales team has no idea whether the buyer opened it, which designs they lingered on, or whether it is worth a follow-up call.
A catalogue system for a wholesaler has to do two things a PDF cannot: re-price itself when the gold rate moves, and report back what the buyer did with it.
What Shinelabb was doing by hand
- "Every catalogue is assembled from scratch." Pulling images and details together design by design, for each buyer.
- "Prices are typed in, and they go stale." A manual price is wrong the moment the gold rate moves.
- "Once it's sent, we're blind." No idea if the buyer opened it, or which pieces caught their eye.
- "We can't tell which designs actually sell." The best-performing pieces were a gut feeling, not a number.
- "Two brands, two sets of everything." Shinelabb and Diamera needed separate branding on every catalogue and PDF, maintained by hand.
How the catalogue changed
Before
- Catalogues assembled by hand, per buyer
- Prices typed in and immediately at risk of being stale
- No visibility once a catalogue was sent
- Best-selling designs a matter of opinion
- Two brands maintained separately
After
- Select designs from one master → catalogue link + PDF in minutes
- Every price computed live from the current gold rate
- Opens, likes, buy-now starts and orders tracked per catalogue
- Conversion by design and by salesperson, on a dashboard
- One product master, brand theme switches per catalogue
Why a custom build, not a catalogue app or a design tool
There are catalogue-maker apps and there is Canva. Neither knows what a diamond design costs today, neither ties a catalogue to a specific buyer and a specific salesperson, and neither tells you what the buyer did after you sent it. For a wholesaler running two brands off one design library, "make a nice PDF" is the smallest part of the problem.
| What a diamond wholesaler needs | Catalogue app / Canva PDF | The system we built |
|---|---|---|
| Price each design from the live gold rate | Manual, goes stale | Computed by the Pricing Engine on every view |
| One product master feeding every catalogue | Re-uploaded each time | Single master, select-and-send |
| Tie a catalogue to a buyer & a salesperson | Not a concept | Built into the Catalogue Builder |
| Know what the buyer opened / liked / bought | Nothing after you send | Per-catalogue analytics + send log |
| Conversion by salesperson | Not available | Admin analytics roll-up |
| Two brands from one library | Two separate sets of files | Brand theme engine switches per catalogue |
| Buyer can express intent (like / buy-now) | Not possible in a PDF | On the public catalogue page |
From product master to tracked order
Users work in the Products Master and Catalogue Builder. The Pricing Engine keeps every price live. Shared links and PDFs carry the same data outward, and every interaction flows back into analytics.
The modules
Products Master
One record per design — SKU (continuing Shinelabb's own SL-XXX-### numbering), name, category, collection, gold weight, diamond carat and count, making charges, stock level, tags and real product photography. 76 designs across pendants, earrings and rings were built in from the client's actual photo library. Benefit: one source of truth for every design, instead of images scattered across folders and chats.
Pricing Engine
A single pricing function computes each design's price from the current gold rate, the design's gold weight, its diamond value and making charges. Nothing is hard-coded. Change the rate and every catalogue — including links already shared with buyers — updates. Benefit: a wholesale catalogue that is never quoting yesterday's gold price.
Catalogue Builder
From the Products Master, toggle "select for catalogue" on the designs you want, then a floating bar leads to "create catalogue": name it, choose the brand (Shinelabb or Diamera), choose which staff member is sending it, and optionally tie it to a customer and phone number. Out comes a short link. Benefit: a tailored catalogue for a specific buyer in the time it takes to pick the designs.
Public catalogue page
The client opens the link with no login and sees only the selected designs, at live prices, in the correct brand's colours. They can like a design, or start a buy-now flow — a payment page with a client-side-generated demo UPI QR code and a name / phone field — that ends in an order request. Benefit: the buyer can express interest or intent without a phone call, and the sales team sees it immediately.
Order requests & confirmation
An incoming order request updates a live badge in the staff sidebar — even across separate browser tabs. Staff confirm it, and the system creates a real order directly (skipping the lead stage, per Shinelabb's process). Benefit: the path from "buyer liked this" to "this is an order" is one click.
Catalogues dashboard & Analytics
The Catalogues page shows per-catalogue engagement at a glance, with click-through to a per-design breakdown. Catalogue Analytics is the admin roll-up: which staff sent how many catalogues, opened / liked / bought / ordered counts, conversion percentage, and a full send log. Benefit: the best designs and the best salespeople are visible as numbers.
Brand theme engine
One product master, two brands. brandData is the single source of truth — Shinelabb's black and gold, Diamera's deep green and gold, each with its own logo, UPI ID and PDF branding. Colours were sampled directly from the real logo pixels, and the logos were background-removed and tight-cropped so they render cleanly at header size. The public catalogue page, the buy-now QR, and the exported PDF all switch on the catalogue's brand. Benefit: two brands run from one system with zero duplicated maintenance.
PDF export
A catalogue PDF with the correct brand logo embedded on the cover and brand colours throughout, using the same live pricing as the link. Benefit: a link for buyers who browse online, a PDF for buyers who want a file — from one selection.
Where AI extends a catalogue system
The Shinelabb build is a clean, self-contained catalogue engine. The same data — designs, engagement, conversion — is what an AI layer works from, and Yukti AI's jewellery systems add it as a next phase:
- Smart catalogue assembly — "build a bridal catalogue for a buyer who liked these three designs" and the system proposes a matching selection from the master.
- Follow-up prompts — a buyer opened a catalogue three times and liked two designs but never ordered: surface it for a call today.
- Design performance insight — which collections, carats and price bands convert, which are dead weight, and how that shifts by buyer type.
- Plain-language questions — "which catalogues sent last month have not been opened", "which salesperson's catalogues convert best" — answered from the analytics data.
- WhatsApp delivery — generate and send the catalogue link over WhatsApp from a short instruction.
What runs without anyone pressing a button
Gold rate changes → every catalogue re-prices
Client engages with a catalogue → the sales team knows
Catalogue created → correct brand everywhere
What each person works with
Owner / Admin
The full Catalogue Analytics roll-up — catalogues and conversion by salesperson — plus the Pricing Engine and brand configuration.
Salesperson
The Products Master, the Catalogue Builder, their own sent catalogues and per-catalogue engagement, and incoming order requests.
Client (no login)
Only the designs selected for them, at live prices, in the right brand — with like and buy-now, and nothing else.
How it was built
Product master from real photos
The client's real jewellery photo library — 56 images with vendor SKU-style filenames — brought in and turned into full catalogue entries, continuing Shinelabb's own numbering.
Live pricing, not hard-coded
A pricing function wired to the gold rate so every design, old and new, prices itself — and stays correct as the rate moves.
The sharing flow
Catalogue builder → no-login public page → like / buy-now → order request → staff confirm to a real order, with a live cross-tab badge.
Analytics
Every open, like, buy-now start and order recorded against the catalogue, rolled up per catalogue and per salesperson.
Multi-brand theming
Real logos processed and colours sampled from them; one theme source of truth wired into the public page, the QR, and the PDF.
What changed
Factual — no invented numbers.
Technology
- Vite + React + TypeScript — a fast single-page app; the public catalogue page is rendered standalone, outside the authenticated shell, so a shared link loads clean.
- Tailwind CSS — the interface, themed per brand from a single config.
- qrcode — the buy-now UPI QR is generated client-side, no network dependency.
- jsPDF + jspdf-autotable — the branded catalogue PDF, with the real logo embedded on the cover.
Shinelabb owns all product and catalogue data. The catalogue-sharing store persists to keep a shared link visible to staff across browser tabs, and the design is built to move to a hosted database as the next step.
If you sell by sending designs or SKUs, this is buildable for you
A product master plus shareable, live-priced, analytics-tracked catalogues fits any business that sends a selection of products to buyers:
- Jewellery brands and diamond wholesalers (see the Lumera and Surati case studies)
- Textile and fashion wholesalers sending design sets to buyers
- Hardware, tile, furniture and building-material distributors
- Any manufacturer whose reps carry a catalogue to clients
Start with a free workflow audit. See Jewellery Software, Custom Web Apps or the full AI Business Management System.
Questions about catalogue software
Explore more
Jewellery Software
Custom diamond & gold inventory, metal ledger, WhatsApp catalogue, GST billing and CRM.
Case study: Lumera Fine Jewellery
A full custom jewellery ERP + CRM — inventory, metal ledger, catalogue and GST billing.
Case study: Surati Jewellery Factory
A jewellery CRM with a two-way WhatsApp inbox and AI auto-reply grounded in the catalogue.
Custom Web Apps
Shareable customer-facing tools — catalogues, order pages, portals — built to your workflow.
Diamond & Jewellery Automation
How Surat's jewellery businesses automate enquiries, catalogues and follow-ups.
All case studies
Every Yukti AI build — jewellery, manufacturing, trading and services.
Summary
Yukti AI built a product-master and shareable client-catalogue system for Shinelabb, a lab-grown and natural diamond wholesaler in Surat that runs two brands (Shinelabb and Diamera). The system holds one record per design — SKU, collection, gold weight, diamond carat and count, making charges, photos and stock — with prices computed live by a pricing function from the current gold rate rather than hard-coded, so shared catalogues re-price automatically. A catalogue builder turns any selection of designs into a no-login public link (like, buy-now with a client-side UPI QR, order request that staff confirm to a real order) and a branded PDF from the same selection. Per-catalogue analytics track opens, likes, buy-now starts, orders and conversion, rolled up by salesperson. A brand theme engine switches colours, logo, UPI ID and PDF branding per catalogue from one product master. Built on Vite, React, TypeScript, Tailwind, jsPDF and qrcode. Yukti AI builds comparable catalogue systems for jewellery, textile, fashion and distribution wholesalers across India.