Ruby Kinglet
Customizers
Three formats. Showcase, a traditional pre-rendered customizer. Builder, a full AI customizer that renders the shopper's exact piece. And Visualizer, a preview engine for a UI you already have. All three launch straight from your dashboard; Visualizer wires the preview into product pages you already have.

Live preview
Connect your store
Import your catalog once, the customizer renders against your real SKUs, and configured pieces add to cart with variant data so they check out like any other order. Inventory and pricing stay synced.

Three formats · pick one
Pre-rendered

Steps · preview · inspector
Pre-rendered images, swapped on click. Fast to launch, familiar to shoppers, zero AI required.
AI rendered

Set scope · 4 editors · 27 sections
Every choice generates a real render of that exact piece. The shopper sees their ring, not a stock photo.
Drop-in

Install snippet · publish · live
Already have a customization UI on your store? We wire our preview engine in behind it so shoppers see a live render of their exact piece.
Also included
On Shopify, a configured Showcase piece moves through the same cart and checkout as the rest of your catalog. Full variant data goes with it, so there is no separate payment flow, no manual order reconciliation, and nothing for the buyer to learn. Builder designs arrive as quote requests instead, with the shopper's exact design attached.
Configure the flow, brand the look, pick the format, and launch from your dashboard. No agency needed for Showcase or Builder. Built for Shopify; the embed works on any site where you can paste HTML, including Webflow, Wix, and Woo.
Today the customizers run on your photos and AI renders. Next: rendering swappable parts straight from your 3DM (settings, shanks, stones, prongs), so the geometry stays exact across every shopper combination. If you have CAD files, they will plug in when it ships.
Use cases
Storefronts using the customizer tools to ship configurators in days instead of months, without an outside integration team.
DTC jewelry brand on Shopify
The problem
Custom engagement rings drive most of the revenue, but the existing builder lives in a third-party app that does not match the brand and is hard to update.
What we do
Spin up a Builder customizer. Configure scopes for the four-prong, six-prong, and bezel options. Style it to match the rest of the catalog. Connect Shopify so requests carry real product data.
The outcome
A builder that matches the brand, renders the exact ring, and ships configured orders into Shopify cleanly.
Jewelry retailer running multiple storefronts
The problem
You sell the same SKU pool across Shopify, Wix, and Webflow stores. Maintaining three separate customizers is unsustainable.
What we do
Configure one customizer in Ruby Kinglet. Embed it across all three storefronts. Use the dashboard to manage options and branding once.
The outcome
One customizer to maintain, three storefronts updated in lockstep.
Bespoke studio with a custom site
The problem
You already invested in a customization UI on a custom-built site, but the previews are static images that do not match the actual piece.
What we do
We wire the Ruby Kinglet preview engine in behind your existing UI with you. Your front-end stays. The preview becomes a live render of the exact piece the shopper has configured.
The outcome
Existing UX preserved. Live, accurate previews behind it.
Retailer with a small option matrix
The problem
You want a customizer live by next week. The option matrix is small enough that AI renders per shopper are overkill.
What we do
Use Showcase. Pre-render every combination once. Launch the multi-step flow on Shopify with brand-matched imagery.
The outcome
A polished customizer live in days, with zero AI runtime cost.
FAQ
Pre-rendered vs AI-rendered jewelry customizer: which converts better?
+
Pre-rendered wins on speed and familiarity; AI-rendered wins on personalization at higher price points. A reasonable rule of thumb: below a few hundred dollars, shoppers are decisive enough that pre-rendered feels fast and is fine; for engagement and bespoke, the lift from "this is exactly my piece" justifies the extra render time. Many brands ship pre-rendered for fashion SKUs and AI for engagement and bespoke. (3D-rendered customizers driven off CAD are a third path, with their own tradeoffs. See the next question.)
How do 3D-rendered (CAD-driven) jewelry customizers compare to photoreal ones?
+
The strength of a 3D-rendered customizer is real-time response and geometric accuracy: every part of the piece is the actual CAD, so what the shopper sees is exactly what gets cast. The weakness is realism. 3D renders are obviously renders. Stones tend to look plastic, metal reads matte and flat, and the piece sits in a vacuum without the brilliance, dispersion, or shadow language a photo or a strong AI render carries. There is also a build-cost question: a real 3D customizer needs a properly authored parametric CAD (typically a custom Rhino project per piece with swappable parts, named layers, and clean topology), which is expensive and slow to produce and tends to lock you into the geometry you started with. For most jewelry, photoreal (AI or pre-rendered) tends to win, because shoppers evaluate sparkle and material as much as silhouette. The sweet spot for 3D is configurators where geometric precision matters more than aesthetic conviction: signet rings, engravable pieces, or builder UIs aimed at the design conversation rather than the final purchase.
Can a small jewelry brand ship a customizer without an agency?
+
Yes, and the answer changed in the last couple of years. Configure-and-launch tooling is now mature enough that a one-person shop can ship a working customizer in a week, work that used to mean a long agency engagement. The time now goes into brand fit (photos, styling, option scopes), not the integration.
How are jewelry shoppers actually using customizers in 2026?
+
They configure more and hesitate less. Live-render customizers in particular cut the gap between "I think I want this" and "this is exactly what I want", which is where most jewelry purchases historically died.
What is the conversion impact of full-custom previews vs static images?
+
One of the biggest variables in jewelry e-commerce conversion. A live preview of the shopper's exact piece converts meaningfully better than static photography, with the biggest gains in engagement and bespoke. The effect is smaller for fashion jewelry at lower price points, where shoppers are more decisive and care less about the exact piece.
How do jewelry customizers integrate with Shopify in practice?
+
The pattern that works is: products live in Shopify, the customizer lives outside (as an embed or app), and the configured piece flows back into the Shopify cart with full variant data. Driving a customizer entirely off Shopify variants hits a wall fast. Shopify raised the variant ceiling to 2,048 per product in October 2025, but it still allows only three options per product, and any real jewelry option matrix (stone × metal × setting × size) is four before you add engraving or ring size. Most serious jewelry storefronts pair Shopify with a dedicated customizer engine.
Should I have a customizer at all if I sell limited bespoke?
+
Yes, and the framing matters. A customizer for limited-bespoke is not there to take orders unattended; it is there to help a serious client pre-visualize and pre-commit before the consultation. The jewelers using it best treat it as a lead-qualification and design-direction tool, with the actual commercial work happening in the consult.
How do you keep a customizer inside what you can actually manufacture?
+
Scopes. Set rules at config time for what can and cannot be combined. Without scopes, customizers happily generate combinations you cannot make (incompatible stone size and setting type, prong styles that will not cast, etc.) and end up with shoppers expecting pieces you have to refuse to fulfill. Every modern jewelry customizer worth using exposes scope controls; if yours does not, it will burn you.
What's the difference between the three Ruby Kinglet customizer formats?
+
Showcase pre-renders every combination: fast, familiar, and AI-free at runtime. Builder renders each shopper's exact piece on demand and collects quote requests with the design attached. Visualizer sits behind an existing custom UI and provides the live preview. Pick based on option matrix size, brand fit, and how custom your front-end already is.
Do I need a developer or an agency to launch?
+
For Showcase and Builder, no. They are configured, branded, and connected from the Ruby Kinglet dashboard, and most teams launch without writing code. Visualizer reads your existing product page and drafts its own wiring; you review it, publish, and paste one snippet. For pieces assembled from many parts, like bead strands, you send your part images and page, and we connect the renderer and test it on your store. A few days to a week.
Can I use my existing CAD files in the customizer?
+
Not yet. Today the customizers run on your photos and AI renders. CAD-driven renders, with swappable parts straight from your 3DM so the geometry stays exact across combinations, are in development. If you have CAD files ready, they will plug in when it ships.
How fast can a customizer go live?
+
A Showcase customizer can launch in days. A Builder customizer typically takes a little longer, because option scopes need to be set up to match your manufacturing reality.
Configure, brand, and launch from one dashboard. No agency, no integration team, no quotes.