📋 Overview
You built A+ Content for your best ASINs, published it, and moved on — and left the Brand Story module empty. That module is a separate content type inside A+ Content that sits above your standard A+ modules, carries a horizontally scrolling carousel, and can be applied across your whole catalog at once.
This article explains what Brand Story is, how it differs from standard A+ Content, how to build and apply it across many ASINs efficiently, and how to test whether it actually helps conversion.
🎯 Who This Is For
🌱 Beginner sellers
- You have Brand Registry and have published basic A+ Content but have never seen the Brand Story option.
- Your detail pages read like spec sheets, and buyers have no reason to look at your other products.
- You sell in a category where competitors all have similar images and you need differentiation that isn’t price.
🚀 Advanced sellers
- You manage dozens or hundreds of ASINs and want one content asset that scales across all of them.
- You want internal cross-linking that moves shoppers between variations and complementary products.
- You want to A/B test A+ Content, including Brand Story, rather than guess at what converts.
🔑 Key Concepts You Need to Know
📄 A+ Content
Amazon’s enhanced product description area, available to brand-registered sellers. It replaces the plain-text product description with image-and-text modules. This feature was formerly called Enhanced Brand Content; that name was retired and the current name is A+ Content.
📖 Brand Story
A distinct content type you build inside the A+ Content manager, separate from a standard A+ Content submission. It renders as a carousel of cards with a background image, and appears above standard A+ modules on the detail page. Each card can link to another ASIN or to your Brand Store.
🏪 Brand Store
Your multi-page storefront on Amazon. Brand Story cards commonly link to Store sub-pages, which makes Brand Story a discovery funnel rather than just decoration.
🧪 Manage Your Experiments
Amazon’s native A/B testing tool for brand-registered sellers. Testable elements include product images, titles, bullet points, descriptions, and A+ Content including Brand Story. Amazon uses a 95% confidence level to declare a winner.
📊 Unit Session Percentage
Your conversion rate at the ASIN level — units ordered divided by sessions — reported in Business Reports. This is the metric that tells you whether detail page content changes are working.
🛠️ Step-by-Step Guide
1️⃣ Confirm eligibility and audit what you already have
A+ Content, including Brand Story, requires brand registration for the brand on the ASIN. Open the A+ Content manager in Seller Central and filter your published content. Note which ASINs have standard A+ only, which have Brand Story, and which have neither.
A good result: a simple list of ASINs grouped into “has both,” “standard A+ only,” and “no A+ content.” Most catalogs that have never touched Brand Story will have nearly everything in the middle group.
2️⃣ Decide what the Brand Story has to accomplish
Brand Story sits in the same vertical space where a shopper is deciding between you and two other offers. Pick one job for it before you design anything:
- Cross-sell — surface complementary or higher-margin ASINs that shoppers don’t find on their own.
- Trust — answer the “who is this seller” question in categories where buyers hesitate.
- Range discovery — show that a size, scent, or format the shopper wanted exists elsewhere in your line.
Trying to do all three in one carousel produces cards nobody reads.
3️⃣ Build the asset with correct, policy-safe copy
Create the Brand Story in the A+ Content manager as its own content submission. Write copy that describes the brand and the products — not the offer.
- No prices, no discount claims, no shipping speed, no “limited time,” no contact details or external links.
- No unsupported medical, safety, or superiority claims.
- Keep card text short. The carousel is scanned, not read, and text overlays on small screens truncate quickly.
Confirm the current image dimension and character requirements for each Brand Story slot inside the A+ Content manager itself — Amazon publishes the spec next to each upload field, and it varies by module.
💡 Pro Tip: Design the background image so the focal point isn’t in the middle. Mobile crops the background aggressively, and a centered product shot is the first thing to get cut.
4️⃣ Make every card link somewhere deliberate
The cross-link is the part sellers waste. Point cards at destinations you actually want traffic on:
- A Brand Store sub-page for a product family, not the Store homepage, when the shopper needs to compare within a range.
- A specific ASIN when there is one obvious next purchase.
- Avoid linking a card back to the same ASIN the shopper is already viewing.
A good result: every card in the carousel has a destination you could justify in one sentence.
5️⃣ Apply it in bulk, then verify on live pages
When you submit the Brand Story, add ASINs in bulk rather than one at a time. This is where the leverage is — one asset can cover an entire catalog, and updating it later updates every page it’s applied to.
After Amazon approves and publishes, open several live detail pages on both desktop and mobile. Check that the carousel renders, the cards scroll, and every link lands where you intended. Broken or self-referential links are the most common post-publish defect.
💡 Pro Tip: Keep a record of which ASINs a given Brand Story is applied to. When you refresh creative later, you need to know the blast radius before you republish.
6️⃣ Set your conversion baseline before you measure
Pull Business Reports for the affected ASINs and record Sessions, Detail Page Views, and Unit Session Percentage for a clean period before publish. Without a baseline you cannot tell a content effect from a seasonal one.
7️⃣ Test rather than assume
If your ASINs have enough traffic, run a Brand Story variant through Manage Your Experiments instead of debating creative internally. Amazon recommends an 8–10 week run when you set your own duration; a run-to-significance setting can sometimes reach a conclusion in as few as 4 weeks. Winners are declared at a 95% confidence level.
Common pitfall: changing the main image, the title, and Brand Story in the same week. You’ll see movement and have no idea which change caused it.
8️⃣ Review it on a schedule
Brand Story is a shared asset, which means it goes stale everywhere at once. Re-open it whenever you discontinue a linked ASIN, restructure your Brand Store, or launch a new product family. A card pointing at a dead ASIN is worse than no card.
💡 Real-World Examples
🧴 A 40-ASIN personal care brand with no cross-sell path
A mid-size seller has strong sales on two hero SKUs and almost none on the eight refill and travel-size variants. Shoppers land on the hero ASIN, buy, and never learn the rest of the line exists.
The seller builds a single Brand Story with four cards — one per product family — each linking to the matching Brand Store sub-page, then applies it to all 40 ASINs in one submission. Over the following weeks they’d watch for two things in Business Reports: sessions on the previously ignored variants, and whether hero-ASIN Unit Session Percentage holds steady rather than dipping from the added distraction.
🔧 A newer seller in a low-trust category
A seller with six ASINs in a tool accessory category competes against listings with almost identical photos. Reviews are thin because the account is young.
They use Brand Story to show manufacturing detail and warranty support in plain language — no claims they can’t substantiate — and link one card to their Brand Store. The realistic expectation isn’t a conversion jump on its own; it’s that the page stops looking like an anonymous drop-ship listing, and that they now have a controlled variable to test against later.
📦 An advanced seller consolidating fragmented content
A seller with 300 ASINs across three brands has A+ Content built ad hoc by different contractors over several years. Brand voice is inconsistent and nothing cross-links.
Rather than rewriting 300 standard A+ submissions, they build one Brand Story per brand and apply each in bulk. Directionally, the win is operational: brand presentation becomes consistent in weeks instead of quarters, and future refreshes touch three assets instead of 300.
⚠️ Common Mistakes to Avoid
❌ Treating Brand Story as decoration
Sellers fill it with a founder photo and a paragraph of mission copy, then wonder why nothing changes. It sits in prime real estate above your standard A+ modules — give it a commercial job, usually cross-sell or range discovery, and link every card accordingly.
🚫 Putting offer or shipping language in the cards
It’s tempting to write “free shipping” or “save 20% today.” Detail page content describes the product and brand, not seller-specific terms, and this kind of copy risks rejection or suppression. Put promotional messaging where Amazon intends it — coupons, deals, and price discounts — and keep Brand Story evergreen.
⚠️ Designing for desktop only
The carousel behaves differently on mobile: background images crop, text overlays truncate, and card order matters more because shoppers swipe less than you think. Preview on a phone before you apply the asset to hundreds of ASINs, and put your most important card first.
❌ Publishing to the whole catalog without a baseline
If you roll out Brand Story everywhere at once with no recorded pre-change Unit Session Percentage, you have no way to evaluate it. Either record a baseline first, or hold a control group of ASINs back for comparison, or use Manage Your Experiments on a high-traffic ASIN.
🚫 Letting links rot
Discontinued ASINs and restructured Brand Stores break cards silently across every page the asset touches. Add a link check to whatever cadence you already use for catalog housekeeping.
📈 Expected Results
Brand Story is a conversion and discovery lever, not a traffic lever. Watch these, in this order:
- Unit Session Percentage on the ASINs where you applied it, in Business Reports — the primary read on whether the content helps or distracts.
- Sessions and Detail Page Views on the ASINs your cards link to — the read on whether cross-linking is moving anyone.
- Units per order or average order value, if your cards point at complementary products.
Timing: content changes need Amazon to approve and publish first, then enough sessions to be meaningful. Low-traffic ASINs may take a month or more before the numbers mean anything. A formal experiment takes longer still — plan for Amazon’s recommended 8–10 week window unless traffic is high enough to reach significance sooner.
The operational gain is often larger than the conversion gain: one asset applied in bulk gives you consistent brand presentation and a single place to update, which is what makes A+ maintenance survivable at scale.
❓ FAQs
🤔 Can I have Brand Story and standard A+ Content on the same ASIN?
Yes. They are separate submissions and both can be live on one detail page. Brand Story renders above your standard A+ modules, so design them to complement rather than repeat each other.
🤔 Do I need Brand Registry for Brand Story?
Yes. A+ Content in all its forms is available to brand-registered sellers for the brands they’ve enrolled. Without registration you get the plain-text product description only.
🤔 How long until my Brand Story shows up after I submit it?
Amazon reviews A+ submissions before publishing, and approved content still needs time to propagate to live pages. Check the submission status in the A+ Content manager rather than refreshing the detail page, and re-verify on a live page once status shows approved.
🤔 Will Brand Story help my search ranking?
Treat it as a conversion asset, not a keyword field. A+ Content is not indexed the way your title and backend search terms are, so write it for shoppers. Any ranking benefit comes indirectly, through better conversion on the traffic you already have.
🤔 Why did my Brand Story get rejected?
The most common causes are offer or pricing language, external links or contact information, unsupported claims, references to competitors, and images that don’t meet the dimension requirements shown next to the upload field. Fix the specific flagged element and resubmit rather than rebuilding from scratch.
🤔 Can I test Brand Story against no Brand Story?
You can test A+ Content variants, including Brand Story, in Manage Your Experiments if the ASIN qualifies on traffic. If it doesn’t, the practical alternative is a holdout group: apply the asset to part of your catalog, leave comparable ASINs untouched, and compare Unit Session Percentage over the same period.