Track a jewelry reservation as a sequence of evidenced events: request, approved allocation, active hold, and eventual sale or release. A note saying “save this for someone” is not proof that the item has been removed from other selling channels. Nor is an expiry time proof that a release actually completed.
Distinguish intention from allocation
Start a request with an internal reference, exact variant, selling unit, quantity, location, requester reference, and the person authorized to decide. Use a restricted customer record where necessary; avoid copying names, contact details, or payment information into a shared stock sheet.
Keep “requested” until the responsible person confirms both authority and available stock. A saved cart is not a substitute for that check. Faire describes saved-for-later items separately from checkout; its page does not establish a reservation guarantee for saved items.
Record the mechanism that actually protects the stock
A confirmed row should identify the inventory system record that implements the hold, the exact option and quantity affected, when it began, and the approved expiry including time zone. Also record where the physical item is kept. A pouch on a separate shelf and a system allocation solve different problems.
Shopify's current draft-order guidance says explicitly reserved, tracked units become committed; an unreserved draft leaves units available. Do not assume merely creating a draft achieves the same result. Review the saved record after the authorized action.
Shopify's inventory-state definitions also distinguish draft-order commitments from app-based reservations. Match the tracker to the actual mechanism rather than forcing every kind of hold into one platform label.
Use a small transition record
| Internal stage | Evidence needed to leave it |
|---|---|
| Requested | Approval or refusal, with an exact item match |
| Active | Saved allocation reference and confirmed quantity |
| Due for review | Current order/payment and hold state checked |
| Sold or released | Linked completed event and quantity readback |
These are proposed internal tracker stages, not new Shopify statuses. Keep a canceled request different from an active reservation that was later released. If the system action fails, retain the unresolved stage and assign someone to investigate; do not mark success because the intended expiry has passed.
Resolve the expiry race before offering the item again
In a hypothetical case, a hold expires at 2:00 p.m., while payment was completed at 1:59 p.m. and its notification is noticed at 2:02 p.m. Releasing from an old printed list could offer the same unit twice. Reopen the current order and reservation record before deciding what happens next.
Similarly, check whether another staff member extended, fulfilled, or canceled the reservation. Use the event's actual timestamp, not just the time someone read the message. Where evidence conflicts, contain the item and escalate rather than choosing the more convenient status.
The key-pendant statement necklace is an example of an exact reference that belongs on such a row. Linking it here does not create a hold or establish reservation terms.
Close both the physical and system sides
After release, confirm the hold is no longer active and the quantity is in the intended state. Return the identified item to its recorded location only after checking its condition. After a sale, link the relevant order instead of recording an unrelated manual loss. Preserve the history so the next shift can explain why availability changed.
For the broader stock-record structure, see the inventory template. For a specific product question, use the wholesale inquiry page; a conversation does not by itself establish a hold, price commitment, or fulfillment promise.