Everything behind the counter, in one system.
Jewelry POS is the core of the platform: the till, the stock, the bench and the back office. Built around pieces that exist once, priced against a metal market that moves, and accountable enough to close the day cleanly.
14-day free trialNo credit card requiredCloud or on-premise
Every piece its own record
Gold by purity, silver
Role-scoped throughout
Same system either way
A jeweler's stock record has to carry more than a name and a price.
Generic retail software models a product with a quantity. That breaks the moment the piece is unique, the cost moves with the metal, and the customer asks what is actually in it. This is one record in Gemora 360.
Halo Solitaire · S/N 2291884
In stock · Case 3At the counter, however the customer wants to pay.
Individual, company or walk-in. Split the tender, take a trade-in against the same sale, put the balance on layaway, and hold the whole thing while the customer thinks about it.
- Split payment across card, cash and trade-in
- Trade-in valued against today's metal price
- Layaway with deposits and a running balance
- Quotes, holds, returns and voids with a reason
- Close register with session history per terminal
Sale 10-4471 · Adam R.
TenderStock that is described, not just counted.
Metals, gems and finished assemblies are separate kinds of record, because they behave differently. A stone can move between settings. A chain can be cut. A finished piece has a serial and a certificate.
- Categories, brands, collections and catalogues
- Supplier orders, incoming memo and vendor returns
- Store transfers with variances that must be explained
- Inventory counts, stock health and storage locations
Repairs and custom orders are work, not sales.
A resize, an appraisal and a bespoke commission all move through their own states. Customer-owned goods stay off your stock ledger while they sit in your safe — which is both an accounting question and an insurance one.
- Take-in receipt with condition noted at the counter
- Estimate, approval, bench, ready, collected
- Customer-owned goods held apart from owned stock
- Promise dates on the day's list, not in a diary
Bench · this week
14 openA day that closes, and a record that stands up.
End-of-day closing per terminal and per session, with the variance shown rather than absorbed. Invoices and credit notes in both directions, and a full audit trail of who changed what.
- End-of-day closing, session and transaction history
- Reports hub with scheduled end-of-day reports
- Incoming and outgoing invoices and credit notes
- UBL export for e-invoicing requirements
- Live monitoring across terminals and locations
End of day · 10 Sep 2026
BalancedRun it on our infrastructure, or on yours.
The same system either way. The choice is usually about network reliability, data residency, or an existing server you already maintain.
| Cloud | On-premise | |
|---|---|---|
| Hosting | Managed by us | Your server or in-store machine |
| Updates | Applied automatically | Scheduled with your IT |
| If the line drops | Counter continues on local cache, syncs on reconnect | Unaffected — it is already local |
| Backups | Managed, daily | Your policy and your hardware |
| Multi-location | Built in | Site-to-site link between stores |
| Data residency | Region of your choosing | Entirely on your premises |
| Suits | Most stores, and anyone who would rather not run a server | Stores with residency rules, poor connectivity, or existing IT |
The core stays the core. Capability arrives as modules.
Everything above is the POS. Anything beyond it attaches to the same records and the same login, priced separately, switched on from your account.
HRM Available
Staff records, shifts, attendance and payroll — attached to the people already clocking in at the counter.
View HRMFurther modules On the roadmap
New capability ships on the same terms. Nothing to migrate, and no second system to learn.
How modules workAsked by jewelers, before they switch.
If yours isn't here, ask us directly — a real answer beats a brochure.
Can it handle one-of-a-kind pieces without duplicate stock numbers?
Yes — that is the default rather than a workaround. Each piece is its own record with its own serial, attributes, cost basis and certificate. Nothing forces you to invent a SKU and set the quantity to one.
Does it price against the live metal market?
Gold by purity — 22KT, 18KT, 14KT, 10KT — and silver are tracked through the day, so cost and margin reflect the market rather than whatever the metal was worth when the piece was taken in.
How are customer-owned goods kept separate from stock?
Repairs, appraisals and custom commissions create work records, not stock records. A customer's ring sitting in your safe never appears in your inventory valuation, which keeps both the accounts and the insurance position honest.
Can we hold stock on memo or consignment?
Yes. Memo and consigned pieces are tracked distinctly from owned inventory, with the vendor attached, so you can see what you hold versus what you own at any point.
What happens to the inventory data we already have?
Migration is part of onboarding. Existing stock, customers and open repairs are imported and reconciled with you before you go live. Scope and timing are quoted per store, since the condition of the starting data varies enormously.
Can we run it on our own server?
Yes — on-premise is a supported deployment, not an exception. The comparison above sets out what changes. Cloud and on-premise run the same system.
Does it work across more than one shop?
Multi-location is built in: transfers between stores, variances that have to be explained, counts per location, and role-scoped access so a manager sees their store while an owner sees all of them.
Try it on your own stock.
Load a dozen real pieces, take a sale, run a repair through the bench, and close the register. That will tell you more than any feature list.