This is editorial guidance, not a report of an actual event. It describes a process an operator could work through; it does not describe an observed 365nails workflow, a real buyer conversation, an inspection, or a measured outcome. Where a buyer appears below, it is a hypothetical example.
The decision and the input record
The specific decision is this: when an operator adds a nail reference image to a working file, what record must travel with it so that later readers can tell where the image came from, when it was captured, and how far it may be relied on. The input record is the image itself plus a small set of attached fields тАФ source, capture date, and a plain statement of what the image does and does not show.
The trap is that a good photograph feels like a specification. A styled shot can make a finish, a length, or a shape look settled when the image was never intended to define any of those things. The input record is what keeps that boundary visible, which is also the point of the weekly theme: keep unverified details visible rather than smoothing them away.
A proposed step-by-step walkthrough
The steps below are editorial guidance тАФ a proposed practice, not a record of something that happened.
- Open a record before the image lands. Create one row or one caption block per image with required fields: source, capture date, and status. Do not add the image until those fields exist.
- Name the source concretely. Record where the image came from in terms a later reader can check тАФ the supplier or catalog it arrived with, or the internal shoot it belongs to. Avoid vague labels like "supplier photo" with no further trace.
- Record the capture date, and say what kind of date it is. If the date is the shoot date, record it as a shoot date. If it is the date the file was received, record it as a received date. Do not let one stand in for the other.
- Write one line on scope. State plainly what the image is evidence of тАФ for example, that a style and finish were offered at the time of capture тАФ and what it is not evidence of.
- Mark the record as reference, not specification. Label the image as visual reference. Any figure the image appears to suggest тАФ width, length, quantity тАФ is treated as unverified until confirmed separately.
- Leave a visible gap rather than a guess. If the source or date is unknown, type "unknown" and keep the field open. A blank or invented value hides the uncertainty; a written "unknown" keeps it visible.
- Re-check the record when the image is reused. If the image moves into a new document, carry the record with it and restate the date it was captured, so a stale reference does not drift into a current claim.
Evidence to request, fields to leave open, and the limit
The observable evidence to request, when an image record matters to a decision, is modest and checkable: the source name, the capture or received date, and a photo with a labeled width reference if size is in question. These are things a reader can look at and verify.
Some fields should stay open. If the source cannot be traced, or the date is genuinely ambiguous, or the image shows no scale, those gaps belong in the record as open items тАФ not filled with a plausible number. What remains uncertain is precisely those open fields: an untraced source, an ambiguous capture date, and any dimension the image implies but does not establish.
The limit of the conclusion is the important part. A recorded source and capture date establish provenance and timing only. They do not confirm that a style is currently available, that a finish will match on another run, or that any measurement shown is accurate. The image stays a reference until separate confirmation exists.
From the 365 Workbench
Two verified service facts set the boundary for what 365nails actually offers, and neither of them turns a reference image into a specification. 365nails combines ready-stock products, custom manufacturing, packaging support, dropshipping fulfillment, and real human 1V1 video selection. Separately, 365nails offers real-person 1-to-1 video selection to compare styles, finishes and packaging and plan product choices, quantities and MOQ before ordering.
That second point matters for this process: when a still image is ambiguous, a live comparison is one way to check a style or finish rather than reading it off a photograph. It is an option for clarifying, not a step that converts a reference image into a verified spec.
Operator Move
Before an image enters a working file, add three fields тАФ source, capture date with its type, and scope note тАФ and label the image as reference. If a field cannot be filled honestly, write "unknown" and leave it open. Treat any dimension the image seems to show as unverified until a separate labeled reference or live comparison confirms it.

