How should I name a product color when screens display it differently?

Start with the approved reference

Anchor the customer-facing color name to the merchant’s controlled SKU or variant record and a checked physical sample. A supplier-approved name can be that reference; for an own-brand product, identify the brand owner responsible for the catalog name. Do not rename Forest Green merely because a dramatically lit photograph looks black. If the name, sample and stock record disagree, resolve that identity conflict before publishing.

Record the reference beside the listing information: approved name, sample identifier if available, and the image set used for review. Avoid replacing a recognized name with a more dramatic description such as Black Green unless the responsible catalog owner has approved that terminology. A creative shade label can create a second color identity and make customer service, replenishment, and variant selection harder.

1. Confirm the color name in the approved SKU record against the physical sample.
2. Review the product under neutral, repeatable lighting rather than only dramatic lifestyle lighting.
3. Compare the photograph with the physical reference and identify lighting or white-balance influence.
4. Keep the approved name, then add a concise screen-variation note if the difference could affect selection.
5. Stop changing the name when the physical reference and approved SKU record agree; investigate the image instead.

Separate naming from image correction

A dark-looking image calls for image diagnosis before a new color name. Compare the original capture, edit, export and actual storefront copy. Shopify documents how embedded image profiles and storefront handling can affect displayed colors. That is one platform-specific delivery factor, not proof that every mismatch is a profile problem. Keep the approved physical reference beside the comparison and use the image-export color review.

Correct exposure, white balance, contrast, and color management only toward the physical reference. Do not brighten Forest Green until it reads as a different green merely because one storefront preview is dim. If an image cannot represent the color reliably, replace or reshoot it and keep the approved product name unchanged.

Write a useful variation note

A variation note should set a reasonable expectation without weakening the listing. For example: “Color may appear different depending on lighting and screen settings. The approved color is Forest Green.” Place it near the variant choice or image area where a buyer evaluates color, not as a substitute for a clear product photograph.

Do not use the note to excuse an avoidable mismatch. It cannot correct a black cast, colored studio light, inaccurate white balance, or an export problem. Show a neutral product view when possible, retain a physical-reference check in the production workflow, and use additional views only when they clarify the same approved color.

Review before publishing

A practical review asks whether the name, reference, and image tell the same story. It does not ask whether every device displays identical color. The pass condition is controlled consistency: the controlled SKU record and physical sample support the name, while the image is close enough to help selection and any material limitation is stated plainly.

If the image still makes the product look like a different variant after correction, stop publication and escalate for a new image or confirmation from the responsible catalog owner. Do not solve unresolved evidence by inventing a broader name such as “dark green mix.” That creates ambiguity instead of resolving the underlying color issue.

Topic-specific review