When a catalog screenshot and a sample photo look different, the first question is not "which one is wrong?" It is "are these two files even showing the same version?" This article answers that directly: it is a proposed process explainer for checking whether a catalog screenshot and a sample photo refer to the same version before calling them a mismatch. It is editorial guidance, not a report of an actual 365nails event, and any customer situation below is a hypothetical example rather than a real buyer, conversation, or inspection.
The decision and the input record
The decision is narrow: on the evidence in hand, do the screenshot and the sample photo describe the same version of the item, or is the difference only a difference in version? You cannot answer that from the images alone. You need one small input record that travels with both files. Before comparing pixels, gather these fields into a single row:
- File identity: where the screenshot came from (page, date captured, who captured it) and where the sample photo came from (who shot it, when, under what lighting).
- Version markers: any style code, revision label, batch reference, or approval date printed on either file or its surrounding document.
- What is being compared: the exact element in question - color, shape, length, finish, artwork placement - named precisely rather than "looks different."
- Approval status: which version, if any, was formally approved, and against which reference.
With those fields side by side, the compare-or-call-mismatch call has something to stand on. Without them, a visual difference is simply an unexplained difference.
A proposed walkthrough (editorial guidance, not an event report)
The steps below are offered as guidance only. They describe how an operator could work through the check; they are not a record of a completed inspection or an observed internal workflow.
- Freeze the inputs first. Save the screenshot and the sample photo exactly as received, with filenames and dates, before anyone edits or re-crops them.
- Match version markers before appearance. Compare style codes, revision labels, and approval dates. If the labels disagree, record a version question first; that does not rule out a separate product quality issue.
- Normalize the comparison conditions. Note lighting, background, and angle. A photo shot under warm light against a catalog render on a white screen is not a like-for-like comparison.
- Isolate one variable at a time. Compare color, then shape, then length, then finish, then artwork. Naming one difference at a time keeps the conclusion bounded.
- Write the finding as a question or a fact, not a verdict. "Color reads warmer in the sample photo under warm light" is an observation. "Wrong color" is a conclusion the evidence may not support.
- Leave unresolved fields visibly open. If a version marker is missing from one file, mark it missing rather than guessing.
Use the walkthrough to describe the observed difference and any unresolved version question precisely. Missing information limits what the comparison can establish; it does not prevent an operator from asking for clarification or raising a suspected product issue.
Evidence to request, fields to leave open, and the limit of the conclusion
Evidence to request: the original file rather than a forwarded thumbnail; the capture date; the version or revision label tied to each file; and the approved reference for the element in question. If any of these cannot be produced, the honest output is "insufficient to compare," not "mismatch."
Fields to leave open: unknown capture conditions, missing revision labels, unstated lighting, and any element nobody photographed. These stay blank in the record rather than being filled by assumption.
The limit of the conclusion: a comparison of two files can only tell you whether those two files agree on the elements you checked. It cannot tell you which version is correct, whether production matched either file, or what a customer experienced. What remains uncertain is the version authority behind each file until an approved reference is supplied. The conclusion stays inside that limit.
From the 365 Workbench
This is where verified service facts belong, kept separate from the guidance above. For 365nails custom projects, the process includes sample approval before production, and quality-check progress appears in the project workspace. That matters here because the approved sample is the reference a screenshot or photo should be checked against. On the after-sales side, for a confirmed product quality issue, 365nails supports a refund without requiring return of the affected product; the team reviews the issue and confirms refund details. A difference between two files is not automatically a confirmed product quality issue. The version check can help explain a concern, but the verified service facts do not make this proposed check a condition for contacting the team about an issue or asking about refund eligibility. The facts above describe 365nails service terms only; they are not a template for other businesses.
Operator Move
Build the version-check row into your own review habit: when raising a difference or a concern, include the capture date, revision label and the element compared where available. If a field is missing, mark it missing and ask for clarification. This proposed record can keep the distinction between a file-version question and a product quality concern visible without delaying contact until every field is complete.


