Finished products
Full jewellery products with their own fields.
Inventory
Track jewellery stock without reducing every piece to one plain SKU.
JewelleryOS stores structured records for jewellery products, variants, diamonds, gemstones, ring settings and related masters. This keeps important details such as purity, colour, shape, clarity, carat, component and vendor available to the teams that price and sell the item.
The problem today
What gets lost in generic software.
Stone grades and ring components disappear inside a product description.
The storefront lists an item without enough stock detail for staff to confirm it.
The same stone can be treated as separate stock when shown with different settings.
A jewellery record should keep the details that decide the price and the sale.
What is this?
Jewellery inventory in JewelleryOS covers four record types: finished jewellery products, product variants, loose diamonds or gemstones, and ring components. Each keeps its own structured fields so purity, grade, shape, carat, component and vendor stay usable.
How it works
From record to real selling.
- 1
Define catalogue masters and product categories.
- 2
Add products, variants, media and sellable fields.
- 3
Add loose stones, component records and vendor details where relevant.
- 4
Connect records to the storefront and ring flows.
- 5
Review availability and affected prices before accepting or fulfilling an order.
What you get
Built into inventory.
Product variants
Metal, purity, size and stone variants held separately.
Loose diamonds
Diamond records with shape, carat, colour and clarity.
Gemstone records
Gemstone type, quality and colour kept intact.
Ring components
Settings, heads and bands as reusable parts.
Vendor details
Source information for relevant stock.
Storefront link
Records connect to listings and ring flows.
Availability review
Confirm stock and affected prices before fulfilling.
Need a jewellery flow that is not listed here?
Jewellery businesses often have their own price rules, approval steps, supplier feeds, certificates, store processes, customer journeys, and reports. JewelleryOS can assess a custom requirement and build the agreed part around the existing platform.
1What job should the feature complete?
2Who uses it, and what may each role see or change?
3Which records and outside systems are involved?
4What result proves the feature works?
Explore what connects to it
E-commerce & OrdersJewelleryOS carries product, variant, stone, price, customer and order information from the online store into the admin. Each order item can move through its own work stage, which suits jewellery orders where resizing, making, cancellation, return and dispatch may differ by item.Ring BuilderJewelleryOS connects ring settings, head and band styles, compatible options, diamonds or gemstones, media and price records. The customer gets a guided choice, while your team controls which combinations are valid and sellable.Multi-branch BusinessesJewelleryOS manages store profiles, hours, holidays, facilities, walk-in services and appointments centrally, while sharing one catalogue and price-rule approach. Full branch-linked order and inventory allocation is scoped and tested per client before it is promised.
FAQ
Questions jewellers ask.
Can we track loose stones?
Yes. Loose diamonds and gemstones are their own record type with structured fields.
Are ring components supported?
Yes. Settings, heads and bands are held as reusable component records.
Do variants keep jewellery fields?
Yes. Metal, purity, size and stone variants are kept as structured data.
Can we record vendors?
Yes. Vendor details can be kept against relevant stock.
Is stock allocated per branch today?
Store-level stock is subject to your store and order data design, and is confirmed and tested before it is promised.
See JewelleryOS working with your own jewellery.
Bring a few products, your rate card, and the process you use today. We will show what is already covered and what would need to be built for you.