Sales reports
Revenue, orders, units, categories and times from orders.
Analytics
See what sold, what customers viewed, and where the journey stopped.
JewelleryOS separates sales records from customer behaviour reports. Sales reports use real orders, while storefront reports use tracked events such as visits, product views, cart actions, checkout starts and purchases. This distinction helps teams read each number in the right context.
The problem today
What gets lost in generic software.
Revenue and browsing activity are mixed into one report.
Product tables count repeated events as if they were separate buyers.
Missing tracking history appears as zero activity without a warning.
A number is only useful when you can see what it counts.
What is this?
Jewellery analytics in JewelleryOS reports sales from real orders and storefront behaviour from tracked events, kept apart so each is read in the right context. Rates are blank without a valid denominator, and coverage is shown when tracking starts after the report period.
How it works
From record to real selling.
- 1
Sales reports read from real orders, units, categories and times.
- 2
Storefront reports read from tracked visit and product events.
- 3
Conversion reports show where sessions stopped between visit and purchase.
- 4
Customer reports show who bought, returned or changed activity.
- 5
Each rate states its denominator and its tracking coverage.
What you get
Built into analytics.
Storefront reports
How visitors used the site in the selected period.
Product performance
Shown, opened, saved, carted, checked out or bought.
Conversion journey
Where sessions stopped between visit and purchase.
Customer reports
Who bought, returned or changed activity state.
Email queue report
What was sent, what failed and what led to an order.
Honest rates
A blank rate when there is no valid denominator, not a fake 0%.
Coverage shown
Tracking start is shown when data begins mid-period.
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
CRM & CustomersJewelleryOS CRM brings customer details, orders, item history, buying preferences and activity into one record. Teams can review what a customer bought and how recently they engaged before planning a relevant follow-up.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.Customer InsightsJewelleryOS brings customer history, product activity, sales, conversion steps and reminder outcomes together. Any AI summary links to its source report, date range and records, so a conclusion can be traced instead of trusted blindly.
FAQ
Questions jewellers ask.
What is the difference between sales and storefront reports?
Sales reports use real orders; storefront reports use tracked website events. They are kept separate on purpose.
When does tracking start?
Coverage is shown when behaviour data begins after the selected report period.
Why is a rate sometimes blank?
A rate is blank when there is no valid denominator, rather than being reported as 0%.
How are product impressions counted?
Journey stages are counted by distinct sessions, with raw events kept as supporting context.
Can reports be exported?
Reports can be exported for approved business use.
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.