Guided quality selection
Shoppers choose shape, carat weight, colour (D–M) and clarity (FL–I3), and the price updates for each as a fixed, percentage, or per-carat add-on that you control. It is a merchandising model, not a stone list.
Live diamond feeds: where we actually are.
This page is deliberately honest about status. Diamond inventory integration is the largest item on the Ring Facet roadmap and is not shipped yet. Here is what works today, what is being built, and what has already been decided.
What the builder does with diamonds today
Real geometry per shape
Each of the eight shapes is a distinct cut with its own facet geometry, rendered by the analytic facet engine — so an emerald reads like step cutting and a round reads like brilliant fire.
No inventory held
Ring Facet does not carry, own, or resell stones. Your supplier relationships, your margins, and your fulfilment stay entirely yours. That does not change when feeds ship.
What connecting a feed will change
Choosing a stone, not a grade
Instead of picking "1.2ct, G, VS1" as an abstraction, a shopper filters real available stones by shape, carat, colour, clarity, cut, and price, sees the certificate details, and sets that specific stone into the ring they have just configured — with the mounting and the stone priced together.
Your feed, your margin, your rules
Margin rules stay private and server-side. The storefront shows only stones you can actually sell. Feeds under evaluation include the formats the trade already runs on — supplier APIs and scheduled CSV exports both.
Each merchant authenticates with their own supplier account
This one is settled. Ring Facet will not sit as a master account with merchants underneath it. You connect your own supplier credentials from inside Ring Facet and keep your own pricing, permissions, and fulfilment relationship intact. It is the slower architecture to build and the only one that leaves you in control of your trading terms.
Saved builds have to survive inventory
A shared link naming a stone that sold yesterday is the failure mode every feed integration hits. The builder already repairs configurations that name components a merchant has removed, and stone availability will use the same mechanism rather than showing a shopper an error.
Software that oversells its roadmap costs you a launch.
Plenty of configurator vendors list inventory feeds as a shipped feature and produce a professional-services quote once you have signed. If live stone inventory is critical to your launch date, tell us before you buy and we will tell you honestly whether the timeline works. Everything else on the features page is running in production today.