Let shoppers choose a real diamond, not a grade.
Most ring builders ask a shopper to pick “1.20ct, G, VS1” as an abstraction, then someone finds a stone that roughly matches. Ring Facet works the other way round: your actual inventory sits in the builder, so the shopper sets a specific certificated stone — its own stock number, cut grade and lab report — into the ring they just configured, and the ring is priced from that stone.
This is live today using your own stone list. Direct supplier API connections are still being built, and that distinction is spelled out below rather than buried.
How it works
Upload your stone list
Export inventory from your supplier or your own system as a CSV and upload it. Column names differ everywhere, so the importer reads your headers and maps them itself — stock number, shape, carat, colour, clarity, cut, polish, symmetry, fluorescence, measurements, lab and report number — then shows you the mapping to confirm before anything is saved.
Set your markup
You upload wholesale cost. Ring Facet applies your markup bands — a different percentage for a $700 stone than a $30,000 one — and shoppers only ever see the retail figure. Your cost never reaches the browser.
Shoppers pick a stone
The picker shows the stones you actually hold, sized on screen by carat weight, with colour, clarity, cut and the certificate number on each card. A shopper opens any stone for full specs and, where your data includes it, supplier photography, 360° video and a link to verify the report with GIA or IGI.
The ring prices itself
Mounting, setting, metal and the chosen stone are priced together and recalculated on the server before checkout — never trusted from the browser. The shopper adds the finished ring to your normal cart and pays through your normal checkout.
Re-upload whenever stock moves
Each upload replaces the previous list: sold stones disappear, prices update, new stones appear. Nothing to reconcile, and no way to accumulate duplicates.
Why it is worth doing
A specific stone is easier to buy than a grade
“G colour, VS1” is a decision a shopper has to research before they trust it. A named stone with a lab report, a photograph and a price is a decision they can make now. You are selling the thing rather than the specification.
Your markup, not a marketplace's
Ring Facet never carries, owns or resells stones, and takes no cut of the diamond. Your supplier relationships, your trade pricing and your margin stay entirely yours — the software only presents and prices them.
The ring on screen is the ring that ships
The mounting is rendered from real CAD geometry and the stone is one you can put your hands on. There is no gap between what was configured and what gets made.
No catalogue to build
You do not create a product per diamond, or maintain thousands of variants in your store. One upload replaces the whole list, and the sellable item is generated at checkout time.
What it does not do
Being clear about the edges is more useful to you than a longer feature list.
Direct supplier API connections
Live feeds from diamond marketplaces — where inventory refreshes itself rather than being uploaded — are in progress, not shipped. When they land, each merchant will authenticate with their own supplier account so trade pricing stays theirs. Until then, uploading your list is the supported path, and it is a genuine one.
Only shapes the builder can draw
The picker offers stones it can render honestly. Eight shapes are modelled with their own facet geometry; a stone the builder cannot draw is kept out rather than shown as a generic sparkle, because a configurator that misrepresents a diamond is worse than one that admits its limits.
We hold no stock
No consignment, no memo, no marketplace in the middle. If a stone sells across the counter, it leaves your next upload and the builder stops offering it.
Getting started
If you already have an inventory export, you are a few minutes from a working stone picker. If you are weighing this against a marketplace's own builder, ask us the awkward questions — where the margin goes, whose customer it is, and what happens to your data. We would rather answer those than win on a feature grid.
See the full roadmap → · How the ring builder works → · Pricing →