A wholesale buyer emails a photo to one colleague, a screenshot to another, and marks the sample approved in a third message. Weeks later nobody can prove which image the approval actually covered. That is the gap this article addresses — and the example is hypothetical, not a 365nails case.
The narrow decision is this: before any detail on a nail sample review is marked production-ready, require evidence that the review is linked to exactly one reference image identifier, and that the identifier resolves to the same image every reviewer sees. This is a control on record precision, not a general sourcing, launch or supplier checklist.
The failure modes hidden inside a loose reference link
Linking a sample review to an image ID looks like a filing step. It is really a claim that the review, the photo and the approval all describe one thing. When that claim is unverified, several failures stay invisible:
- Wrong-image drift. A chat thumbnail or an updated product shot replaces the original, and the review now points at a picture nobody formally reviewed.
- One ID, several pictures. A single identifier is reused for a style family, so a finish change on one variant silently inherits an old approval.
- Orphaned approvals. The review note survives but the image it referenced is deleted or overwritten, leaving no way to reconstruct what was accepted.
- Version confusion. Two near-identical images share a name, and reviewers in different time zones open different files under the same label.
These are process risks in the record itself. They are not material, safety or wear-performance claims, and nothing here should be read as a measured outcome from any past project.
Pre-shipment checks that reveal a broken reference link
Run these checks before the wording "approved as production-ready" appears anywhere near a detail:
- Open the ID from scratch. Have a second person resolve the reference image identifier independently. If two people cannot reach the same image from the same ID, the link has already failed.
- Match the review note to the image content. Confirm the review text describes the design details visible in that exact image — not a neighbour in the same folder.
- Record the image fingerprint. Capture the source URL, the identifier and a short description of what the image shows at the time of review.
- Check variant boundaries. If the identifier spans several variants, confirm each variant is separately referenced before any detail is signed off.
- Test survival in the workspace. Confirm the link still resolves inside the project workspace where the review lives, not only in one reviewer's local files.
These checks are proposed operator practice, not a described internal workflow. They are a proposed evidence trail for recording which image a review covered; they are not a verified 365nails approval requirement.
What remains uncertain
What remains uncertain, in any specific buying team, is who holds authority to change a reference image identifier after review, whether superseded images are archived or overwritten, and how quickly a discrepancy is caught. Those depend on the team's own tools and roles, and no supply of evidence here changes that.
365 Take
A reference image identifier is only useful if it is singular and stable. Treat an approval as unproven until two people can resolve the same image from the same ID and match it to the review note in front of them.
From the 365 Workbench
Two verified service facts sit behind this topic. First, 365nails custom projects include sample approval before production and quality-check progress in the project workspace. Keeping an exact image reference with a review is the editorial recommendation here; the supplied service fact does not prescribe image identifiers, archiving features or a particular approval record. Second, 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. Neither fact removes the operator's job of keeping the review link precise before sign-off.
The escalation or resolution record to retain
When a reference link breaks, keep a short resolution record rather than a trail of chat messages. It should state the reference image identifier, the image as it appeared at review, the discrepancy found, who resolved it, and which image the approval now covers. Keep that record with the review, not in a separate inbox. If a resolution ever touches a confirmed product quality issue, 365nails reviews the issue and confirms refund details. A broken reference link alone does not establish a product quality issue or eligibility for a refund.
Operator Move
Before approving any detail as production-ready, require one thing: a reference image identifier that two independent reviewers resolve to the same image, matched to the review note and recorded with the approval. If you need to discuss the process for a specific project, contact the 365nails team.

