RetailPOS.AI
Jewellery shop — buyer guide

How to choose a POS for your jewellery shop.

Last reviewed 2026-05-26 · by the RetailPOS team

A jewellery POS is a different beast from a coffee or apparel POS, because every fine piece on the showroom tray is one-of-a-kind. Your 1ct solitaire is not the same as another 1ct solitaire — it has its own weight, metal, stone certificate, and history. If your POS treats them as interchangeable inventory units, you cannot answer the most basic insurance question: which exact piece did we sell, and where did it come from?

This guide is for independent jewellers — bespoke ateliers, family-owned shops, watch and stone specialists. It walks through the features that genuinely matter (per-piece tracking, repair workflows, valuation print-outs) and the ones that look impressive on a demo but rarely earn their keep.

What this industry actually needs from a POS

Per-piece tracking is the headline win

Every fine ring, every loose stone, every watch is a unique unit row — serial, weight, metal stamp, certificate. The till picks a specific unit at sale; returns flip the same unit back to the case; repairs reference the piece, not the SKU.

Certificate metadata travels with the unit

GIA / IGI / HRD certificate number, carat, cut, colour, clarity. Stored on the unit, not on a separate spreadsheet. The customer takes the printed certificate at sale; you take the digital record.

Repair tickets are a separate workflow

Sizing, polishing, stone reset, chain solder. Each is a service ticket attached to a specific unit. The bench tech sees which ring is in front of them, not just “ring size 7.”

Insurance valuations are part of the workflow

Customers ask for printed valuations every 2-3 years for insurance renewals. The valuation references the unit's serial + certificate; a $75 service line and a printed receipt with the metadata is the workflow.

Layaway is the norm for high-ticket purchases

$3K+ purchases routinely pay across 3-12 months. The POS has to keep the order open through the plan and only flip it to paid when the balance hits zero.

Hold-for-customer happens daily

Customer reserves a piece with a deposit; comes back next week to decide. The unit is taken off the floor but not yet sold. The status enum should support this; many POS systems just don't.

Trade-in / buyback is common

Customer brings in old gold to credit against a new piece. The POS should accept the trade-in as a value-line on the basket; tracks separately for tax and reporting.

Security audit trail matters

The audit log is genuinely insurance-grade. Every refund, every price change, every unit retirement should leave a tamper-evident line. If anyone in your team has access to back-of-house, this is your defence against accusations.

Must-have features

  • Per-piece serial tracking

    Every fine ring / necklace / earring set / watch / loose stone is its own variant_unit row. At sale, the cashier picks a specific unit; that exact unit leaves stock.

  • Unit metadata storage

    Weight, metal, stone details, certificate number — stored on the unit, not on a separate file. Reads back at refund, repair, valuation time.

  • Repair ticket workflow

    Service order tied to a unit ID. Status: intake → in-progress → ready → collected. The bench tech sees the specific piece, not the SKU.

  • Valuation as a service SKU

    $75 (or your price) service line. The receipt prints as a stamped valuation referencing the unit's serial + certificate.

  • Layaway / payment plans

    Create a plan with deposit + scheduled payments. Order stays open through the plan; only closes when the balance hits zero. Customer can pay any combination of cash / card across the plan.

  • Hold (reserved) status

    Take a piece off the floor for a customer without selling it. The unit shows as “reserved”; not available to other customers until the hold is released.

  • Tamper-evident audit log

    Every refund, price edit, unit retirement leaves a chained line. If a line is tampered with, the chain breaks and the system reports it. Insurance grade.

  • Fine vs fashion vertical split

    Fashion jewellery (CZ rings, brass earrings) should NOT be per-unit tracked — it's integer stock. The POS must support both modes side-by-side; flipping each variant individually.

  • Customer record with purchase history

    High-ticket repeats are common (anniversary gifts, milestone pieces). The customer's past pieces surface at the next visit so staff can recommend.

Nice-to-haves

  • +
    Goldsmith bench tablet

    A small iPad at the bench showing open repair tickets ordered by intake time. The tech bumps each ticket when ready.

  • +
    CAD / 3D drawing attachment per unit

    For bespoke commissions, attaching the CAD file (or photo) to the unit is useful at refund or repair time. Few POS systems support this; a notes-with-image hack works.

  • +
    Per-stylist commission

    The salesperson who closed the $5K ring gets a commission on the sale. The salon-pack pattern works as-is.

  • +
    Trade-in calculator

    Type the gold weight + purity, get a buyback value at the current spot. Stops the customer feeling fleeced; speeds the salesperson.

  • +
    Auction / consignment ledger

    Pieces brought in on consignment from a dealer: track who owns them, settle on sale. Reuses the boutique consignment pattern.

Buying traps to avoid

  • “Variants” instead of per-piece units

    Most retail POS systems offer “variants” (sizes, colours) but those are quantity-tracked groupings, not unique units. Asking the demo to show how a 1ct solitaire is distinguished from another 1ct solitaire usually breaks the salesperson.

  • Certificate metadata in a notes field

    Some POS systems will accept the certificate number in a free-text notes field. That is not the same as structured tracking — you cannot search by certificate, you cannot refund-by-certificate, you cannot prove to insurance the chain of custody. The metadata has to be a real column or row.

  • Layaway as a paid bolt-on

    Some specialty POS systems charge extra for layaway. If the platform's pricing has a “layaway add-on”, expect the workflow to be half-baked. Look for layaway shipped as core.

  • No backup workflow if the goldsmith is sick

    Repair tickets that only live on the bench's personal computer are a single point of failure. The POS should be the source of truth so any staff member can answer “where is my ring?” on the spot.

  • Encryption-at-rest as a marketing line, not a fact

    Given the value of the data (and the customer records), confirm the database is actually encrypted at rest. Ask for a confirmation in writing; most cloud POS providers are SOC2 audited, ask to see the report.

How to choose your jewellery shop POS

  1. 1
    List your fine inventory honestly

    Walk the floor. Count how many pieces are genuinely one-of-a-kind (every fine ring, watch, loose stone) vs fashion stock (CZ rings, brass earrings, costume pieces). The first number is what you need per-piece tracking for; the second number stays on integer stock.

  2. 2
    Confirm per-piece is real, not a notes field

    In the demo: ask the salesperson to show how the system distinguishes two physically distinct 1ct solitaires (same SKU). Watch closely. If the answer is “you put the certificate number in the notes,” the system fails the basic test.

  3. 3
    Test the cashier serial-pick flow

    Have the demo cashier scan a SKU for a piece with 3 units available. The till should show a list of 3 specific units (with serial / certificate snippets) so the cashier picks the one in hand. Two seconds, no menu drill-down.

  4. 4
    Walk through a repair ticket

    Customer brings a ring in for sizing. Demo: create a service ticket with sizing SKU + a free-text note referencing the unit ID. Confirm the bench-side view shows the open ticket with the unit's metadata at hand.

  5. 5
    Validate the layaway flow

    Demo creates a $3K order with $500 deposit + $500/month plan. Take the deposit through the normal tender flow. Confirm the order stays open. Take a second tender of $500 a month later. Confirm balance accrues. Take the final tender. Confirm the order closes + plan flips to fulfilled.

  6. 6
    Check the audit log

    In the demo, refund a sale. Edit a price. Retire a unit. Then ask to see the audit log. Confirm each action shows as a line with timestamps, actor, and the before/after values. Confirm tampering with one line breaks the chain.

  7. 7
    Confirm data ownership + export

    High-ticket businesses produce high-ticket data. Confirm you can export everything (sales, units, certificates, customer records) as a single file in one click. If the system makes you email support, you are locked in.

  8. 8
    Run a real Tuesday

    Demos are choreographed. Get a 14-day trial; run a real Tuesday including one walk-in browse, one repair intake, one trade-in conversation, and one full sale with valuation. The system that fits the rhythm is the one to buy.

Glossary

Per-piece tracking
Each physically distinct unit gets its own database row, with its own serial / certificate / metadata. The opposite of “3 in stock” integer counting.
GIA / IGI / HRD
Independent gem-grading labs (Gemological Institute of America, International Gemological Institute, Hoge Raad voor Diamant). The certificate number is the canonical reference for a stone.
Layaway
An installment plan where the goods stay with the shop until the balance is fully paid. The customer makes scheduled payments; the order stays open through the plan.
Hold / Reserved
A unit pulled off the floor for a specific customer's consideration; not yet sold. The status differs from “sold” (transaction complete) and “available” (back on the floor).
Repair ticket
A service order on an existing unit (ring sizing, stone reset, chain solder). Has its own status lifecycle: intake → in-progress → ready → collected.
Insurance valuation
A printed statement, signed by the shop, attesting to a piece's replacement value at a point in time. Used by the customer's home insurance for jewellery coverage.
Trade-in / buyback
The shop accepts old gold or stones at an assessed value, credited against the new purchase. Tracked separately from regular sales for tax + reporting.
Audit log
A tamper-evident record of every state change in the system. Each entry hashes against the prior; tampering breaks the chain.
Bench tech / goldsmith
The skilled artisan who performs sizing, repair, stone setting, polish. Their work queue is the repair-ticket list.
Loose stone
A diamond, sapphire, or other gem not yet set in a piece. Stocked with its own certificate; tracked the same way as set pieces.

Frequently asked

How does the cashier pick the exact piece at the till?
Scan the SKU; the till pops a unit picker showing every available piece for that SKU with its serial. Cashier taps the one in hand. Two seconds.
What about loose stones with GIA certificates?
Each loose stone is its own unit. Certificate number, carat, cut, colour, clarity go in the unit's notes (JSON for V1; structured columns are a follow-up). The certificate PDF attaches to the unit's record.
Repair workflow — how does it work?
Customer drops a piece in. Create an order with a service SKU (cleaning, sizing, stone reset, etc.); add a note referencing the unit ID. The goldsmith's bench tablet pulls open service tickets ordered by intake time. Charges at pickup.
Layaway — does it ship with the jewellery pack?
The payment-plan primitive ships in the platform layer (used by furniture). The jewellery cashier UI for it lands in a future bump; today, manage holds with a sticker on the case and ring the deposit through the existing tender flow.
Insurance valuations — can we print one?
Yes — “Insurance valuation” is a service SKU at $75 (configurable). The receipt doubles as a printed valuation tied to the unit's serial + certificate. Stamped, signed, customer takes it to the insurer.

Ready to look at the product side of this? See the jewellery shop pack →

Open your jewellery shop in 30 seconds.

No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.