Store profiles
Each branch with its own details.
Multi-branch Businesses
Give every jewellery branch its own store details without separate systems.
JewelleryOS 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.
The problem today
What gets lost in generic software.
Each branch keeps its own hours, services and catalogue copy.
Head office has no single view of store-level information.
Branch stock and order allocation is assumed, not proven.
Every branch needs its own details without a separate system.
What is this?
Multi-branch jewellery software keeps each store's profile, hours, holidays, facilities, services and appointments under one head office, sharing a common catalogue and price rules. Branch-linked stock and order allocation is a client-specific implementation, not an assumed default.
How it works
From record to real selling.
- 1
Set head-office catalogue and price rules once.
- 2
Give each branch its own profile and settings.
- 3
Manage hours, holidays, facilities and walk-in services per store.
- 4
Let customers book appointments at a chosen branch.
- 5
Scope branch-linked stock, orders and reports around your data model.
In practice
JewelleryOS is made for gold, diamond, gemstone, and multi-store jewellery businesses. Product fields, price rules, ring choices, customer records, and order work sit in one system instead of being forced into clothing-store software.
What you get
Built into multi-branch businesses.
Hours & holidays
Per-store timing and closures.
Facilities & services
Walk-in services shown per location.
Appointments
Customer appointment flow by branch.
Shared catalogue
One catalogue and price-rule approach.
Branch stock (scoped)
Branch-linked orders and stock, implemented and tested per client.
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
InventoryJewelleryOS 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.Orders & InvoicingJewelleryOS keeps the customer, order, product snapshot, selected options and item stages together. Because items in one jewellery order may take different paths, the order view shows each distinct item stage instead of forcing one misleading status onto the full order.Admin PanelThe JewelleryOS Admin Panel is the private workspace used to manage catalogue data, pricing records, ring options, customers, orders, stores, appointments, content, site controls and reports. Access is permission-based so each user sees the work relevant to their role.
FAQ
Questions jewellers ask.
Can each branch have its own hours?
Yes. Store profiles, hours, holidays and services are managed per branch.
Is stock allocated per branch today?
A full branch stock and order promise is published only after each order and stock record is tied to a store and tested.
Do branches share the catalogue?
Yes. One catalogue and price-rule approach is shared across branches.
Can customers book at a specific store?
Yes. Appointment flow can route to a chosen branch.
Can you add transfers and branch reports?
Transfers, branch stock, local prices, pickup and branch reports are scoped as custom work.
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.