A stock-exception handover should let the next shift take one safe next action without repeating work already done. “Delivery unfinished” or “check jewelry” is too vague. State the affected record, physical location, observed facts, remaining uncertainty, and the person who accepts responsibility.

Hand over exceptions, not the whole stock sheet

List work that is unfinished or cannot safely proceed: an unmatched item, an incomplete transfer, a reservation awaiting review, an unresolved count, or a sample not returned. Completed routine work belongs in its normal record, not in an ever-growing shift note that buries the actual blockers.

Prioritize cases that could cause a duplicate sale, duplicate receipt, misplaced object, or missed required follow-up. Use the real store process to set review times; do not invent a universal deadline. One named next owner is more useful than “team to investigate.”

Make each note operationally complete

  • Reference: the exception and related order, transfer, or variant.
  • Observed state: what was physically seen and what the system showed, with times.
  • Location: a findable tray, bin, cabinet, or receiving area.
  • Next action: the specific check or authorized decision still needed.
  • Do not repeat: any receipt, adjustment, or message already completed.
  • Owner and evidence: who accepts the task and where the supporting record is kept.

Separate “planned,” “clicked,” and “verified saved.” Shopify's adjustment history can help establish an actual quantity event. A staff member's intention to save a change is not the same evidence.

Work an interrupted transfer example

Suppose a hypothetical inter-store transfer contains five brooches. At handover, all five are physically in receiving tray R-2, but only three have been accepted in the system. The operator was interrupted before reviewing the other two. Nothing is reported missing, and no damage has been established.

The handover should say: “Five observed in R-2 at 4:10 p.m.; three accepted on transfer T-41; two not yet inspected or accepted. Next owner checks the two remaining units against the transfer and completes the appropriate action. Do not receive another five.” Attach the transfer reference and the count evidence.

Shopify supports partially processed transfers. A shift ending does not justify marking all units complete. If the next person finds a different physical count, preserve that new observation and investigate rather than rewriting the earlier note as though it never existed.

Walk to the location and read back the task

Where possible, show the incoming owner the actual hold or receiving area. Faire's labeled-location guidance matters most when the person searching was not there for the original event. A photograph of an unmarked tray may not identify its current location.

Ask the new owner to summarize what is already complete, what remains, and what they must not duplicate. That short readback reveals a misunderstanding before either person changes stock. It confirms responsibility, not resolution.

Use exact item references without exposing private data

A note pointing to the black tiger epaulette brooch is more precise than “large black piece,” but an actual handover also needs its exact stock record. Keep customer details, invoice attachments, and staff-sensitive information in their proper restricted systems; use references in the shared note.

Gold-tone tiger-shaped brooch with black stripe details
An exact product reference is more useful in a handover than a vague description such as the large black brooch. View the product and current options.

Retire the note only after evidence closes it

Record the completed action, result, time, and person. Link any follow-on exception rather than leaving an old warning active after the original problem is resolved. Review repeated exception types separately; a handover list is not evidence that a particular employee caused a loss.

Use the inventory-record guide for the underlying ledger. For an unresolved product identification question, the wholesale inquiry page offers a route to ask; it does not close the internal exception.

Shop the collectionBack to the journal