Jewellery ERP software in Surat
with AI and automation, built around your business.
Yukti AI builds a custom software system for your jewellery business — diamond and gold inventory, a live metal ledger, karat-wise stock, certification, job work, a client catalogue that sends on WhatsApp, GST billing and a customer CRM, all in one platform. Ready-made jewellery software is built for a showroom's billing desk. Ours is built for how you actually work — manufacturer, wholesaler or brand — with AI watching your stock and your sales.

Jewellery software is one system that runs a jewellery business — inventory of diamonds, gold and finished pieces, a live metal and stone ledger, karat-wise stock, certification, job work and karigar tracking, a client catalogue that sends on WhatsApp, GST billing and a customer CRM — instead of separate Excel files and registers. Yukti AI builds a custom jewellery system around how your business actually works, whether you manufacture, wholesale, trade diamonds or run a retail brand, with an AI layer that watches stock movement, ageing pieces and customers who are going quiet. Delivered on a working version of your workflow, live in days or weeks depending on scope, one-time build with 12 months of support. If you also sell online, see our Shopify jewellery store guide.
The trade runs on Excel, memory and a lot of WhatsApp.
Diamonds in one file, gold in another, finished pieces in a register. Every order deducted manually, piece by piece — and the metal ledger never quite tallies.
The same designs sent to every client, prices retyped each time, photos scattered across chats. Making a proper catalogue for a customer takes an hour.
WhatsApp enquiries, no follow-up, no history. You don't know a regular buyer's taste, their last purchase or their occasion until you scroll back through chats.
Everything a jewellery business needs — in one system.
We build only the parts your business needs, but stock, ledger, catalogue, billing and customers all live in one place. Here is what each module does, why it matters and how it works in practice.
Diamond, gold & piece inventory
Diamonds are tracked by shape, size, carat, colour and type (natural, lab-grown, moissanite); gold and metal by weight and karat; finished pieces with full specs and images. Why it matters: one place to answer "do we have this" instead of three files that never agree. In practice: an order for a 1.20 ct oval lab-grown solitaire ring deducts the exact stone and the gold weight from stock the moment it is confirmed.
Live metal & stone ledger
Gold and silver given out, returned, and the running balance by karat, per vendor and per karigar. Why it matters: the metal position is always current, so there is no month-end reconciliation and no argument about how much gold sits where. In practice: issuing 45 g of 18k to a karigar for a bangle order updates his balance immediately, and the finished-piece receipt closes it against actual weight and wastage.
Catalogue on WhatsApp
One product master; generate a professional client-facing catalogue in seconds with your own pricing rules — live metal rate, making charge, margin — and send it as a PDF on WhatsApp. Why it matters: the catalogue every salesperson sends is current and on-brand, not a folder of old photos. In practice: a wholesaler shares a 40-piece bridal catalogue with a retailer, each piece priced at today's gold rate, with a buy-now link.
Job work & karigar
Material issued to a karigar is tracked out and back, with a simple mobile view for progress. Why it matters: nothing on the bench is lost, and every karigar's pending work and metal balance is visible. In practice: a piece out for polishing and stone-setting shows which karigar has it and how many days it has been out.
GST billing & payments
GST invoices with separate diamond, metal and making-charge lines, generated straight from an order, with certification details and an outstanding report across every customer. Why it matters: billing matches the piece specification exactly, and hallmark and certificate numbers are on the invoice. In practice: scanning a piece's QR code pulls its full spec into a GST invoice in seconds.
Customer CRM
Every customer with their taste, budget, occasions, past purchases and follow-up reminders, plus a two-way WhatsApp inbox and a lead pipeline. Why it matters: a regular buyer's history is on one screen instead of scrolled back through chats. In practice: an anniversary coming up for a past buyer prompts a reminder to send a matching-set catalogue.
If your business runs on Excel and a register today, this is the shift to replace Excel and Tally with one connected custom ERP — read what to look for in jewellery ERP software before you choose one.
Want help applying this to your business?Send us your current setup on WhatsApp. Free workflow audit, reply the same day — in Hindi, Gujarati or English.
Get a free workflow auditAn AI that watches your stock and your customers.
A database with screens is just data entry. What makes this AI-powered is a layer that reads your live data and tells you what needs attention — without anyone running a report.
A summary every morning
Sales, new enquiries, orders in progress, gold position and what's pending — a short WhatsApp message to the owner every day.
Slow-moving and ageing pieces flagged
Designs sitting too long, a karat running low, a job that's overdue with a karigar, a piece out for approval and not returned — surfaced early.
Buyers about to slip away
A regular customer who hasn't bought in a while, an enquiry that went cold, an occasion coming up for a past buyer — the AI nudges you to reach out.
And it runs the follow-ups
Enquiry replies, catalogue sharing, payment reminders, order-status updates — handled automatically, so your team focuses on selling.
Why not just buy Marg, Jwelly or another jewellery package?
Three jewellery businesses already running on Yukti AI.
Lumera — diamond jewellery brand
A full ERP/CRM: orders with complete diamond and gold specs, a live metal ledger, catalogue, inventory, barcodes and GST invoicing, plus a WhatsApp enquiry bot. The system now generates Lumera's customer invoices directly — it replaced six-plus separate Excel files.
Surati Jewellery Factory — manufacturing
A CRM with a custom lead pipeline, a two-way WhatsApp inbox so the whole team replies from one place, catalogue sending, invoicing and full conversation history per customer.
Shinelabb — lab-grown wholesale
A product master plus client-facing catalogue generation — silver, lab-grown and natural, karat-precise gold weight, certification handling, GST display, and one-tap WhatsApp catalogue PDFs.
Shopify stores and online catalogues for jewellery brands
Yukti AI builds the online store as well as the back office. Two recent builds are custom Shopify stores for jewellery brands: Shinelabb, which sells lab-grown diamond and moissanite jewellery, and Miswah Jewellery, an Indian online jewellery brand. Both are custom Liquid themes on Shopify's free Dawn theme, so checkout, cart and filters stay native, and each took about 7 days of build work.
Jewellery is hard to sell on a standard Shopify theme for three reasons: every option multiplies the variant count, diamond specs typed as free text cannot be filtered, and a flat menu hides a large catalogue.
Shinelabb: variants and metafields planned for diamond jewellery
Shinelabb's store at shinelabb.com sells lab-grown diamond and moissanite pieces set in 925 sterling silver or gold vermeil, all made to order. It is a separate build from the Shinelabb product master and client-catalogue system listed above: this one is the brand's public, direct-to-customer storefront. Treating metal, metal colour, stone, carat and ring size as variants would have meant 864 variants per ring, and Shopify allows only three options per product. So only the three choices that change the price are variants (metal, stone and diamond size), which gives 12 per product. Metal colour, Indian ring size (4 to 27, each shown with its inside diameter in mm) and engraving travel with the order as cart line-item properties. Nineteen product metafield definitions hold the product data, including diamond shape, carat weight and setting style.
That metafield work is what makes the store shoppable by diamond shape: ten shape tiles on the homepage swap in a ring photo and link to a pre-filtered collection, every collection page has a shape bar, and the filter sidebar shows a stone thumbnail beside each shape. Six mega-menu panels (Rings, Earrings, Bracelets, Necklaces, Chain / Pendants and Gifts) are editable by the client in the theme editor, and the Rings panel lists nine ring styles with a preview photo that changes as you move down the list. Because every piece is made to order, variants are untracked and nothing shows "Sold out". Shinelabb owns its store; Yukti AI works on it as a collaborator.
Miswah Jewellery: a material-first catalogue, with collections created by script
For Miswah Jewellery, the catalogue is organised material first, by the stone in each piece. The Engagement Rings, Wedding Rings, Fine Jewelry and Gifts menus each open a mega menu with separate Lab Grown Diamond, Moissanite and Gemstone columns, plus Featured and Education columns. Behind it sit 77 collections and a 103-item menu across 15 mega-menu columns, created through the Shopify Admin API by a script instead of by hand. The script shows a dry run first, publishes each collection to the Online Store, and can rebuild the same structure on another store. Product tags decide which collections a product joins at import, and they also print the spec line on each product page (stone, cut, colour, carat and clarity, with the SKU beside it). The theme ships with 13 automated end-to-end checks for the cart, wishlist and search.
Read the Shinelabb Shopify store case study and the Miswah Jewellery Shopify case study for the full builds, or see how Yukti AI approaches Shopify store development for brands in Surat and across India. If you need both a store and a back-office system, both can be scoped in the same free workflow audit.
Want help applying this to your business?Send us your current setup on WhatsApp. Free workflow audit, reply the same day — in Hindi, Gujarati or English.
Get a free workflow auditSoftware for loose-diamond traders
A loose-diamond trading desk needs different software from a jewellery maker: one live stock book of certified stones, a separate price for each buyer, and holds that do not depend on a phone call. Yukti AI built exactly this for a Surat diamond export house, in about 7 days, on the firm's own daily stock list.
Before, the whole book went out once a day as one Excel file on WhatsApp. Every buyer got the same sheet, holds were agreed by phone with no expiry, and each buyer's price lived in someone's head. The stock list the platform was built on held 408 IGI-certified polished diamonds in 13 shapes, from 0.50 ct to 20.25 ct, in white D to H colours and fancy colours such as vivid pink, vivid blue and intense yellow.
What the platform does
- One live stock book. The daily Excel is imported, not retyped. Grade and fluorescence codes become plain grading fields, and a data-quality check flags duplicate certificate numbers, stones without media, missing cut grades and out-of-range depth or table figures before any buyer sees the change.
- A private portal and price per buyer. Each client has a tier and a markup, the base rate is removed from the data a client receives, and visibility rules can hide chosen shapes or cap the carat weight for a particular buyer.
- Holds that run themselves. A buyer requests a 2, 4, 12 or 24-hour hold, the price locks, the desk approves, and a lapsed hold goes back to the book on its own. Only one live hold is allowed per stone, and every change is kept in an audit trail.
- Search in trade shorthand. A query such as "1.5 thi 2 carat cushion D to F VS", Gujarati-English included, is read as shape, carat range, colour and clarity. When nothing matches, the search loosens one criterion and says which; it never shows a stone that is not in the book.
The platform has four roles (owner, admin, sales desk and client), and access is enforced in the data layer, not only in the menus. It runs on Next.js, React and TypeScript on Vercel, with connection points ready to connect Supabase, OpenAI, the WhatsApp Cloud API and n8n; hold confirmations and new-stock alerts are already composed as WhatsApp messages inside the platform. In this build Memo is a stone status, and a full memo-out and memo-return workflow with jangad slips can be added as a later phase.
Read the diamond trading platform case study for the full build, or see diamond software in Surat for stock, holds and trading systems built around how your desk works.
Built differently for each part of the trade
"Jewellery business" covers very different operations, and the system is shaped to yours:
- Manufacturers — the system centres on job work and karigars, the metal ledger, wastage, and order-to-delivery tracking through each bench stage.
- Wholesalers and traders — it centres on the design catalogue, WhatsApp catalogue sharing with live pricing, party-wise ledgers and stock across memo and outright sale.
- Diamond traders — parcel and single-stone inventory by 4C, certification, memo issue and return, and margin per parcel.
- Retail brands — a customer CRM with taste, occasions and purchase history, a WhatsApp enquiry bot, and GST billing with hallmark and certificate details on the invoice.
Whichever you are, the modules are built around your process — not a showroom template with your name on it. It can also grow into a full AI business management system as you add finance, HR and analytics.
Related systems and guides
AI Automation for Surat Jewellers
How Surat's diamond and jewellery businesses are automating enquiries, catalogues and follow-ups.
AI Business Management System
The full picture — CRM, ERP, billing and WhatsApp in one custom platform.
Custom ERP Software
The horizontal version — inventory, orders, production and billing for any trade.
Guide: choosing jewellery ERP software
A checklist — metal ledgers, karat-wise stock, certification, job work — and when custom wins.
Shopify Store Development
Custom Shopify themes for jewellery and D2C brands: variants, filters, collections and payments planned for an Indian store.
Case study: Shinelabb Shopify store
Lab-grown diamond and moissanite jewellery: shop by shape, Indian ring sizes, engraving, and 12 variants per product instead of 864.
Case study: Miswah Jewellery
A material-first mega menu and 77 collections created by script, on a custom Shopify theme built on Dawn.
Diamond Software in Surat
A live stock book from your daily Excel, a price per buyer, holds that expire on their own and search in trade shorthand.
Case study: diamond trading platform
Built for a Surat diamond export house: one live stock book, private buyer portals and timed holds on 408 IGI-certified stones.
Case study: diamond assorting ERP
P. Hitesh & Co., Surat: diamond inventory management, stock custody, assorting with lot traceability, payroll and accounts.
Case study: diamond trading ERP
Arham Exports, Mumbai: lot-wise diamond inventory management, ageing, broker scorecards, CRM and an AI copilot.
What is jewellery software? The five types explained
Jewellery software is a business application built for the way jewellery is bought, made and sold: it tracks metal by weight and purity, stones by their specifications, pieces by tag, and parties by ledger. In India it falls into five types — retail billing, manufacturing ERP, wholesale, diamond and loose-stone stock, and online catalogue or store software — and most businesses need a mix of two or three.
The phrase “jewellery software” is used for very different products, which is why two vendors can both claim to be the best and still be unusable for each other’s customers. A showroom that sells finished gold ornaments over a counter and a Varachha workshop that issues gold to twenty karigars every morning are both “jewellery businesses”, but their software problems have almost nothing in common. Knowing which of the five types you are shopping for is the first step to a useful demo.
| Type | Who it is for | What it is built around | Typical gaps if you pick the wrong type |
|---|---|---|---|
| Retail billing software | Showrooms and counters selling finished ornaments | Tag-wise stock, daily rate billing, old-gold exchange, customer dues | Weak on karigar job work, raw-metal ledgers and bulk catalogue selling |
| Manufacturing ERP | Workshops and factories that make to order or to stock | Metal issue and receipt, job cards, wastage, bench stages, order-to-delivery | Overbuilt if you only buy and resell; billing may be an afterthought |
| Wholesale software | Traders and wholesalers selling to retailers | Design catalogue, party ledgers, memo and approval, rate-linked quotes | Often thin on production and on single-piece retail tagging |
| Diamond and loose-stone stock | Diamond traders, assorters, lab-grown suppliers | Stone-by-stone or lot-wise stock, 4Cs, certificates, holds, buyer-wise pricing | Metal-centred packages do not model parcels, lots or holds |
| Online catalogue and store software | Brands selling on WhatsApp or through a website | Product master, live pricing, shareable catalogues, variants, filters | Not connected to stock and ledgers, so sold-out designs get sent |
Most readers of this page sit across two types. A Surat manufacturer that also sells to wholesalers needs manufacturing ERP plus wholesale selling; a growing brand needs a product master, a catalogue and an online store. That overlap is the practical argument for a custom ERP built in Surat around your own mix, instead of paying for the full feature list of a package that is strong in only one type.
If you are still deciding whether you need an ERP or simply a better CRM, the guide on ERP vs CRM: what a growing business needs first walks through the order in which most owners adopt them.
Jewellery software features by business type: manufacturer, wholesaler, retailer, online brand
A manufacturer needs a metal ledger, karigar job work and wastage control above everything else. A wholesaler needs a live-priced design catalogue, party ledgers and memo tracking. A retailer needs tag-wise stock, daily-rate billing and customer history. An online brand needs a product master, clean variants and a catalogue that re-prices itself. The table marks which module is essential, useful or optional for each.
Use this as a scoring sheet. Mark each row against your own business before you talk to any vendor, including us. Anything marked “Essential” for your type should be shown live, on your own data, during the demo.
| Module | Manufacturer | Wholesaler | Retailer | Online brand |
|---|---|---|---|---|
| Metal ledger by karat | Essential | Useful | Useful | Optional |
| Karigar issue and receipt | Essential | Optional | Optional | Optional |
| Wastage and loss control | Essential | Optional | Optional | Optional |
| Stone and diamond register | Essential | Useful | Useful | Useful |
| Tag, barcode or QR per piece | Useful | Useful | Essential | Useful |
| Design master with photos | Essential | Essential | Useful | Essential |
| Rate-linked pricing rules | Useful | Essential | Essential | Essential |
| WhatsApp catalogue sharing | Useful | Essential | Useful | Essential |
| Memo and approval tracking | Useful | Essential | Optional | Optional |
| Party ledger and outstanding | Essential | Essential | Useful | Optional |
| GST invoice with HSN | Essential | Essential | Essential | Essential |
| HUID on hallmarked articles | Useful | Essential | Essential | Useful |
| Old-gold exchange | Optional | Optional | Essential | Optional |
| Customer CRM and follow-ups | Useful | Useful | Essential | Essential |
| Order-to-delivery tracking | Essential | Useful | Useful | Essential |
| Multi-branch or multi-location stock | Useful | Useful | Useful | Optional |
| Role-based access and audit trail | Essential | Essential | Essential | Essential |
| Owner dashboard and daily briefing | Useful | Useful | Useful | Useful |
Notice how little overlap there is between the “Essential” columns. That is the reason the jewellery ERP buying checklist asks each vendor to demonstrate the module on your own numbers rather than show a feature list. For the manufacturing side in particular, the general manufacturing ERP page explains how job cards and bench stages are modelled.
The metal and stone ledger explained: gross, net and fine weight, karat and wastage
A metal ledger records every gram of gold or silver that enters, leaves or sits with someone, expressed in fine weight so that 22 karat and 18 karat balances can be added. Gross weight includes stones and other non-metal parts, net weight is the metal alone, and fine weight is net weight multiplied by purity. Wastage and labour are separate charges layered on top.
Ask five jewellers how they calculate a bill and you may get five slightly different answers, because the vocabulary of the trade is local and sometimes personal. A good system does not impose one method; it lets you define your rules once and then applies them consistently. The concepts below are general trade practice, not a promise about any particular software.
Gross, net and fine weight
- Gross weight is what the piece weighs on the scale, including stones, pearls, enamel or other attachments.
- Net weight is gross weight minus the weight of stones and non-metal parts — the metal alone.
- Fine weight is net weight multiplied by the purity as a fraction. It is the pure-gold equivalent and the only number that lets different purities be added together.
Karat and purity
Karat expresses purity out of 24. Twenty-four karat is pure gold; 22 karat is 22/24, about 91.6 percent (often written 916); 18 karat is 75 percent (750); 14 karat is 58.5 percent (585). A ledger that stores weight but not karat cannot tell you how much pure gold you are actually holding, which is why the live metal and stone ledger on this page keeps balances karat-wise.
| Item | Example figure | How it is derived |
|---|---|---|
| Gross weight | 10.00 g | Read from the scale with stones in place |
| Stone weight | 0.80 g | Total weight of stones, converted from carats where needed |
| Net weight | 9.20 g | Gross minus stone weight |
| Purity (18 karat) | 75% | 18 divided by 24 |
| Fine weight | 6.90 g | Net weight times purity |
The figures above are an arithmetic illustration of the method, not data from any client.
Wastage, labour and loss
The word “wastage” is used in two senses and a system should keep them apart. Wastage charged is an allowance, usually a percentage of net weight, added to what the customer or party pays for. Process loss is the metal actually lost between issue and receipt at the bench: filing, polishing, melting. The first is a pricing rule; the second is a control number. Comparing process loss per karigar, per process and per month is how a manufacturer finds where metal leaks.
Labour or making charge is the charge for the work, quoted per gram, per piece or as a percentage of metal value depending on the trade and the party. Stone setting, polishing and rhodium plating are often priced separately. Because quoting habits differ by party, a flexible rule engine matters more than a long list of fixed fields.
For how a ledger of this kind appears in a working system, see the Lumera jewellery ERP case study, where gold balances are kept by purity for each vendor and karigar.
Karigar job-work workflow, step by step
Karigar job work is the process of issuing metal and stones to an artisan or workshop, tracking the job through each bench stage and receiving finished pieces back against the original weight. The software’s job is to make sure that what went out is accounted for when it comes back, in pieces, in fine weight and in time.
Create the job from an order or design
A job card links the customer order or stock design, the expected weight, the karat and the due date. Everything issued afterwards hangs off this one number.
Issue metal and stones
Gold, silver and stones leave the vault against the job and the karigar’s account. The metal balance of that karigar rises immediately, by karat.
Track the bench stages
Casting, filing, setting, polishing and plating each get a status. A piece that has sat in one stage too long becomes visible without anybody asking.
Receive finished pieces
Weigh each finished piece, record net weight and stones set, and close the job. The system compares what was issued with what came back.
Settle wastage, scrap and labour
Scrap and filings returned are credited; process loss against the agreed allowance is shown; the labour amount is calculated by your rule and posted to the karigar’s account.
Quality check and stock-in
Pieces pass inspection, receive a tag or barcode and enter finished stock, ready to be sold, sent on memo or added to a catalogue.
Two reports matter most here: the karigar balance (metal still outstanding with each artisan, by karat) and the pending-jobs report (what is overdue and with whom). Built in a client system: a vendor and karigar gold ledger by purity, with issue, consumption and return linked to orders (see the Lumera case study). Can be built: job cards with bench-stage status, process loss against an allowance, per-stage wages and a quality-check step; these are scoped in the free workflow audit; the manufacturing ERP page shows how job cards are modelled for other trades.
Memo, approval and outright sale: how each should be recorded
An outright sale transfers ownership and creates a GST invoice at once. A memo, also called approval or jangad in the trade, hands goods to a party for viewing while ownership stays with you; the goods remain your stock, sit against the party, and must later be returned or converted into a sale. Software has to keep these two flows separate, or stock and receivables both go wrong.
| Question | Outright sale | Memo or approval |
|---|---|---|
| Who owns the goods? | The buyer, from the invoice | You, until the party confirms |
| Does stock reduce? | Yes, immediately | It moves to “out for approval” against the party |
| Is a GST invoice raised? | Usually a tax invoice at sale | Typically a delivery challan or similar movement document rather than a tax invoice; confirm the exact rules with your CA |
| What closes it? | Payment of the invoice | Return of the piece or conversion to a sale |
| What to watch | Outstanding and ageing | Pieces out too long, parties with the most goods outstanding |
What a good memo register shows
- Every piece or parcel out, with party, date and the number of days it has been out.
- One-click conversion of a memo line into a sale at the agreed rate, with the remaining lines staying open.
- A return entry that puts the piece back into stock with its original tag.
- A party-wise summary of memo value outstanding next to that party’s invoice outstanding.
This is general guidance. In the diamond trading platform built for a Surat export house, Memo is a stone status; a full memo-out and memo-return workflow with jangad slips is not included and can be added as a later phase, as the diamond trading platform case study states. A party-wise memo register of the kind described above can be built. For the loose-stone side of memo, see diamond software in Surat.
Jewellery catalogue and WhatsApp selling workflow
A workflow that suits a wholesaler is: keep one product master, select designs for a buyer, let pricing rules calculate each price from the current metal rate, share the result as a link or PDF on WhatsApp, then see which designs the buyer opened or liked. Each step that is manual in a PDF process is an opportunity for a stale price or a lost lead.
The six steps
- Maintain the product master. Every design with SKU, collection, photos, weights, stone details, making charge and stock status, entered once.
- Select designs for the buyer. Pick a bridal set, a 22 karat light-weight range or a new arrivals list.
- Apply the pricing rule. Metal rate, making charge and margin are applied by the system, not typed by a salesperson.
- Share on WhatsApp. A branded PDF or a link, sent in a few taps from the same screen.
- Watch the response. Opens, likes and order requests tell you where to follow up.
- Convert to an order. The chosen designs become an order and then a job or a sale in the same system.
Why PDF-by-hand fails
A catalogue built in a design tool is frozen at the moment it was made. When the gold rate moves, every price in the file is wrong, and nobody can tell which version a buyer is holding. Selling a design that is already sold, or one that went to a different party on memo, damages credibility with trade buyers.
Yukti AI built this workflow inside client systems. Shinelabb has a product master that prices every design from the current gold rate, a no-login catalogue link and a branded PDF built from the same selection, with analytics on opens, likes and buys. Surati Jewellery Factory has the two-way WhatsApp inbox, where the customer conversation, record and quotation sit together. For the broader WhatsApp picture, the WhatsApp automation page and the WhatsApp Business API pricing guide for India explain what the channel can and cannot do.
Pricing rules and daily rate handling in jewellery software
Jewellery prices are a formula, not a fixed number: metal weight times the day’s rate, plus stone value, plus making charge, plus any wastage allowance, then tax. Good software stores the formula and the rate separately, so that when the rate changes every quote, catalogue and invoice that uses it recalculates instead of being retyped.
The rate is the most volatile input in the business. If it is typed into a billing screen or a PDF, it will eventually be wrong somewhere. The design questions worth asking are about who sets the rate, how often, and what happens to documents created before the change.
A typical price build-up
| Component | How it is usually calculated | Rule the software should let you set |
|---|---|---|
| Metal value | Net weight (or fine weight) times metal rate for the purity | Which rate applies, and who may change it |
| Wastage allowance | Percentage of net weight, or a fixed gram figure | Default by category, override by party |
| Stone value | Per carat, per piece or lump sum | Separate lines for diamonds, coloured stones and other stones |
| Making charge | Per gram, per piece or a percentage of metal value | By design family, by party tier, by order size |
| Discount or margin | Flat amount or percentage | Role-limited, so salespeople cannot go below a floor |
| Tax | Applied by HSN and nature of supply | Maintained centrally and kept visible on the invoice |
Questions to settle before you build or buy
- Is the rate entered by a person once or twice a day, or pulled from a feed you trust?
- Does a quote lock the rate for a stated period, and how is that shown to the customer?
- Should a catalogue shared last week show last week’s price or today’s? Wholesale buyers and retail customers expect different things.
- Who is allowed to see cost and margin? Pricing logic and the roles that can read it should be designed together.
Shinelabb’s catalogue system prices every design from the current gold rate so shared links reflect rate changes automatically; read how it was built in the Shinelabb catalogue case study. Pricing logic of this kind is a major reason owners choose a custom ERP over a fixed package.
GST, HSN, invoicing and hallmarking (HUID) in jewellery software: what to know
Jewellery software must produce GST invoices that show the correct HSN code, the taxable value split into metal, stones and charges, and, for hallmarked gold articles, the hallmark details. Hallmarking is a purity certification for gold and, more recently, silver articles, carried out at BIS-recognised assaying and hallmarking centres, and each hallmarked article carries a unique HUID under the Bureau of Indian Standards scheme. This is general information only; confirm current rules and rates with your chartered accountant.
Rules and rates change, and your own position depends on turnover, registration and the nature of your supply, so this section deliberately explains concepts instead of quoting a rulebook. Treat it as a list of questions to put to your CA and to any software vendor.
GST on jewellery: the concepts
- Rate by supply. Gold and silver jewellery, diamonds and job work on jewellery have historically been taxed at different rates. Software should let each line carry the correct rate rather than apply one rate to the whole bill.
- HSN codes. Articles of jewellery, precious stones and precious metals sit under different HSN headings. The master should store an HSN per item category.
- Invoice breakup. Showing metal value, stone value and making charge on separate lines makes the bill easier to audit and to explain to customers.
- Job work. Metal issued to a karigar for job work and the labour charged back raise their own documentation questions. Ask your CA how your flows should be treated before configuring them.
- E-invoicing and e-way bills. Whether they apply depends on turnover and on the movement of goods. Ask whether the system can produce the required data and whether a connection to the government portal is built or planned.
Hallmarking and HUID basics
Hallmarking is a purity certification for gold articles, carried out at BIS-recognised assaying and hallmarking centres. Hallmarked articles carry a mark showing the BIS logo, the purity grade and a HUID, a unique six-character alphanumeric identification. Many jewellers record the HUID against the tagged piece in stock and print it on the invoice so a customer can verify the item later.
What a jewellery system can reasonably do around this: store HUID per piece or per tag, block sale of a piece that lacks a required HUID if you choose that control, print it on the invoice, and report stock by hallmarked and unhallmarked status. Whether your business must hallmark a particular article, and by when, is a legal question for your CA or the relevant BIS guidance.
Other compliance points that affect software design
Cash receipt limits and customer identification requirements can also apply to jewellery sales. A system can capture PAN or other identity details on the invoice where you decide to collect them and can flag a cash total above a threshold you configure. The threshold itself, and what to do when it is crossed, should come from your accountant.
Yukti AI built GST invoice PDFs generated straight from the order, with diamond value, metal value and making charges itemised, for Lumera. Printing a HUID on the invoice is a field that can be added; it is not described in any published case study. If your accountant wants to keep Tally, see Tally integration with a custom ERP.
Jewellery inventory, tags, barcodes and stock audits
Jewellery inventory is tracked at three levels: raw material by weight and purity, semi-finished work inside jobs, and finished pieces by individual tag. A barcode or QR tag on each finished piece lets staff pull its full specification at the counter, run a stock audit by scanning, and know instantly what is in the showcase, in the vault, on memo or with a karigar.
The three layers of jewellery stock
| Layer | Unit of count | Typical location | Main risk |
|---|---|---|---|
| Raw material | Weight by karat or by grade; stones by carat or piece | Vault, vendor, karigar | Balances that do not tally across parties |
| Work in progress | Job card with weights issued and stage | Bench, polishing, setting, plating | Jobs that sit too long; unrecorded loss |
| Finished goods | Individual tagged piece | Showcase, safe, branch, on memo | Pieces missing at audit; duplicate sales |
Tag and barcode basics
A tag typically carries the design code, gross and net weight, karat and a barcode or QR code. Scanning it at billing can fill in the item, weight and price (and the HUID, where you store one), so the bill cannot disagree with the tag. Printing needs a label printer and a layout that matches your tag size; confirm this early because tag formats are often fixed by existing printers.
A stock audit in practice
- Freeze movements for the area being counted, or note the time of the count.
- Scan every piece physically present into an audit session.
- Compare the scanned list with the system list for that location.
- Review the differences: missing, extra and wrongly located pieces.
- Resolve each difference with a reason, and keep the audit record.
Per-piece barcode and QR tags and multi-location inventory were part of the Lumera build; see the Lumera case study. For diamond parcels, where the unit is a lot rather than a tag, the P. Hitesh diamond assorting ERP and the Arham Exports diamond trading ERP show lot-wise stock and ageing.
Old-gold exchange, gold savings schemes and repairs: what retail jewellers expect
Retail jewellers often need three workflows that manufacturers rarely do: taking back old gold against a new purchase, running a monthly gold savings scheme, and handling customer repairs. Each touches money, stock and the customer record together, so a software system should treat them as proper modules and not as notes in the margin of a bill.
Old-gold exchange
The customer brings old ornaments; the jeweller tests purity, deducts melting loss or an agreed percentage, and credits the value against the new bill. Software should record the weight, the tested purity, the rate used and the deduction on the same invoice, then send the received metal into raw stock or scrap so the metal ledger stays right.
Gold savings schemes
A scheme collects monthly instalments from a customer and redeems them against a purchase at the end. The software needs enrolment, an instalment calendar, receipts, reminders and a clean redemption entry. Because customers pay in advance, scheme money also needs careful treatment in the accounts; confirm the rules with your CA.
Repairs and custom orders
A repair takes in a customer’s own piece, which is never your stock. It needs a receipt, a due date, a karigar assignment and a delivery step. Custom orders add design approval and advance payments.
Honest status: Yukti AI’s published jewellery builds centre on manufacturers, wholesalers, brands and diamond traders. Old-gold exchange, gold savings schemes and a repairs desk are can be built modules if you run a retail showroom; they are not described as delivered in any case study on this site. If these matter to you, raise them in the free workflow audit and compare them with ready-made retail packages before you decide. The custom ERP vs off-the-shelf ERP comparison helps with that decision.
Jewellery software in Surat: why the local trade needs a different shape of system
Surat is best known as a centre for cutting and polishing diamonds, and its jewellery trade has grown beside that industry. Many local businesses sit between diamonds, lab-grown stones, gold and silver manufacturing and wholesale supply to retailers elsewhere. That mix favours software that handles stones and metal together and sells by catalogue and WhatsApp, not only over a showroom counter.
Several features of the local trade shape what software should do:
- Many small and mid-size workshops. Owner-run units with a handful of karigars need something fast to adopt, with screens in plain language and often a mix of Gujarati, Hindi and English.
- Trade by relationship and WhatsApp. Orders, photos and approvals travel by message. Systems that cannot take part in that conversation are used less.
- Stones and metal in one product. Natural diamonds, lab-grown diamonds, moissanite and coloured stones each need their own grading fields next to gold weight and karat.
- Parties in several cities. Wholesalers sell to retailers in other states, so party-wise ledgers, state-wise GST and outstation shipments matter.
- Seasonal and festive peaks. Wedding and festival demand makes order tracking and karigar capacity visible problems.
Yukti AI is based at 220, Leonard Square, Yogichowk, Varachha, Surat, and works with jewellery and diamond businesses across India. Surat builds on this site include a CRM for a jewellery factory, a catalogue and product master for a diamond wholesaler, and a private trading platform for a diamond export house. See also the guide on AI automation for Surat diamond and jewellery businesses and, for the diamond side of the trade, diamond software in Surat.
18 questions to ask any jewellery software vendor
Choose jewellery software by asking each vendor to show your own workflow on your own data, then score them on the same questions. The eighteen below cover fit, data, compliance, cost, support and exit. If a vendor cannot answer a question plainly or avoids a live demonstration, treat that as an answer.
Fit
- Which of the five types (retail, manufacturing, wholesale, diamond stock, online catalogue) is the product built around?
- Can you show karat-wise metal balances for one karigar, issued, returned and outstanding?
- Can pricing rules reflect my making-charge and wastage habits without manual edits on each bill?
- How are stones modelled: shape, carat, colour, clarity, certificate, natural versus lab-grown?
- How are memo, approval and return handled, and how do they show on the party ledger?
- Can I send a rate-linked catalogue on WhatsApp from inside the system?
Data and control
- Who owns my data, and can I export all of it in a standard format at any time?
- How will my existing Excel and Tally data be brought in, and who checks the opening balances?
- Which roles exist, and can a salesperson be blocked from seeing cost and profit?
- Is there an audit trail showing who changed a weight, a rate or an invoice?
- Where is data hosted, and how are backups taken and tested?
Compliance
- How does the invoice handle HSN, tax by line, HUID and the metal, stone and labour breakup?
- What happens when tax rules or invoice formats change, and is that update included?
Cost and support
- What is the total cost over three years including setup, training, per-user fees and upgrades?
- What does support cover, in which languages and at what hours?
- How long from signing to the first live day for a business like mine?
Exit and growth
- Can the system grow to add a branch, a store or a new module without starting again?
- If I leave, what do I take with me and in what format?
The shorter eight-row version is in what to look for in jewellery ERP software. If you are also weighing cost, custom ERP software cost in India breaks down what moves a price.
Build, buy or integrate? A decision framework for jewellery businesses
Buy a ready-made package if your process is a standard retail counter. Build a custom system if you have a metal ledger, job work, a large design catalogue or a wholesale model that a package fights. Integrate when parts of your stack, such as Tally for accounts, already work and only need to connect to the stock and selling side.
| Option | Best when | Watch out for |
|---|---|---|
| Buy a ready-made package | Your process is common, your team is small, and you want to start this week | Features you may not use, possible workflow compromises, recurring fees where the model is a subscription, and limits on changing screens |
| Build custom | Your workflow is distinctive, spans metal, stones, catalogue and CRM, or must connect to WhatsApp and AI | Needs a clear scope, a reliable builder, and an owner who can decide on rules |
| Integrate existing tools | Accounts in Tally work well; you need stock and selling to talk to them | Two sources of truth if the boundary is vague; agree which system owns which record |
| Hybrid: package plus custom add-ons | A package covers billing, but catalogue or CRM is missing | Data duplication between package and add-on |
Five questions that decide it
- Does a demo of a package on my real karigar and catalogue flow succeed, or do I need workarounds?
- Will I outgrow the package in three years, for example through a second branch or an online channel?
- Do I need WhatsApp-first selling and an AI layer that a package does not offer?
- Is my accountant attached to Tally and unwilling to move?
- Do I prefer a one-time build or a recurring licence?
Yukti AI builds custom systems and integrations, and says plainly that a plain retail counter may be well served by a package. See AI ERP for how an intelligence layer sits on top of the same data, and the business management system page for how a first module grows into a full platform.
Moving a jewellery business from Excel, registers and Tally to one system: data migration steps
Migration succeeds when you move clean, agreed opening balances and a small set of masters, not every historical row. The usual order is: list your sources, clean the masters, load opening metal and stone balances, load parties and outstanding, test with a parallel run, then switch on a stated date. Old history stays in Excel or Tally for reference.
The eight steps
- List every source. Stock Excel files, the karigar register, the party ledger in Tally, the catalogue folder, WhatsApp contact lists.
- Decide what moves. Opening balances and live masters move; years of old vouchers usually do not.
- Clean the masters. Merge duplicate parties, standardise karat names, design codes and stone grades.
- Count and agree opening stock. Physical count of metal, stones and tagged pieces, signed off by the owner.
- Load and reconcile. Import into the new system and compare totals against the count and the books.
- Train by role. Billing staff, store keeper, production supervisor, owner — each practises on their own screens.
- Run in parallel for a short period. Enter the same transactions in the old and new systems and compare end-of-day totals.
- Cut over on a fixed date. Stop the old entries, keep the old files read-only.
What typically goes wrong
- Karats written five different ways in different sheets, so balances split.
- Opening metal balances that were never physically verified.
- Party names that differ between the sales register and Tally.
- No owner for the decision of what to leave behind.
Yukti AI’s practice is to build on a working version of your real process and include data setup in the build, then team training and twelve months of support. The diamond trading platform for a Surat export house imports the firm’s daily Excel stock list and runs a quality check for duplicate certificate numbers and missing media before any buyer sees the change. For the wider picture, read moving from Excel and Tally to one system and how to replace Excel and Tally.
Jewellery software implementation phases and timeline
A jewellery software project normally runs in five phases: workflow audit, scoped build on a working version, data setup, training and go-live, then support. At Yukti AI, focused builds typically take about 7–10 days and a multi-module ERP or CRM usually takes a few weeks, depending on scope. The timeline depends most on how quickly decisions and data arrive.
| Phase | What happens | What we need from you |
|---|---|---|
| 1. Free workflow audit | A 30-minute walk through stock, ledger, catalogue and billing; the right modules are scoped | Samples of your Excel files, a bill, a catalogue and your karigar register |
| 2. Build on a working version | The modules are built on your real process so you can react to screens, not paper | Quick answers on rules such as wastage, making charge and roles |
| 3. Data setup | Masters and opening balances loaded and reconciled | A signed-off stock count and party list |
| 4. Training and go-live | Each role is trained; a cutover date is fixed | Staff time, and a named person to lead adoption |
| 5. Support and refinement | Twelve months of support included; small annual maintenance afterwards | Feedback from the first weeks of real use |
Anything that adds scope, such as a connection to an outside portal, a hardware device or a new module, is discussed and quoted separately before work starts. Pricing for a full multi-module ERP or CRM starts from ₹30,000, with the final quote given after the free workflow audit. Shopify store projects start from ₹60,000. The custom ERP cost guide explains what moves a quote.
Roles, permissions and audit trail in jewellery software
Jewellery is a business of high-value, small items, so software must control who can see cost, change a weight or edit a posted bill. Roles give each person only the screens and numbers they need, and an audit trail records who changed what and when. Together they protect the business from both honest mistakes and deliberate tampering.
| Role | Should see | Should not see or do |
|---|---|---|
| Owner | Everything, including cost, margin and the metal position | Nothing hidden, but changes are still logged |
| Manager | Orders, stock, parties, reports | User management; possibly purchase cost |
| Sales | Catalogue, customer records, quotes | Cost price and profit |
| Production or store | Job cards, metal issue and receipt | Customer outstanding and pricing |
| Accounts | Invoices, payments, ledgers | Editing stock weights |
What an audit trail should capture
- Edits to weight, karat or rate on any posted record.
- Deleted or cancelled invoices and the reason given.
- Price overrides and discounts beyond a set limit.
- Logins, with the time and the user.
Role-based access with row-level security, and cost and profit visible only to admin and manager roles, are part of the Lumera build, as described in its case study. The Surati Jewellery Factory CRM has Owner, Manager and Staff roles, with row-level security across all 12 tables, and the Surat diamond trading platform has four roles with access enforced in the data layer, not only in the menus; see the Surati CRM case study and the diamond trading platform case study.
What AI can and cannot do inside jewellery software
AI inside jewellery software is useful when it reads your live stock, ledger and customer data and tells you what needs attention: a morning summary, an ageing flag, an answer to a customer’s first WhatsApp message. It does not replace weighing, counting or accounting. Below, every capability is labelled as built in a client system or as something that can be built.
| Capability | What it does | Status |
|---|---|---|
| Daily recommendations to the owner | Analysis runs on its own and the owner receives suggestions on what to act on | Built in a client system (Lumera) |
| WhatsApp first-reply assistant | Answers the opening enquiry from the live catalogue, defers on exact prices and stock, staff can switch it off for one chat | Built in a client system (Surati Jewellery Factory) |
| Rule-based owner copilot, daily brief and ageing insights for diamond lots | Answers from the ERP’s own numbers: lot ageing, fast and slow stock, and what needs attention | Built in a client system (Arham Exports); the case study states no measured results |
| Smart search in trade shorthand | Reads queries such as carat range, shape, colour and clarity, including Gujarati-English | Built in a client system (Surat diamond export house); runs as built-in logic on the stock book, with an AI-model connection point ready but not yet connected |
| Import data-quality check | Flags duplicate certificate numbers, missing media and out-of-range figures before buyers see them | Built in a client system (diamond trading platform); runs as built-in logic, with an AI-model connection point ready but not yet connected |
| Overdue karigar job alerts | Warns when a job has stayed in one stage too long | Can be built |
| Slow-moving design flags for jewellery stock | Surfaces designs that have not sold for a period you set | Can be built |
| Metal-loss anomaly flags | Highlights a karigar or process whose loss is unusual against the agreed allowance | Can be built |
| Customer re-engagement nudges | Reminds you of a buyer who has gone quiet or has an occasion coming up | Can be built |
The limits
- AI cannot replace a physical stock count or a purity test.
- Its answers are only as good as the data entered; weak masters produce weak flags.
- Exact prices and stock should come from the system itself, not from a language model guessing.
- Anything that sends a message to a customer should have a human override.
See AI ERP, AI CRM and how AI changes a CRM for the general approach.
Cloud, desktop, mobile and multi-branch jewellery software: which setup fits
Cloud software runs on remote servers and opens in a browser or app from any location; desktop software runs on a computer in your shop. Cloud suits owners who want live visibility across branches and phones, while desktop can suit a single shop with unreliable internet. Many jewellers choose cloud with careful backups, plus a plan for what staff do if the connection drops.
| Question | Cloud or web-based | Desktop or local server |
|---|---|---|
| Access from phone or home | Usually yes, with a login | Often limited or needs extra setup |
| Several branches in one stock view | Natural fit | Needs synchronisation |
| Works when internet is down | Depends on the design; ask what is possible offline | Yes, for local work |
| Backups | Handled by the host; ask how often and how restored | Your responsibility |
| Updates | Applied centrally | Installed on each machine |
Multi-branch questions
- Can each branch see only its stock while the owner sees all?
- How are transfers between branches recorded and acknowledged?
- Are party ledgers shared across branches?
- Can a branch manager approve a discount, and up to what limit?
Mobile
Owners value a phone view of today’s sales, stock position, pending jobs and receivables. Karigars and store keepers may prefer a very simple mobile screen to record issue and receipt. Ask any vendor to show the actual phone screens, not slides.
Yukti AI builds web-based systems with login by role, as in the Lumera system, which tracks stock separately by location. Offline operation is not claimed for any of these builds and would be scoped separately if you need it.
Ten common mistakes when buying jewellery software
The most common mistakes are choosing a software type that does not match your business, skipping a demo on your own data, ignoring migration, treating compliance as the vendor’s problem alone, and forgetting to train staff. Each can be avoided with a short checklist before signing and a firm cutover plan afterwards.
- Buying on the longest feature list. A package with a long feature list you do not use can hide the few modules you need.
- Accepting a slide demo. Insist on your own karigar flow and your own bill.
- Leaving opening balances unverified. A wrong start makes every later report doubtful.
- Not defining wastage and making-charge rules. The system cannot apply rules nobody wrote down.
- Giving every user every screen. Cost and margin should be role-protected from day one.
- Ignoring the catalogue. Many businesses sell mostly through WhatsApp, yet buy software that has no catalogue workflow.
- Forgetting the accountant. If Tally stays, decide the boundary early.
- Skipping training. A tool that staff avoid is worse than a spreadsheet.
- No exit plan. Know in what format your data would leave.
- Waiting for perfect. Start with the modules that remove the most daily pain and add others in phases.
The jewellery ERP buying guide covers the first five in more detail, and the article on business management systems shows how a first module can grow into a full platform.
Reports a jewellery owner should be able to see without asking anyone
An owner should be able to open a handful of reports at any time: the metal position by karat, outstanding with each karigar, stock by location and age, receivables by party, sales by design and salesperson, and memo out. If any of these requires a staff member to compile it by hand, the software is not yet doing its job.
| Report | Question it answers |
|---|---|
| Metal position by karat | How much gold and silver do I hold, owe and have outstanding? |
| Karigar balance and pending jobs | Who has my metal and which jobs are late? |
| Stock by location and ageing | What is sitting where, and for how long? |
| Party outstanding and ageing | Who owes me, and since when? |
| Memo out | Which goods are with which party and for how many days? |
| Sales by design and salesperson | What sells, and who sells it? |
| Catalogue activity | Which designs were opened or liked, and by whom? |
| Wastage and process loss | Where is metal being lost? |
An AI layer on top of an ERP can add a written summary of these numbers each morning, which is how a daily owner briefing is meant to work.
What decides the price of jewellery software in India
The price of jewellery software depends on the pricing model (licence, subscription or one-time build), the number of modules, users and branches, the amount of data to migrate, and any hardware or outside connections. At Yukti AI a full multi-module ERP or CRM starts from ₹30,000, and the final quote comes after a free workflow audit.
| Cost factor | Why it moves the price |
|---|---|
| Pricing model | Licence or subscription fees recur; a one-time build is paid once, then a small annual maintenance charge follows the first twelve months |
| Number of modules | Metal ledger, job work, catalogue, billing, CRM, WhatsApp and AI each add scope |
| Users and branches | Some ready-made packages charge per user or per branch; ask the vendor |
| Data migration | Clean masters are quick; years of untidy Excel are slower |
| Hardware | Label printers, scanners and scales are bought separately |
| Outside connections | Portals, payment gateways and WhatsApp API usage have their own terms |
| Training and support | Included for twelve months in a Yukti AI build |
We do not publish a rate card for custom work because the modules differ for every business; the audit exists so that the quote matches your scope. See custom ERP software cost in India, AI automation cost in India and, for online stores, Shopify store development in Surat.
Jewellery software glossary: 30 trade and software terms
This glossary defines the terms used when jewellery businesses and software vendors talk to each other, from karat and fine weight to HUID, memo and row-level security. Definitions describe general trade usage; individual businesses sometimes use a word slightly differently, so confirm meanings during the audit.
| Term | Meaning |
|---|---|
| Karat (k) | Purity of gold out of 24 parts; 22k is 22 parts gold in 24 |
| Fineness | Purity expressed per thousand, such as 916 or 750 |
| Gross weight | Total weight of a piece including stones and attachments |
| Net weight | Weight of the metal alone |
| Fine weight | Net weight multiplied by purity; the pure-metal equivalent |
| Tunch | Trade term for the tested purity of gold, especially old gold |
| Wastage | Allowance charged on weight, or the metal actually lost in making |
| Making charge | Charge for the work of making a piece, also called labour |
| Karigar | Artisan or workshop that makes or finishes jewellery |
| Job work | Making or finishing work done by a karigar on metal supplied to them |
| Issue and receipt | Metal going out to a karigar and finished pieces coming back |
| Metal ledger | Running account of metal given, received and held, by party and karat |
| Memo | Goods given on approval without a sale; also called approval or jangad |
| Jangad | Trade word, used in Gujarati and Hindi, for goods given on approval or consignment |
| Party | A customer, supplier or other account in the ledger |
| Tag | Label on a finished piece carrying code, weight and barcode |
| HUID | Hallmark Unique Identification, a unique code on a hallmarked article |
| Hallmark | Official purity mark applied at a recognised centre |
| BIS | Bureau of Indian Standards, the national standards body that runs hallmarking |
| HSN | Harmonised System of Nomenclature code used on GST invoices |
| 4Cs | Carat, colour, clarity and cut, the main grading factors for diamonds |
| Certificate | Grading report from a laboratory for a stone |
| Lab-grown diamond | A diamond created in a laboratory rather than mined |
| Moissanite | A gem-quality stone often used as a diamond alternative |
| Melee | Very small diamonds, usually sold by weight in lots |
| Lot or parcel | A group of stones bought or sold together |
| Product master | The central record of every design with its specifications and photos |
| SKU | Stock-keeping unit; the unique code for a design or item |
| Row-level security | A database feature that limits which records a user can read or change |
| Audit trail | A time-stamped record of who changed what |
What Yukti AI has built for jewellery and diamond businesses, in one place
These summaries restate what each case study already says. Open the case study for the full detail and for the limits of each build.
Lumera: ERP and CRM
Orders with diamond and gold detail, a vendor and karigar gold ledger by purity, multi-location inventory, barcode and QR tags, GST invoice PDFs and an online catalogue with analytics.
Surati Jewellery Factory: CRM
A two-way WhatsApp and Instagram inbox, an AI first reply grounded in the catalogue, a lead pipeline, quotations and invoicing.
Shinelabb: catalogue engine
A product master priced from the current gold rate, shareable catalogue links and PDFs, and analytics, serving two brands.
Shinelabb: Shopify store
A custom theme with shop-by-diamond-shape, Indian ring sizes and a variant plan that keeps each ring at 12 variants.
Miswah Jewellery: Shopify store
A material-first mega menu and 77 collections created by script on a custom theme.
Surat diamond export house: trading platform
One live stock book from a daily Excel list, a private portal and price per buyer, and holds that expire on their own.
P. Hitesh & Co.: assorting ERP
Diamond inventory, stock custody, assorting with lot traceability, payroll and accounts.
Arham Exports: trading ERP
Lot-wise diamond inventory, ageing, broker scorecards, CRM and an AI copilot.
Ready to plan your own system? Start with the free 30-minute workflow audit: send your current setup on WhatsApp at +91 95862 55455, or visit 220, Leonard Square, Yogichowk, Varachha, Surat - 395006. If you also sell online, read the Shopify jewellery store guide.
Questions, answered.
Summary
- Yukti AI, a software company at 220, Leonard Square, Yogichowk, Varachha, Surat, builds custom jewellery software for manufacturers, wholesalers, diamond traders and retail brands across India, covering diamond and gold inventory, a live metal ledger, karat-wise stock, job work, a WhatsApp catalogue, GST billing and a customer CRM.
- Yukti AI built a full ERP/CRM for Lumera, a diamond jewellery brand, with a live metal ledger, catalogue, inventory, barcodes and GST invoicing; the system now generates Lumera's customer invoices.
- Yukti AI built a CRM with a two-way WhatsApp inbox, a lead pipeline and invoicing for Surati Jewellery Factory, and a product master with WhatsApp catalogue generation for Shinelabb.
- Yukti AI built a custom Shopify theme on Dawn for Shinelabb, a lab-grown diamond and moissanite jewellery brand at shinelabb.com, keeping each ring at 12 variants instead of 864 by carrying metal colour, Indian ring size and engraving as cart line-item properties.
- Yukti AI built a custom Shopify theme for Miswah Jewellery (miswah.in) with a material-first mega menu, and created its 77 collections and 103-item menu by script through the Shopify Admin API.
- For a Surat diamond export house, Yukti AI built a private diamond trading platform in about 7 days that turns the daily Excel stock list of 408 IGI-certified polished diamonds into one live stock book, with a private portal and price for each buyer and holds that expire on their own.
- Every Yukti AI jewellery software project starts with a free workflow audit and is delivered as a one-time build that includes data setup, team training and twelve months of support.
Loose diamond stock and diamond ERP, not just a jewellery ledger
Jewellery businesses that buy loose diamonds often need more than a metal-and-stone ledger: lot-wise cost, custody of parcels, ageing of stock and a clean link to the accounts. Two diamond ERPs built by Yukti AI show the pattern: the P. Hitesh & Co. diamond assorting ERP for a house that sorts and moves parcels, and the Arham Exports diamond trading ERP for a trader that buys lots and sells them in parts.
Each case study includes a feature checklist for diamond inventory management software, the benefits that design is meant to deliver (no measured results are claimed) and an honest AI menu. For the jewellery side of the trade, see what to look for in jewellery ERP software.