Record variant, color, size and quantity before QC comparison.

Two QC sets can show the same product name and still describe different evidence targets. One may be black in size M; another may be charcoal in size L. A third may be a two-piece bundle whose thumbnail shows only the main item. If those option fields are not recorded before comparison, precise-looking observations can be attached to the wrong target.

This QC variant record is designed for already-found listings and inspection material. FindQC can help surface product and QC research, but it does not place the order, operate the warehouse, select a variant or execute a return. The buyer-selected agent handles those transaction steps. The record here makes the buyer's intended option and the evidence option explicit before any handoff.

1. Treat option identity as a separate evidence problem

A listing identity answers “which commercial page?” Variant identity answers “which exact selection on that page?” A matching item ID does not settle color, labelled size, quantity, version, bundle or custom text. Conversely, translated option names can differ while still referring to the same source choice. The method therefore stores both the original value and the reviewer’s normalized interpretation.

Define the decision target before opening the most attractive QC image. If the intended purchase is a navy hoodie, size L, one unit, with no added lining, those are not incidental notes. They are constraints. A measurement from size M can help formulate a sizing question, but it cannot be filed as the measurement of size L. A close-up from a black option may show construction, but it cannot settle whether the navy color is correct.

2. Build one canonical QC variant record

Use a stable header containing source URL or item ID, seller or store when shown, capture date and a short buyer reference. Beneath it, create one row each for product variant, color, labelled size, quantity, bundle or included parts, and any version-specific field. Electronics may need model, plug and voltage. Shoes may need colorway, tagged size and pair quantity. A garment may need fit name, lining or graphic option.

Add a “decision relevance” column. A tiny seller code may be informational, while shoe size and plug type are required. This column stops a reviewer from spending equal effort on every detail. It also makes conflict handling consistent: a required-field conflict blocks product-specific comparison; a preference conflict may simply be noted; an informational difference may have no effect.

Do not use “same as listing” as a value. It hides what the listing said at the time. Copy the exact text into the source-value field, then translate or normalize in a separate field. This preserves an audit trail if the option menu changes later.

3. Preserve original wording before normalizing it

Option text can include seller shorthand, machine translation, punctuation, color codes and bundle counts. Preserve the original characters where possible. A normalized entry such as “dark blue” is useful for comparison, but it should never overwrite “藏青” or a seller code such as “N03.” Keeping both lets another reviewer see whether two labels are truly equivalent or merely assumed to be.

Normalize units and field names, not unsupported meaning. Convert a clearly labelled EU 42 into a comparison column if needed, while retaining EU 42 as the source value. Do not convert a generic “XL” into a body measurement. Do not call “coffee” brown without recording that the mapping is editorial. If an option name is ambiguous, mark it unresolved and preserve the full selection path.

Color deserves particular restraint. Warehouse lighting, exposure, compression and displays can alter appearance. Record the selected color name independently from the photographed appearance. A photo can support “the received item appears cooler than the neutral reference in this frame,” but not a definitive color mismatch when the source names or lighting are unresolved.

4. Record quantity, bundles and included parts explicitly

Quantity is often lost because the listing thumbnail shows one object even when the option sells a pair, set or multi-pack. Record order quantity and units per selected option separately. Two orders of a three-piece option equal six pieces, not two. If the bundle wording is unclear, do not infer the contents from promotional images.

Use an included-parts list when completeness matters. For shoes, a pair is the product quantity while spare laces or a box are included parts. For electronics, the main device, plug, cable and adapter may be separate fields. For a bag, strap, pouch, lock and dust cover may each need a line. Mark whether each part is seller-stated, visible in QC or not shown.

A packaging photo is not automatically proof of every included part. The record should say “box visible” or “strap visible,” not “complete package,” unless every required component is identifiable. This wording makes a later targeted photo request far easier.

5. Attach every QC observation to an option row

Each image set, measurement or video should carry the variant state it actually supports. Add the QC record ID or file group, evidence date, visible label, associated seller or item ID and confirmed option fields. If size is not visible, the record does not acquire a size because the listing target has one. Keep listing claims and QC observations in separate columns.

Then classify the relationship: exact option, partial option match, contextual only or conflict. Exact means all required variant fields agree and none conflict. Partial means the product source likely matches but at least one required option field is absent. Contextual means the evidence is useful only for general construction or coverage planning. Conflict means a required field disagrees.

Never let one matching field erase another conflict. The same color does not rescue a different size. The same size does not rescue a different model. Likewise, one absent field should not be described as a conflict; absence creates uncertainty, while conflict requires disagreeing evidence.

6. Resolve conflicts without rewriting the source

When listing text, order details and QC metadata disagree, preserve all three. Record the source and timestamp of each value, then ask which source represents the actual selection or received unit. An order record can show what was submitted; a photographed label can show what is on the received item; a current listing can show what the page states now. None should silently overwrite the others.

Use a conflict note with four parts: field, values, evidence strength and next question. For example: “Size — order record L; photographed neck label M; direct conflict; ask the selected agent to confirm the unit linked to this order.” This is more actionable than “wrong size?” and avoids an authenticity claim based on a label.

If a listing changes, append a dated revision. Do not edit the earlier value to match the new page. The old record may still accurately explain historical QC evidence even though it no longer describes the current option menu.

7. Compare only fields the variant match permits

After identity is established, write the comparison question at field level. Measurements may be compared only across the same labelled size or clearly stated different sizes. Color evidence should be compared only after selected names and lighting limits are recorded. Included-parts completeness needs the exact bundle. Surface construction may remain useful across colors if the model is fixed, but the limitation must be explicit.

End each comparison line with an evidence limit. “Both size L records show similar seam placement, but they are two historical units” is honest. “This item always has aligned seams” is not. The log exists to preserve what the available sample can and cannot support.

8. Audit the record before an agent handoff

Review the header, every required option, the expected quantity calculation, evidence relationships and unresolved conflicts. A second reviewer should be able to identify the intended selection and see why each QC set is exact, partial, contextual or conflicting without opening a private chat history.

A concise handoff note can now say: “Target is dark gray, size L, one unit. The available QC set matches item and color but does not show the size label, so its measurement is contextual only. Please confirm the received size label and provide the existing warehouse measurement for the exact unit.” The selected agent decides what warehouse action is available under its terms; the record simply makes the evidence gap precise.

Variant logging is intentionally mechanical. That is its strength. It prevents a polished comparison from hiding a basic identity error and leaves a dated trail when listings, options or evidence change.