A comparison table can look complete while combining information that does not belong together. A published model specification, a configuration selected in a menu and an unanswered question have different meanings. Keeping those three kinds of information separate makes an online comparison easier to review and update.

Start with the decision the table should support. Are you choosing between two products, checking whether an option is available, or preparing questions for a retailer? A table that tries to answer every possible question often becomes difficult to maintain. Choose a short set of fields that matter to the decision and leave room for uncertainties.

Identify the exact source for each column. Record the full product-page address, the displayed model name and the date you read it. If a page offers several configurations, give the configuration its own label. A model name alone may not distinguish two versions or two combinations of options. A screenshot can preserve context, but it should accompany the source address rather than replace it.

Use a dedicated row for published facts. Copy measurements with their units and keep the original wording when a qualification matters. A dimension described as approximate should remain approximate in the table. If a value is missing, write “not stated” rather than zero. If the retailer supplies two conflicting values, record the conflict as a question instead of silently choosing one.

Put selected options in a different section. These describe a proposed configuration, not necessarily the standard product. Note the option's displayed name and whether you have merely considered it, selected it in the interface, or received written confirmation that it applies. Those are different stages. Do not present a draft selection as an accepted order.

Give unresolved questions their own column. A useful entry includes the question, the page or passage that prompted it and the date you asked it. For example: “Does the listed measurement apply to configuration B?” is clearer than “Please confirm everything.” When an answer arrives, keep the answer and its date together. Update the relevant cell while preserving enough context to understand the change.

Keep costs and timing tied to their conditions. A displayed product price may differ from a completed checkout total, and a preparation estimate describes a different stage from carrier delivery. Label figures according to what the source actually says. Do not add numbers from different configurations or combine unrelated timing estimates into a guaranteed delivery date.

A compact row template is: field; product A; product B; source and date; open question. A second section can list intended options and confirmation status. The structure is deliberately simple so that another person can inspect both the information and its origin without reconstructing a long conversation.

Finally, decide what belongs in a private record. Full delivery addresses, payment details, order identifiers and personal documents have no place in a publicly shared comparison table. Share only the product information and questions needed for the discussion. Review the table again before placing an order, because it is a working record of what you found and asked, not a substitute for the retailer's current terms or written confirmation.