The memo that vanished

The scene

Three diamond eternity bands arrive from Stuller on memo in March. The packing slip says ninety days. The owner pulls the slip out of the box, glances at it, files it in the binder above the safe with the others, and puts the three pieces in the case.

One sells in April. The associate marks the sale on the duplicate slip in the binder. The second sells in May. The third sits. It's not bad jewellery — it's just the one that didn't find its customer. The store moves on. The slip stays in the binder.

In August, an invoice from Stuller arrives. The third band is now thirty-two days past its return window and the price is non-negotiable: the store is being billed for the piece, in full, whether it sells next week or sits there for another year. The owner walks back to the case, looks at the band, and then back at the binder. The piece had been on memo for almost six months. Nobody flagged it. The system that should have caught it — and the binder, and the staff, and the workflow around the safe — were never asked to.

How widespread it is

The failure happens behind the counter, which is why it doesn't show up on customer review sites — but it lives openly in trade press, jeweler forums, and supplier interviews. Three examples from three different platforms, three different positions in the trade, all centred on the same operational reality:

Why it persists

Most POS systems don't model consignment as a state distinct from owned inventory. A memo'd piece looks the same on the floor as a piece the store paid for — same case, same tag, same sales workflow. The slip from Stuller is filed in a binder somewhere. The dates on it are in the binder. The aging clock is in the binder. The binder is the system.

Even when there's a digital record, it's usually a free-text tag in the description field or a note on the inventory row. There's no scheduled job that checks dates, no overdue counter on a dashboard, no surfacing logic. If the owner doesn't manually pull up the binder once a month, no part of the workflow will tell them anything is wrong. The piece stays in the case earning trust-debt against the store, and the store doesn't know it.

Reconciliation is a calendar event, not a system event. "On the first of the month I go through the binder and call Stuller back about anything past 90 days." That works in a steady-state quiet shop. It does not work in a busy showroom where the first of the month is also the day three customers want repairs back, the bench has two custom jobs due, and the binder is somewhere in the back office under last quarter's supplier statements. The skipped first-of-month is the moment the memo starts vanishing.

Who pays the price

The store pays first, in real dollars: the unsold memo piece converts to an owned piece at the supplier's price, with no margin recovered, often above what the store would have set the eventual retail at if it had bought the piece outright. The bookkeeper pays in the discovery — the month-close reconciliation surfaces the new line in payables and someone has to walk the floor to find a piece that's been there so long it's stopped being interesting. The sales associate pays in not being told, at intake, that this specific piece had a clock on it. The owner pays in two ways at once: in the cost of the converted memo, and in the trust the next memo arrangement carries — Stuller's rep notices the past-due, and the next call about a new line of bands is a slightly different conversation. The store didn't lose the relationship, but it just used up some of its slack.

How Nexpura fixes it

Consignment is a first-class state on inventory in Nexpura, not a freeform tag. A piece coming in on memo is marked `is_consignment` at intake; the stock number is automatically prefixed with a C, so the consignment status is visible on every screen the piece appears on. The badge on the inventory row says "Consignment" without anyone having to remember it was on a slip somewhere.

Return-window dates are structured fields, not a number written on a paper slip. The piece's `consignment_end_date` is set at intake and used by the system, not by a calendar reminder on someone's phone. Anything past the return window is flagged in the tenant's own time zone — a piece that's overdue at 11pm Friday in Melbourne is overdue at 11pm Friday in Melbourne on the dashboard, not at midnight UTC the day before.

The /memo surface is a dedicated ledger view, separate from general inventory. Memo Out and Consignment In sit as tabs at the top. Summary cards across the top show Active Value, Commission Earned, Overdue Items, and Turnover Rate — so the owner sees the size of the problem at a glance before opening any individual record. The supplier reference on the memo-items workflow is structured, which means "how much is due back to Stuller right now" is a query the system can answer rather than a guess from the binder.