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

Give each number an origin and a meaning

An external data row should name the product edition, quantity, value, unit, source revision and relevant conditions. A weight including packaging is not the same quantity as product-only weight. A runtime without its brightness setting can omit the fact needed to understand it.

In a fictional lamp family, supplier sheet S1 lists L1 runtime as 8 h at low brightness. Sheet S2 lists L2 runtime as 6 h at high brightness. Those are invented records for this exercise. Placing 8 and 6 under an unqualified Runtime heading would erase the mismatch; calculating that L1 lasts about 33% longer would not repair it.

Resolve the basis before converting or comparing

NIST separates quantity values, numerical values and units and explains how conditions belong with the quantity rather than being hidden inside a unit symbol. This supports clear expression. It does not validate S1/S2, choose a test method or supply missing product evidence.

Keep an approved row record outside the artwork

For each proposed row, retain the original source entry and any checked conversion. Name the reviewer’s decision: comparable and approved; accurately qualified but not ranked; unresolved; or omitted. A tidy spreadsheet is not approval unless its entries have a supported basis.

Do not measure dimensions, runtime or protection from generated scenes, battery icons or decorative bars. A realistic before-and-after image is not a recorded experiment. Use product-family chart planning to choose a useful set of rows after their evidence is settled, rather than filling a layout first and inventing the blanks.

Choose a readable destination representation

Amazon describes native technical-specification and comparison modules and advises keeping text readable rather than embedding dense wording in images. Choose the actual supported destination fields for the approved values where suitable. Its comparison guidance concerns your own products and its rules exclude competitor references.

CartVisual’s Comparison or Specifications role creates visual candidates from the supplied facts. It does not fetch verified live catalog measurements. If the raster chart swaps L1 and L2, changes 0.42 to 0.24 or loses a condition, correct the output or use native text-supported content. Do not approve it because the overall chart looks professional.

Close the loop from data version to visible asset

Read every digit, unit, column name and condition in the export against the approved row record. Then review the normal destination view; a condition unreadable on mobile has not been communicated simply because it exists at full size. Keep alternative text and surrounding wording consistent with the same product identities.

If a source changes, update the affected data row and every dependent visual. Editing the source sheet does not update a previously uploaded image. Keep the source revision, approved data version, asset and destination together. No lamp runtime, mass measurement, generation or seller publication was tested for these illustrative records.