Identity control
OOPBuy variant match checklist
Most listing mistakes happen below the product-title level: color, size, batch, model, material or bundle.
Build a stable variant key
Create one line in this order: item ID / seller / model or batch / color / size system and size / material or finish / included pieces / quantity. Use the seller’s exact option language and add your own plain-English note separately.
Four checkpoints
- Discovery: capture the option represented by the spreadsheet row, not only the product family.
- Live page: select the intended option and observe whether price, image, stock or description changes.
- Order submission: compare the submitted option string with the stable variant key.
- Warehouse: use labels, visible characteristics and requested measurements to check the received item.
Size labels are not measurements
A label such as M, 42 or US 9 can represent different measurements across listings. Record the stated size system and the relevant numeric dimensions. Compare them with a similar item you own; do not convert from a label alone.
When images disagree
Seller images may show multiple colors or versions. If the selected option image, description and option text disagree, mark the variant unresolved. Ask for clarification or compare another listing rather than guessing which representation controls.
Variant questions
Can I use the product title as the variant key?
No. The title normally identifies a product family, while the purchasable option may depend on color, size, batch, finish or bundle.
What if the order record abbreviates the option?
Compare every retained identifier and ask the external service for clarification when the abbreviation could describe more than one option.
Sources and limits
The OOPBuy beginner guide provides the visible order-stage context. This checklist is an editorial control method; it cannot verify hidden materials or authenticity.