The comparison chart module inside A+ content is the highest-leverage single module Amazon will let you build. After running CVR splits on 380+ A+ pages across 14 categories, the data is not subtle: a properly built comparison chart moves CVR more than the other six standard modules combined.
It's also the module that 70%+ of brands build wrong. The chart is there. It's "filled in." It's also actively losing the sale.
I've spent the last 18 months tearing these apart for clients ranging from supplements to outdoor gear. This post is the full breakdown — what the data says, what works by category, and the nine specific anti-patterns I see most often.
Why the Comparison Chart Module Outperforms Other A+ Modules
In a controlled A+ rebuild study across 87 listings where we held every other module constant and only varied the comparison chart, the median CVR delta from chart redesign was +8.4%. The next-most-impactful single module change (objection-handling text + image module) came in at +3.1%.
Three reasons the chart is structurally more powerful than every other A+ block:
- It's the only module where the shopper is doing comparative reasoning. Every other module is descriptive — features, lifestyle, brand story. The chart triggers the brain's already-active "which one of these is right for me" pattern.
- It works on the shopper closest to buying. Shoppers who reach the A+ section have already cleared title, hero, bullets, and at least one image. The chart catches them mid-decision.
- It funnels traffic back to your own catalog. Done right, the chart redirects 4–11% of shoppers to a more appropriate variant or sibling SKU you already own — instead of losing them to a back-button.
If you're going to spend a $300 design block on A+ this quarter, spend it here.
The Two Strategic Uses (Pick One)
The single biggest mistake brands make is trying to use the chart for both strategic purposes at once. There are exactly two valid plays:
Play A: Within-Brand Routing
Compare your hero SKU against 3–5 of your own variants or sibling products. The goal: catch shoppers who landed on the wrong SKU and route them to the right one before they bounce.
Best for brands with:
- 3+ variants of a similar product (e.g., size/strength tiers)
- Multiple form factors solving the same job
- A clear "good/better/best" tier
This play wins when you have catalog depth. CVR uplift from a well-built routing chart, measured at the parent ASIN level, sits at +11–18% in our dataset.
Play B: Single-SKU Feature Anchor
Compare your SKU against itself across attributes — i.e., the chart is just a structured feature grid, not a multi-product comparison. Use it when you only have one SKU in the category or when sibling SKUs are too different to compare meaningfully.
This play wins on visual hierarchy and scanability. The chart functions as a feature module dressed as a chart, which actually outperforms a standard feature module by +4–7% CVR because the grid layout is easier to parse on mobile.
What you cannot do — and 70%+ of brands try this anyway — is mix the two. You cannot list your SKU + four competitor SKUs in the chart. Amazon forbids comparison to competitor brands by name in A+ (it gets pages suppressed at scale), and the "anonymous competitor" version reads as desperate. Skip it.
The Anatomy of a Chart That Converts
After 380+ audits, the structural template I now ship by default:
- 5 columns total: hero SKU first, four sibling/variant SKUs to the right. Five is the mobile sweet spot — six causes horizontal scroll truncation on most devices in 2026.
- 5–7 rows of comparison attributes. Fewer than 5 looks lazy. More than 7 induces fatigue and shoppers stop reading at row 4.
- Row 1 is the differentiator that matters most to the buyer. Not "material." Not "color." The single attribute the shopper is most likely to filter on mentally.
- Row 2 is the differentiator that flatters the hero SKU. This is where the hero wins clearly and the others have visible gaps.
- Rows 3–6 alternate between feature attributes and use-case fits. Don't stack all features. Mix in "best for [use case]" rows — those drive routing decisions faster than spec rows.
- Last row: price tier indicator (lowest/mid/premium) — never actual dollar amounts. Amazon changes prices; your A+ doesn't.
Mobile Rendering Is Where Most Charts Die
Roughly 78% of A+ views happen on mobile in 2026. The comparison chart renders fundamentally differently on mobile vs desktop, and most charts I audit were clearly designed on a desktop monitor and never re-checked on a phone.
What breaks on mobile:
- Column headers truncate at ~14 characters. "Premium Stainless Steel Edition" becomes "Premium Stainl…" — useless. Use 2-word SKU labels max.
- Attribute icons under ~40px disappear visually. That checkmark you used at 24px? On a phone, it's a smudge. Use 60px minimum.
- Row text under 14pt becomes unreadable. Most "Comparison Chart" templates default to 11–12pt to fit more content. Bump it.
- Image thumbnails in the top header row need to be square-cropped, not rectangular. Rectangular crops introduce inconsistent row heights and the chart looks broken.
Build the chart on a phone-sized canvas. If you can't read every cell on a 6" screen at arm's length, neither can the shopper.
The 9 Anti-Patterns I See Most Often
1. The Wall of Checkmarks
Every column has a checkmark in every row. Visually, no SKU wins anything. Fix: at least 2 rows must show clear differentiation (checkmark + X, or different values). If everything is the same, you're not running a comparison chart — you're running a feature grid badly.
2. The Confusing Hero Column
Hero SKU is somewhere in the middle of the chart instead of column 1. Shopper has to hunt for the SKU they're actually on. Hero column always goes first, always gets a subtle background tint, and always has a "Your Selection" or equivalent label.
3. Attribute Inflation
12 rows of attributes because "more = better." By row 6 the shopper has tapped away. Cap at 7.
4. Real Dollar Pricing in the Chart
"$24.99" in the price row. Two problems: price changes, A+ doesn't refresh. And shoppers fixate on the cheapest column, which is usually not your hero SKU. Use tier language.
5. Spec-Sheet Brain
All rows are technical specs (weight, dimensions, material). No use-case rows. Shoppers don't reason in specs — they reason in "is this the right one for [their situation]." At least 2 of 7 rows should be use-case oriented.
6. Tiny Mobile-Killed Icons
Custom icon set designed for desktop, indistinguishable on mobile. Use simple, large, high-contrast symbols. ✓ and ✗ beat custom-illustrated icons in every mobile test I've run.
7. Inconsistent Image Crops Across Columns
One image is a lifestyle shot, the next is a pack shot, the next is a render. Chart looks unprofessional in 0.4 seconds. Use identical crop style + identical background across all SKUs in the chart.
8. The "All Bestsellers" Trap
Brand puts only its top performers in the chart. Routing fails because nothing in the chart is meaningfully different from the hero. Include at least one SKU that's clearly a "different use case, also great" — that's the route that actually converts.
9. No Visual Hierarchy
All columns identical weight, no row emphasis, gray-on-gray everywhere. Shopper's eye has nowhere to land. The hero column gets a subtle tint. The most-differentiated row gets a slightly bolder background. Three visual anchors per chart, max — but at least one.
Category-by-Category Recommendations
Different categories use the chart differently. What I'd ship by default:
Supplements / consumables: Routing play. 5 columns across strength tiers or formula variants. Row 1: serving size or strength. Row 2: primary use case ("daily," "post-workout," "sleep support"). Row 3: dietary attributes (vegan, non-GMO, etc.). 4–7 rows total.
Apparel: Routing play. 5 columns across fits/cuts. Row 1: fit type (slim, regular, relaxed). Row 2: fabric weight. Row 3: occasion. Don't try to chart sizes — sizes are a variation, not a comparison.
Kitchen / cookware: Routing play. 5 columns across set size or material. Row 1: number of pieces or capacity. Row 2: heat source compatibility (induction, gas, etc.). Row 3: cleaning method.
Pet: Routing play. 5 columns across pet size or life stage. Row 1: pet size/weight range. Row 2: life stage (puppy/adult/senior). Row 3: primary benefit.
Beauty / skincare: Feature anchor play more often than routing — formulations differ too much to chart cleanly. Use the chart as a benefit grid for a single SKU.
Single-SKU brands (any category): Feature anchor play. Don't fake comparison. Use the grid layout to break down 5–7 product attributes clearly. CVR uplift is smaller (+4–7%) but reliable.
The 6-Step Comparison Chart Audit
Run this on every existing A+ page:
- Open the listing on a phone. Scroll to the chart. Squint test — can you read column 1?
- Count differentiated rows. Fewer than 2 with clear visual differentiation? Rebuild.
- Check the first row. Is it the attribute the shopper cares about most? Or is it "material"?
- Check column 1. Is it the hero SKU with a visual tint?
- Check column count. More than 5? Chop one.
- Check pricing. Real dollar amounts? Replace with tier labels.
If the chart fails any of steps 1–4, rebuild from scratch. Tweaks won't save it.
FAQ
How often should I refresh my comparison chart? Every time the SKU lineup changes. Otherwise: at least every 12 months. Charts that reference discontinued sibling SKUs are common and embarrassing.
Can I A/B test comparison chart variants? Yes, through Manage Your Experiments — A+ comparison module is one of the supported test units. Run it. The 8.4% median uplift I cited is from these tests, not vibes.
Should the chart sit early or late in the A+ stack? Late — typically modules 5 or 6 of 7. Shoppers who reach the chart have already qualified themselves; they're in decision mode. Putting the chart at module 1 catches the wrong attention state.
What about Premium A+ comparison charts? Premium A+ unlocks larger chart modules with more visual flexibility. The structural rules above still apply. The mobile rendering pitfalls get worse with the larger Premium modules, not better — more real estate to mismanage.
How do I handle the chart if I only have one SKU? Feature anchor play. Use the chart as a structured feature grid. Don't invent fake "sibling" SKUs or compare anonymous "competitors." Both look bush-league.
If you want a chart-by-chart audit across your A+ pages — column count, mobile render, anti-pattern flags, rebuild priorities — that's something my team runs as a standalone engagement. Get in touch.