How to show a product screen without inventing its interface

Decide whether the screen identifies or demonstrates

Start with the buyer question. A desk clock might need a visible time display so the object is identifiable, while a thermostat image might be expected to explain a particular operating mode. These jobs require different evidence. A familiar looking screen is insufficient when the numbers, icons or arrangement imply controls that belong to another edition of the device.

Create a small display record outside the workbench: product revision, photographed powered state, interface language, allowed icons, approved visible values and whether those values are examples. An example should be recognizable as such in the surrounding approved explanation. Do not let an attractive generated reading become the only evidence for a measurement capability or a claimed operating condition.

Choose a screen treatment with an honest evidence burden

Use this invented clock record C9/r2 to make the display decision concrete. The approved powered photograph S1 shows segmented hours and minutes plus one alarm icon. It contains no weather icon. Time “07:30” is an example display in this exercise, not a reading taken now or a clock-accuracy test.

If the image must explain a menu or mode absent from S1, obtain its actual current screen record. A sharper display from another edition cannot supply it. For identity-only use, a documented off state is a separate possible brief; do not silently switch off a screen that the assigned question needs to explain.

Give Product images matching references

Open Product images and upload clear photographs of the actual device. Include the approved screen state among consistent views of the same product. In Product facts & requirements, describe the documented state and the details that must remain visible. Select an image role that suits the communication job rather than expecting a decorative scene to serve as technical documentation.

Review the housing before the display: bezel thickness, screen location, button count and orientation. Then examine the display separately for characters, units, symbols, decimal points and active areas. CartVisual does not operate the device or validate its software. A plausible case around an inaccurate interface remains an inaccurate product image, even when the screen occupies a small part of the frame.

Work through a hypothetical clock example

Compare candidate A with S1 in two passes. First check C9/r2’s housing and button layout. Then read each display position, colon, icon and unit. Suppose A adds a weather symbol: reject it for suggesting an unsupported function, even if “alarm clock” remains correct in the nearby text. Candidate B has the correct icon but shows “0730” in a new layout; hold it when the required display arrangement is S1’s “07:30.”

For exact readable information, use the genuine current display or approved screen artwork in an external editor, then check its alignment within the photographed bezel. Keep the actual product state and example wording visible in the handoff. Do not make up a firmware number or infer interface language from the country of the buyer. These candidates and labels are fictional; no device was operated, screen replaced or image generated here.

Handoff the screen exception explicitly

Google's merchant policy requires truthful representations of products.

Keep a rejected display crop with the source crop and identify the exact mismatch. Ask the next reviewer for a decision about interface evidence, not a general preference for realism. Record whether the final asset uses a real display, an approved sample or an off state, together with the device revision. Recheck that record when the product interface changes.

For physical connections, use the separate connection evidence guide. For lettering printed on a housing or package, consult label readability review. These checks complement screen approval but cannot substitute for it. Keep the source record and the actual delivered file together so later cropping does not turn a documented example into an unexplained apparent reading.