Jewelry Store Daily Operations: The 2026 Checklist

A well-run jewelry store runs on rhythm: the same opening count, the same case discipline, the same end-of-day reconciliation, done the same way by every shift whether the owner is in or not. The stores that lose pieces or discover a drawer problem three weeks late are rarely careless. They are stores where the routine lived in one person's head, and that person had a day off.

Jewelry is small, valuable and easy to move, so a missed step costs more than in most retail. A forgotten case count is not a tidiness problem; it is a $6,000 ring nobody can place for three days. This is the daily playbook, written so you can hand it to a new manager, with notes on why each step is there and where WJewel makes it faster or checkable.

Opening Checklist

Count the cases before the doors open

Pull stock from the safe, set the cases, and count them before the first customer walks in. The morning count is the baseline for the day; without it, an evening shortage could have happened any time in the last 24 hours. With barcode tags this is a piece-by-piece scan, and most stores only manage it for the high-value cases. With RFID tags a reader sees every piece in a case in seconds, so counting the whole floor every morning becomes realistic, and the count reconciles against live inventory.

Verify yesterday's close

Confirm the deposit matches the reconciled tender totals and the drawer float is right. Doing this in the morning, with fresh eyes and no customers, is how a counting error from last night gets caught the same week rather than at month end. If the close was never completed, it is the first item of the day.

Know what today has already promised

Before opening, look at three lists. Repairs due today, so the bench knows what has to be finished and the counter knows who to expect. Special orders promised this week, so anyone running late can be called before the customer calls you. And the appointment calendar, with each customer's CRM file open: what they looked at last time, what they own, what they are shopping for. Overnight web orders go into the same review; an in-store sale during the day has to come off the site at once or the piece sells twice, which is the sync the Shopify integration post covers.

The Selling Floor

Log every piece that leaves a case

Nothing comes out of a case without a record of where it went: a customer at the counter, a showing tray, the bench, a memo out to a client. The record does not need to be elaborate; it needs to exist and to be closed when the piece goes back. Most shrinkage investigations end with a piece that was shown, set down and never returned, and only a log says who had it.

Take repairs in properly, every time

A repair intake with photos, a description of the piece and its condition, a signed estimate and a target date protects both sides. Without the photo, a stone that was chipped on arrival becomes an argument at pickup. Without the date, the promise made at the counter never reaches the bench. In WJewel a repair is a transaction type at the register: photos, notes, deposit and a barcoded job bag, with status changes that text the customer. See the repair tracking guide.

Keep the CRM honest

Any conversation that includes a price, a date, a ring size or a name goes into the customer record before the associate serves the next person. "Two-carat oval, budget around $12,000, anniversary in October" is worth more than the sale that did not happen today, because it becomes the follow-up call in September. Recorded wish lists get followed up; the ones in a notebook do not.

Closing Checklist

Reconcile every tender, by drawer

Close each register separately and reconcile cash, card, financing and gift-card tenders against what the system recorded. Reconciling by drawer and by salesperson, rather than one store total, turns "we were $40 short" into "drawer two was $40 short on the afternoon shift", a question one person can answer.

Run the exception report

Voids, refunds, unusual discounts, price overrides and no-sale drawer opens are the transactions that hide problems. Read the day's list every day. A single void is nothing; the same associate voiding one ticket every closing shift is a pattern you only see if somebody looks. Per-user permissions on voids, refunds and overrides shorten the list before it is printed.

Final count, then sign off

Count the cases again before they go into the safe and investigate any variance right then, while the people who worked the floor are still in the building. A piece missing at 6pm with the whole team present is usually found in ten minutes: check the showing log, the bench, the repair envelopes and the day's sales for a piece rung under a similar SKU. The same piece missing at 9am tomorrow is a police report. Then lock up, set the alarm and record who closed.

The Weekly Rhythm

Some things produce noise if checked daily but a mess if skipped for a month. Once a week, on the same morning, review memo aging in both directions, repair aging against promised dates, the oldest inventory on the floor, and the associate numbers: sales per hour, average ticket and close rate. The KPI guide explains each, and the memo tracking post covers the memo review.

A Worked Example: What the Routine Catches

Say a store carries 1,800 pieces at an average cost of $900, roughly $1.6 million on the floor, and hand-counts the high-value cases daily and everything else quarterly. A $2,400 pendant goes missing from a fashion case in early March. Nobody notices until the June count, when it is one of a dozen variances and the trail is three months cold. Run the same store with a morning and evening RFID count of every case: the pendant is flagged the evening it goes missing, the showing log says who had it out at 3pm, and it turns up at the bench where it went for a chain swap. The difference is fifteen minutes a day that the software makes cheap enough to actually do.

Where WJewel Fits

Most of the checklist is human discipline. What the point of sale does is make each step fast enough to happen and recorded well enough to check: RFID counts against live inventory, reconciliation by drawer and salesperson, per-user permissions on voids, refunds and overrides, and repairs, layaways and special orders that carry their dates so the morning review is a report rather than a memory. The owner can pull the day's numbers on the iOS and Android apps, or ask Ask AI "what did we void yesterday".

FAQs

How long does a WJewel open/close take?
A full-store RFID count takes minutes rather than the hours a hand count takes, and reconciling a drawer is a few minutes per register. The rest, reading the exception report, reviewing the day's promises and locking up, is the human part and depends on the routine, not the software.

Can I enforce the checklist in WJewel?
The parts that live in the system are enforced by the system: per-user permissions control who can void, refund or override a price, each drawer has to be reconciled to close the day, and RFID counts reconcile against live inventory and flag missing pieces. The paper or tablet checklist is still yours to run; the reports are how you confirm it was.

Run Your Store on Rails

Request a Free WJewel Demo →