Using the A+ Comparison Chart — the cross-sell module Brand Registry sellers under-use.

Of the eight Standard modules the A+ Basic library exposes, the Comparison Chart is the one with the highest conversion impact per module slot — and the one most consistently left empty or filled in lazily. This episode is about why the chart matters, what it actually renders, the build rules, and the three cross-sell strategies that justify spending one of the seven precious module slots on it.

What the Comparison Chart actually is

The Standard Comparison Chart is a fixed-shape module: up to six product columns across, up to ten attribute rows down. The leftmost column is reserved for the current ASIN (the one whose detail page renders the chart). The other five columns each carry a different ASIN: thumbnail image, product title, a "View product" link that routes to that ASIN's detail page, and the attribute values per row.

The shopper's flow it enables is the entire point: someone reading the detail page for product A sees five sibling products in the same brand laid out alongside it, with the attributes they care about already filled in, and can click straight to any of those five sibling ASINs without going back to the SERP. Every cross-sell click that happens inside the chart is a click that did not happen on the competitor-filled "Customers also bought" rail Amazon stitches in below.

The build rules

Five hard rules govern the chart:

• Only ASINs you own can be linked. Brand Registry validates this on submission; you cannot put a competitor in the chart.
• Each linked ASIN must be in stock and Buy-Box-eligible for the link to render as a clickable "View product" button. Out-of-stock ASINs render with the link suppressed.
• Thumbnail and title are pulled live from the linked ASIN's catalogue record — not stored in the A+ project. Edits to the target ASIN's main image or title propagate into every comparison chart that links to it. You do not have to re-publish the chart.
• The attribute rows are stored in the A+ project — short text values typed into the row cells. These do not update if the underlying ASIN's attributes change. A stale row is a maintenance issue, not an automatic problem.
• Approval is per project, not per ASIN. Editing the chart triggers a fresh moderation pass on the whole A+ project. Plan batched edits.

The attribute-row order that converts

Ten rows is plenty in theory and rarely enough in practice. The order is what actually decides conversion — most shoppers scan the first three rows, glance at the next two, and ignore the rest. A stable order that holds up across most categories:

1. The headline differentiator — the single attribute that most cleanly distinguishes the products in the chart (capacity, size, target use-case). The row a shopper uses to decide which of the five is for them.
2. Material / construction — the trust beat. Premium materials in row 2 sell the rest of the chart.
3. Capacity / dimensions — the quantitative spec. Numbers, units, terse.
4. Compatibility / fit — for accessories, "passend für …" / "compatible with …" is row 4. For standalone products, use the next core feature instead.
5. Included / in the box — what the shopper actually receives. Resolves the "is the accessory included" question immediately.
6. Care / cleaning — only when relevant to the category. Otherwise drop the row.
7. Warranty / certifications — de-risk row.
8. Country of origin / brand provenance — only if it differentiates within the family.
9. Use-case / room / setting — a soft "where this fits" row.
10. Closing differentiator — the attribute the brand most wants the shopper to remember. Often a sustainability or award/test-winner attestation.

The hard rule: the same attribute row order across every comparison chart in the brand. A shopper who lands on three ASINs in a row and sees three different attribute orders cannot compare anything. Lock the order once, repeat it.

The three cross-sell strategies the chart supports

Comparison Chart belongs in every Brand Registry listing, but the which five other ASINs question has three useful answers:

• Variation-family chart — the five other children of the same parent ASIN. Use this on a parent listing or a child whose variation theme has >6 children that don't fit the variation swatches. Keeps the family coherent on a single ASIN's detail page.
• Tier-up chart — current ASIN on the left, the brand's better / bigger / premium versions of the same use-case in the other columns. Captures the upgrade shopper who landed on the entry-level ASIN. Highest impact when the entry-level ASIN gets the most search traffic.
• Use-case chart — the brand's adjacent products that complete a use-case (cookware piece + matching utensil + matching care kit). Optimised for basket-builder shoppers; lower conversion uplift per click but higher revenue per converted basket.

Choose one of the three per ASIN. Mixing all three into one chart dilutes every row.

What to put in the row cells

Row cells are short text fields with tight character limits. The rule is parallel construction across every column:

• Same units everywhere in the row. Don't mix kg and lbs, or cm and inches, even if the underlying ASIN's title uses different ones. The chart is the place to normalise.
• Same answer shape per row. Either every cell is a number, or every cell is a yes/no, or every cell is a short noun phrase. A mixed row looks like a typo.
• No marketing copy. The chart is comparison, not selling. The bullets and A+ modules above the chart do the selling; the chart confirms the decision.
• Em-dashes for "not applicable" — not empty cells. An empty cell reads as "we don't know"; "—" reads as "this attribute doesn't apply to this product."

Maintenance — the row that goes stale

The chart's hidden cost is maintenance. Every time a SKU in the family launches, refreshes, or is discontinued, every chart that lists it as one of the five comparison columns drifts out of date. The standard maintenance routine:

• Monthly audit of every A+ project's comparison chart against the live-stock list. Discontinued SKUs come off; new SKUs go in.
• Bulk rebuild after any variation family restructure (Module 5) — the chart should reflect the new family structure, not the old one.
• Attribute-row freeze. Once the row order is locked, it doesn't change. Adding row 11 means rebuilding every chart in the brand; the row order is the brand standard.

When not to use the chart

Three cases where the Comparison Chart is not the right module:

• Single-SKU brands. No five siblings to compare to. Use the slot for a Standard Single Image & Highlights or a Standard Four Image / Text Quadrant instead.
• Brands where every ASIN is functionally identical except for colour. The chart adds nothing the variation swatches don't already show. Use the slot for material / construction.
• Listings where the conversion problem is at the top of the page (CTR, main image, price). The chart sits below the fold; it helps shoppers who already scrolled. Fix the top of the page first.

What this episode hands off

The Comparison Chart is the cross-sell module. The next episode covers the other side of an A+ project: actually building one — opening a project, picking modules, drafting the stack, uploading images to spec, applying the project to ASINs and submitting for approval.