Finding an earring can solve a physical shortage while creating a bookkeeping duplicate. Before adding a pair back to stock, answer two separate questions: which parent unit did the component belong to, and is that parent already represented in the ledger?
The inventory worksheet covers complete-pair counting, and the receiving guide covers containment and holds. Here, the task is narrower: reconcile a found component with competing parent records, then document exactly one recovery outcome.
Keep custody separate from stock quantity
Open a custody record with a temporary reference, physical component count, found location and time, current container, and evidence references. Leave the parent link proposed or unknown until checked. This record tracks an object; it is not a new retail SKU or an extra inventory receipt.
All identifiers, quantities and records below are hypothetical. OC-17 is one clip-on earring found inside numbered sleeve SC-41/B at a photo station. Its custody row initially reads: one component; parent unresolved; held in container H2. Sleeve numbers identify this shop's internal custody records, not standardized product identifiers.
Test the competing parents
Record why each candidate remains plausible or is rejected. Do not select the parent whose balance is easiest to repair.
| Candidate | Evidence checked | Link decision |
|---|---|---|
| PAIR-41: same variant; one component retained in H2 | The original issue photo and signed custody sheet assign sleeve SC-41/B to this parent. Its separately contained counterpart is labeled SC-41/A. | Confirm only after the sleeve history and both physical components agree. |
| PAIR-42: same variant; recorded complete | Both components remain together on its identified card. Its custody record shows no component issued to the photo station. | Reject as the source of OC-17; leave the intact pair untouched. |
| PAIR-43: similar front; earlier removal recorded | Its documented fastening is a stud, unlike the found clip-on component. | Reject the variant link regardless of its missing-stock history. |
GS1's identification guidance distinguishes products and their variations. A matching product identifier is not custody evidence: two instances of the same variant can still be competing parents. Do not convert a sleeve number into a GTIN or infer pairing from a catalog image.
In this case, the reviewer verifies the SC-41 records and components and confirms PAIR-41. If sleeves had been mixed or the issue photo were insufficient, the correct result would instead be “variant consistent; individual parent unresolved.” State the missing handoff evidence and make no parent quantity correction. Appearance checks belong in the matched-pair guide, not in an invented provenance story.
Read the parent's saved history before choosing an entry
Link OC-17 to PAIR-41 in the custody record, then inspect the authoritative variant/location ledger. Shopify's adjustment history shows activity, actor, date and state-specific quantity changes. Read the saved event and resulting balance, not just a note saying “missing.”
These are alternative prior histories for the same confirmed parent, not simultaneous balances:
| Parent history | Recovery decision after verification | Duplicate to prevent |
|---|---|---|
| Held: PAIR-41 remains counted as one unavailable parent under the shop's declared unit model. | Parent quantity stays 1. After completeness, condition and release authorization are established, change the hold status through the supported process. | Do not add another pair: 1 + 1 would represent two parents when only one was restored. |
| Removed: event REM-08 reduced this parent from 1 to 0; no later recovery exists. | An authorized recovery linked to REM-08 restores one parent, 0 + 1 = 1, protected from sale until separately released. | Do not post both a reversal and a fresh receipt for the same recovery. |
| Unclear: a note reports removal but no saved event or reliable current balance is established. | Keep the confirmed physical association; leave the quantity decision pending with the stock-record owner. | Do not guess whether the correct change is zero or plus one. |
The held row explicitly records an incomplete parent, not two previously observed earrings. Both branches assume the components have custody records only, not separate stock quantities. If a component is already stocked elsewhere, reconcile that representation before applying either branch.
Shopify separates unavailable from available stock. The proposed case records and recovery branches are internal controls, not native Shopify transaction instructions. Use the store's authorized process and verify the resulting state; a physical match alone does not release stock.
Close the worked case with one linked outcome
Our case follows the held branch. Record: “OC-17 reunited with SC-41/A under PAIR-41; two components checked; parent quantity before 1, after 1; stock addition 0.” Add the evidence references, approver, saved hold-release reference and final location. PAIR-42 remains intact and PAIR-43 remains excluded; no donor pair supplies a component.
Close OC-17 as reunited, retaining its history and destination rather than deleting it. If the quantity or release entry is not confirmed saved, mark that action pending. A second operator should finish the existing event, not treat the closed physical search as authority for another addition.
Keep related reports and catalog references in their roles
A recovered item may also affect an earlier shipment report. Faire's order-issue guide explains that a report may be cancellable in the portal, or require support to update it; an unwanted replacement may need a separate cancellation request. Check the actual channel and record the outcome. Finding the component does not automatically cancel a replacement or settle a refund.
The heart clip-on drop earrings illustrate a listed pair, not the fictional incident. Their photograph does not link a loose earring to a particular parent or authorize a single-earring sale.
Use the earring collection for product references, not custody proof. A finished reconciliation identifies the component's parent, explains the quantity effect, and leaves any uncompleted action visible.