Where should the numbers in an A+ comparison chart come from?

Give every value an origin and a condition

A weight, capacity or runtime is not complete information merely because it includes a unit. Record where it came from, which model it describes and the conditions that matter. A supplier specification may include packaging weight, while your own measurement includes only the product. Those values cannot be compared as though they describe the same thing.

For a hypothetical lamp family, one runtime might be documented at low brightness and another at a different setting. Do not remove the condition to make the chart tidier. Decide whether a comparable verified value exists, whether the condition can be made clear, or whether that row should be omitted. The image generator should receive an approved comparison, not a request to invent the missing benchmark.

Normalize the meaning before arranging columns

The point is comparable meaning, not equal-looking typography. Keep the original value with the converted value in your external record so a reviewer can trace the calculation. Do not present illustrative numbers from an article as specification data.

Avoid using pictures as measurement instruments

A generated bottle height, battery icon or series of bars does not establish a numerical result. Perspective and scene scale can change apparent size, and a decorative icon can look like a measured score. Use documented dimensions or a real measurement process for specifications. Keep subjective impressions, such as a preferred appearance, separate from quantitative rows.

If the campaign includes “before and after” imagery, identify what evidence actually supports the depicted difference. A generated brighter surface is not a recorded cleaning result. Use appropriate verified material for a performance comparison, or describe the feature without pretending the image is a test. This article does not supply experimental validation for any product.

Generate the visual only after the data is approved

In A+ content, provide the approved comparison information with exact product identities and source photographs. Review each rendered digit, unit, column association and note against the external record. If the image cannot reproduce the table reliably, use the product visuals in a destination’s text-supported comparison layout or finish the chart in a suitable external editor.

The Amazon A+ design guide describes comparison content and destination restrictions. Keep a product-family comparison within the current allowed scope. Selecting an Itemlume comparison role does not validate evidence, compare live catalog data or guarantee that Amazon will approve the exported content.

Preserve a readable version and an update trigger

Keep the same approved values in readable text for review and, where supported, in the destination’s native content fields. This gives a reviewer a way to check the numbers without enlarging a raster image. It also prevents the generated visual from becoming the only surviving copy of the specification table.

Assign a source review date and an owner to the record. If a product changes, inspect the affected row, its labels and the depicted edition. A corrected spreadsheet does not automatically correct a published image. For the illustrative lamp family, replace the outdated runtime asset and inspect the destination after upload. The approval trail should make clear which actual data version the buyer is seeing.