Home / PPF Guides / Dealer comparison tables
Key takeaways
- Use the same meaning for every cell across a row.
- Show exact product names in the column headers.
- Separate the description, source and next action.
- Split technical comparisons that require another basis.
- Read across each row at the actual phone width.

What makes two product columns genuinely comparable?
Each row must ask the same question of both products. A row headed “Stated surface” can compare ultra-matte with satin; it should not compare one film’s finish with another film’s delivery promise. Begin with the customer’s decision, then include only the rows that help that person distinguish the candidates and choose a useful next step.
The filled example uses 5006 Ultra-Matte Alexander Silver and 5025 Satin Aluminum Mercury. Both are named silver candidates, and their current listings supply different surface descriptions. That makes a short appearance table useful. The question here is how the table communicates those fields; the owner’s low-gloss silver comparison handles the actual surface preference.
Why does a mixed-field table make the choice harder?
A mixed-field table makes the reader compare unrelated ideas. If the left column says “matte” and the same row on the right says “ask for a sample,” the reader has not learned whether the second film has a different surface. A column filled with slogans is equally hard to compare with a column containing specific appearance descriptions.
The deliberately disordered example below uses real product identities but arranges the field types badly. Its problem is the organization, not a defect attributed to either film. Correct it by separating the surface description, the product source and the next sample action into their own rows. A single-product showroom label can remain compact because it identifies one display; a comparison table must also make horizontal reading meaningful.
| Mixed row | 5006 column | 5025 column |
|---|---|---|
| Surface or action? | Ultra-matte | Compare a physical sample |
| Identity or surface? | 5006 | Satin low-gloss |
| Source or slogan? | Current product page | Premium appearance |
Which rows belong in a short customer-facing example?
Use the full identity, stated surface, a relevant observation to make on the physical piece, and the product destination. Keep the full name and code visible in the column header, then let the surface row say what is actually different. A sample row should explain what to examine, while the source row lets the reader open the corresponding product.
For these two silver candidates, the useful contrast is the named ultra-matte versus satin direction. An observation row can ask the reader to examine a broad panel reflection on both actual pieces. It need not turn that observation into a score. The product-identity guide solves an earlier naming problem; here, both identities are already established and the reader needs a clear comparison between them.

| Shared field | 5006 Ultra-Matte Alexander Silver | 5025 Satin Aluminum Mercury |
|---|---|---|
| Product identity | 5006 — Ultra-Matte Alexander Silver | 5025 — Satin Aluminum Mercury |
| Stated surface | Ultra-matte | Satin, low-gloss |
| Observation on the sample | Broad-panel reflection and curved area | The same broad panel and curved area |
| Sample action | Compare the exact 5006 piece | Compare the exact 5025 piece alongside it |
| Product source | 5006 current product page | 5025 current product page |
How should the four vehicle photographs support the table?
Place the photographs near the corresponding products and say which view they provide. The two 5006 Tesla views show an outdoor front-quarter composition and a more distant front view. The two 5025 vehicle views show front-quarter and rear-quarter bodywork on a street. They give the reader recognizable examples of the two named materials on cars.
Keep the images alongside the appearance discussion rather than inserting them into a row labeled “performance.” Different shoots are not a calibrated gloss test. The table’s surface wording comes from the product descriptions; the photographs show body areas a customer may wish to examine. The photo-set guide, alt-text examples and caption guide address how those individual images are selected and described.

When should a proposed row be removed or split?
Remove a row when its cells do not share a meaning, unit or relevant basis. “Thickness” and “durability” belong to different questions, even when both entries contain numbers. Likewise, a supplier’s promotional statement should not become a numerical value in the neighboring product column. A shorter table of meaningful differences is easier to use than a large table that suggests false precision.
If a technical comparison is actually needed, put it in a separate table built from the named documents and their applicable conditions. The thickness-unit guide explains one common unit distinction. The document-revision guide handles which document belongs to the product. This public appearance example stays with the small set of fields that can help the customer choose a sample.

| Proposed row | Keep, remove or split? | Reason |
|---|---|---|
| Named surface category | Keep | Both cells answer the same appearance question |
| One finish versus another delivery promise | Remove | Different property in each cell |
| Thickness versus service life | Remove | Different quantities |
| A technical property with aligned documents | Separate technical table | Units and applicable conditions need room |
| Source and sample destination | Keep as separate rows | Each has a distinct reader action |
How do the headers help someone read across the table?
Use product names as column headers and shared properties as row headers. A reader can then move horizontally from “Stated surface” to the two answers, or vertically down one product to see its complete entry. Give the table a short caption that names the comparison, so its purpose is clear even when someone reaches it separately from the preceding paragraph.
W3C WAI’s two-header guidance describes row and column header associations using the scope attribute. Its caption guidance explains how a table heading helps readers find and understand the content. Those principles inform the examples here. A simple comparison benefits from simple structure: one row meaning, two product answers, and no need to decode a nested collection of unrelated headings.
Mixed cells
Surface, identity and action appear under the same vague row.
Comparable cells
Each row asks one question of both named candidates.
Where should the product and sample links go?
Put the product destination in a source row or another clearly labeled location, and keep the sample action separate. A link to the 5006 listing answers “which product is this?” A sample route answers “what should I do next to judge the surface?” Combining both into an unlabeled “more” cell makes the purpose of the link harder to understand.
Use the product-link wording guide when naming those destinations. The sample route is useful after the customer understands the difference, while the sample request example can turn that interest into a precise request. Keep a formal installation quotation separate from this comparison: its panel scope and commercial discussion perform another job.
How should a dealer check the finished table on a phone?
Read one complete row at the actual page width, then read one product column from top to bottom. The customer should be able to keep the property label connected to both answers. If a wide technical table needs sideways movement, retain its headers and a clear scroll area; do not squeeze long entries into unreadably narrow cells just to avoid that movement.
The photo-cropping guide helps with the neighboring images, but a better crop cannot fix ambiguous table headings. Remove redundant rows, shorten sentences and separate a second decision into another table. Keep the public Color PPF browsing route available for readers who need more candidates. For professional sourcing questions, take the named products and the comparison purpose to the dealer application.
What should the reader be able to do after the table?
The reader should be able to name the difference and take the next step without interpreting a sales ranking. In this example, the outcome is understanding ultra-matte versus satin as two stated surface directions, then comparing the exact samples. The table has done its job when the customer can say which surface deserves closer examination and open the right product.
Keep the table stable while that decision is being made. If a different material enters the shortlist, replace or add its column using the same row meanings. Use a separate product-change record when a real project selection changes, and the shop’s sample-approval record when an actual piece is accepted. The comparison remains a readable choice tool, with those later decisions handled in their own records.
Continue through the NEOPPF dealer application with the two named candidates and a specific comparison purpose.
Frequently asked questions
What is the smallest useful table structure?
Give each candidate its own product column and each common question its own row. Include the stated difference, its product source and a clear next sample action.
Should the table name an overall winner?
Name the difference that matters to the reader. In the silver example, the decision is which stated surface to examine, rather than an overall performance ranking.
Can a photo replace a stated-surface entry?
Keep both roles clear. A photograph shows a vehicle view; the stated-surface entry identifies the description associated with that exact product.
What should happen to a row with unlike quantities?
Remove it from the appearance comparison or rebuild it in a separate technical table using the same property, units and applicable basis for both products.
Why keep the product source and sample action separate?
One lets the reader open the exact candidate; the other explains the next comparison step. Separate rows make both destinations easier to understand.
0件のコメント