Different fields answer different questions
When reading an export, distinguish the finish identifier from a number associated with an individual item's pattern. A shortened label such as 'pattern' can conceal either meaning. Request a field definition or original source record before sorting. Do not interpret a column merely because its numbers look familiar: similar numerical values can belong to unrelated identifier systems and provide no independent visual evidence of the claimed finish.
Check a small set of records
Find two records for one weapon and finish, then compare their technical fields and inspections. Add a record for a different finish on the same weapon. This small sample helps test which column describes design and which describes individual variation. It is a diagnostic aid, not proof of the source schema. Renamed or combined fields still require documentation rather than a guess based on three rows.
Do not join tables on an ambiguous number
The error becomes particularly harmful when joining a catalog with offers. Joining on a vague 'pattern' column can attach another finish or image to a card. Use a confirmed design key for catalog identity and retain a separate offer identifier for individual listings. After joining, check complete names and several individual images. If names disagree, stop processing: an attractive price does not justify a broken association.
Label the technical record precisely
| Column | Question to resolve |
|---|---|
| Finish identifier | How the source identifies the finish |
| Pattern seed | What the individual-item number means |
| Item identifier | How one offer is distinguished |
| Display name | How its catalog association is checked |
Keep the original field key and its meaning in your notes. You may improve a display heading without discarding that key. Read the pattern review guide for visual context. Do not turn a technical identifier into a public rarity claim without separate evidence.