How to Create Amazon A+ Content With AI—From Product Brief to Five Verified Modules

Start with the product and the questions shoppers need answered

Collect the current listing, photographs of the exact variant, measurements, package contents, care instructions, and any records needed to support a product claim. A photograph can show a glaze colour or connector shape. It cannot establish capacity, electrical compatibility, food safety, or a fabric's composition. Record those separately.

Read the product's customer questions, relevant support enquiries, and your own return reasons to identify missing explanations. Use authorised, anonymised material. Summarise recurring questions without copying a customer's review into A+ copy. For a mug, useful questions might concern the finish, capacity, dimensions, what is included, and cleaning. For a cable, compatibility and connector details may deserve more space than the brand story.

Write a short purpose beside each proposed module. If two modules answer the same question with the same picture, combine them. If a module only repeats the listing title or a generic quality claim, replace it with information that helps someone choose or use the product.

The worked example uses a fictional indigo-drip ceramic mug, a sample product image and example specifications. The decorative background was AI-generated. The five modules are checked against those example records; they have no real ASIN and have not been submitted to Amazon. Replace the sample data and images before using the kit for a real product.

Check access and choose the content type

Amazon's A+ eligibility page describes Professional selling accounts with a Brand Representative or Reseller role for an enrolled brand, and an access route for generic products. Check the intended marketplace and product in your account before designing. For a branded ASIN, confirm the appropriate brand role. For a generic product, check its available A+ options directly; do not invent a brand association to fit a branded workflow.

Basic A+ provides image and text layouts and product comparison modules. Premium adds options such as video, hotspots and carousels; Brand Story appears in its own area. Use Basic for this tutorial. If your account exposes Premium, select its modules and specifications separately rather than resizing this example and assuming that its layout will transfer.

In A+ Content Manager, select the content type and intended language. Give the project a name that identifies the product family, marketplace, language and revision, such as mug-indigo-US-en-v02. Open each proposed module and record its image requirements, headline and body fields, and alt-text field. Those live hints take precedence over a downloaded template.

If the product or expected feature is unavailable, check the active marketplace, selling plan, brand association and permissions first. An AI tool or design subscription cannot supply missing A+ access. If only AI generation is unavailable, use the external-tool route below with the modules your account does provide.

Match each asset to an actual Amazon module

A Basic A+ page is assembled from different module types. Each type has its own image slots and text fields. A banner designed for an overlay module is not automatically an asset for a header or square-image module.

The examples below use Amazon's official standard-module reference. Its listed minimum image sizes and field limits are useful starting points; verify the selected module in your marketplace before exporting.

These are the standard-reference allowances, including spaces and punctuation. They are ceilings, not writing targets. A two-sentence care note does not need expansion to fill a 5,000-character field. The module plan records the separate image and copy requirements for the example. Other layouts, including comparisons, need their own field checks.

Prefer native fields for ordinary headings, descriptions, compatibility notes and care information. Reserve text inside an image for a diagram or label that needs a fixed position. Native text is easier to correct and localise; embedded text must be checked at the size shoppers actually see on a phone. Never assume alt text will compensate for an unreadable paragraph baked into a picture.

Complete a product brief that AI can use safely

Use the product-fact brief to keep commercial facts separate from styling instructions. Enter the product name, exact variant, quantity, included items, exclusions, specifications, care, compatible models and required qualifications. For each fact, record its source and who approved it. Leave missing values unknown.

Specify units and measurement definitions. Width with the handle is different from rim diameter. Nominal capacity may differ from comfortable fill volume. If a dimension has a tolerance, record it and describe it accurately; do not let AI convert an approximate measurement into an exact guarantee.

For variants, maintain a shared record and a separate variant record. Shared copy may cover a material or cleaning method that is identical across the family. Capacity, colour, pack count, compatible models and photographs should come from the specific variant. Before reusing a module, check every fact in it against every ASIN receiving it.

Do not paste customer identifiers, confidential supplier contracts or account credentials into a copy tool. Supply the approved product facts it needs. For certifications, preserve the permitted wording and required qualifications in the brief instead of uploading an entire confidential report and asking the model to decide what you may advertise.

Filter Amazon restrictions before checking the evidence

Read the current A+ content guidelines for your marketplace. Some wording is prohibited in A+ even when a business could substantiate it elsewhere. Evidence alone does not make a price, purchase instruction or warranty suitable for this placement.

Use this two-stage decision in the prompt and review sheet: first decide whether the content belongs in A+; then verify that it is accurate for the product. A keyword filter can flag familiar phrases, but a reviewer must also assess implications in photographs, symbols and diagrams.

Turn product facts into useful copy

Ask for one module at a time. Give the model the selected module, its live field limits, the shopper question and the approved facts. Require a source for each product statement and a separate list of suggestions it omitted. This makes a short draft easier to inspect than an entire generated detail page.

Draft ONE Basic A+ module.
Inputs: approved product brief, exact variant, selected module,
live field limits, shopper question, and brand writing sample.

Return a headline, body and descriptive image alt text.
For each product statement, identify the supporting fact.
Keep unknown information out of shopper-facing copy.
Do not infer specifications or add a new benefit from category norms.
Exclude A+ prohibited promotions, purchase instructions, shipping,
warranties, customer quotes, competitor comparisons and contact details,
even when those details exist in the brief.
List any other claim requiring a separate policy or evidence review.
Keep background ideas separate from the product photograph.

The downloadable prompt includes the same separation and a field-by-field output format. If the model returns an unsupported suggestion, delete it from the shopper draft and keep the question in your internal notes. Showing buyers a list of unverified possibilities adds confusion.

The mug's sample records support the copy below. Each module answers a separate question without adding unverified benefits.

Apply a human edit after checking facts. Replace abstract benefits with the actual feature or use instruction. Remove repeated adjectives and sentences that add no new information. A mug's colour does not need a second paragraph about a refined everyday ritual. A compatibility module does need the actual compatible models and relevant exclusions.

For alt text, describe what the image shows in concise language. For the header, an example is Indigo-band speckled ceramic mug with an amber drip and right-side handle. For the rim-and-handle close-up, describe those parts rather than repeating the full-product description. Do not fill alt text with shopping keywords or use it as a second advertising headline.

Route one: use Amazon's AI-ready modules

Amazon documents AI generation for selected A+ module text and image fields. Where available, choose a module with the AI Ready badge, select the content fields, enter the brand-owned ASIN required by that flow, and use the offered insights or your own prompt. Feature availability should be checked in the current account.

1. Create or edit the A+ project, choose the content type and add the desired module.
2. Choose the AI Ready module and the specific text or image fields to generate. For a copy-only task, keep your approved photograph.
3. Provide the required ASIN and a concise product brief where the prompt accepts it. State the exact variant and unknown fields.
4. Generate a candidate, then compare each specification, included item and claim with your brief. Reject any feature supplied only by a category insight.
5. Edit the text to fit the live field, then preview the whole module. Check the picture separately for changed labels, quantities, connectors, seams or proportions.

Category insights can suggest useful questions, such as whether a buyer needs a size comparison. They do not establish your item's dimensions. If the output invents a fact repeatedly, shorten the brief to the facts needed for that module and write the sentence manually. Repeated generation does not provide additional evidence.

If an image generation option cannot preserve a distinctive product surface or label, use the original photograph in a standard module. Amazon's creation instructions also state that Amazon owns images generated by this GenAI feature and does not permit editing them or using them outside A+ Content. Keep that route inside the Amazon workflow. For an externally generated decorative background and your own product photograph, use the next route.

Route two: draft with AI and assemble the images in Photopea

Use this route when you want to keep your own photographs and edit the design yourself, or when the account lacks the relevant AI Ready module. The steps below use Photopea as the image editor. A text model drafts the native copy; an image model may create a decorative background. You can also keep a plain background and skip image generation entirely.

Work from a completed brief

Take M01, the Standard Header Image with Text. Its job is to identify the mug variant. In the kit, open source/mug-reference.png beside the product-fact brief. For this sample, the material record says ceramic, and the image shows an off-white speckled body, indigo upper band, amber drip and right-side handle. The capacity and care record belong to later modules; this header does not need to repeat them.

Draft the native fields for M01: Standard Header Image with Text.
Headline limit: 150 characters. Body limit: 6,000.
Image alt-text limit: 100. Keep each field brief.
Shopper question: Is this the indigo-drip mug I am looking for?

Approved sample facts:
F01 Product name: Indigo drip ceramic mug.
F02 Material record: ceramic.
P01 Product image: off-white speckled body, deep indigo upper band,
one amber drip, handle on the viewer's right.

Use only F01, F02 and P01. Preserve the visible variant.
Do not add handmade, durable, comfortable, food-safe, dishwasher-safe,
microwave-safe, gift-ready or temperature-retention claims.
Exclude prices, promotions, purchase instructions and guarantees.
Return headline, body, alt text and a fact ID for each statement.
Keep unresolved questions in internal notes.

Paste this completed prompt into your copy tool. Inspect the returned fields against the image and brief. For example, an illustrative draft reading “A premium handmade mug that keeps every drink hot” would need rewriting: none of those three claims is established by the supplied records. Keep the rewrite within the supplied facts.

The reviewed copy for M01 is: headline Indigo drip ceramic mug; body Off-white speckled ceramic with a deep indigo upper band and an amber drip.; alt text Indigo-band speckled ceramic mug with an amber drip and right-side handle. The headline uses F01, the body uses F02 and P01, and the alt text describes P01. Keep these three fields in the copy sheet, outside the image file.

Create a background without inventing the product

The kit includes source/brand-background.png, so you can follow the assembly steps without generating a new image. To create your own background, use a prompt such as the one below. Check your chosen image tool's usage rights before using its output commercially.

Create a decorative background for a 970 × 600 pixel ceramic-product header.
Warm ivory texture with restrained indigo and amber accents.
Keep the right side quiet for a separate product photograph.
No cup, product, packaging, hand, person, logo, writing or watermark.
No props that could look like included accessories.
Generate only the background; do not redraw a product.

The requested size is a design instruction; inspect the actual output dimensions. A larger background can be cropped to the header ratio. Reject a background with invented lettering, product-like shapes or objects that imply extra contents. If it makes the mug hard to distinguish, use a plain light background.

Assemble and export M01

1. Open Photopea and choose File → New. Name the project m01-header-v03, set Width to 970 and Height to 600, choose Pixels, RGB mode and sRGB profile, and create it. The pixel dimensions matter for this upload; increasing DPI alone will not make a small image meet the slot requirement.
2. Choose File → Open & Place and select the decorative background. Scale and crop that layer to cover the canvas. Do not use this crop to alter the product photograph.
3. Place mug-reference.png as a separate layer. Keep its original light background as a square tile. For this layout, use a 407 × 407 px tile, centre it vertically, and leave about 39 px to the right edge. These are example placement values, not Amazon requirements.
4. Use Edit → Free Transform, keep the width/height chain linked, and scale the photograph proportionally. For the 1,254 px square source, about 32.46% produces the 407 px tile. Confirm the transform. Do not drag only one side to stretch the handle or mug body. Photopea's transform guide explains the linked controls.
5. Inspect the rim, handle, drip and foot ring against the source at full size. Keep the photograph above the background layer. Add no headline or body text to this header image; those go into Amazon's native fields. Save the editable layers with File → Save as PSD.
6. Choose File → Export as → JPG, confirm 970 × 600, and save m01-asset.jpg. Reopen the exported file and check both the product detail and file size. If it reaches 2 MB, lower JPEG quality and inspect again without reducing the image below the selected slot's minimum. Photopea's save and export guide covers these formats.
7. In A+ Content Manager, add Standard Header Image with Text, upload m01-asset.jpg to its image slot, and enter the reviewed headline, body and alt text into their corresponding fields. Save the draft and preview desktop and mobile. The background is an image layer; the copy remains editable in Amazon.

Your M01 handoff now contains an editable PSD, one 970 × 600 JPEG, and three native text fields. The kit's generated JPEG follows this layout, but its review illustration is not a Seller Central screenshot.

Finish the other four modules

For a technical diagram, labels may need to be embedded beside the parts. Export it with only verified names, measurements and relationships, then read it on a phone. Updating the copy sheet cannot correct numbers already baked into an older graphic.

The optional builder produces these four image assets, the separate copy sheet and a review board from the example records. You can complete the Photopea route without running it.

Change the plan for different products

Use the five-module mug plan as a starting point. Choose the modules around the buyer's decision, and remove any slot that cannot answer a distinct question. Use these product-specific decisions to adapt the layout.

Decide whether three, four or five modules are useful

The five-module example demonstrates five different jobs. It is not a requirement to fill five slots. Plan the page by writing down the question each module answers, then read the sequence as a buyer.

Add a steps module when a buyer must follow an order and the manual supports each illustrated step. A connector close-up is useful for recognising a plug; a steps module is useful for connecting it correctly. Do not split one obvious action across three pictures merely to fill a template.

Add a comparison when shoppers must choose between same-brand models with meaningful differences. Use identical attribute definitions across columns, such as nominal capacity rather than nominal capacity for one model and fill volume for another. If the only difference is colour, variant photos may answer the question more directly. Comparison and multi-step layouts require their own module configuration; the kit's automated size checks cover only its four listed module types.

The kit includes three- and four-module alternatives in plans/. The three-module version combines size and contents. Its checker follows the selected plan; setup instructions appear below.

Reuse content across variants only where the facts match

Use one A+ project for several ASINs only when every module is correct for all of them. For example, a shared care module does not make a page saying “350 mL” suitable for a 500 mL mug. Keep a small application sheet with one row per ASIN and columns for colour, capacity, quantity, compatibility and content revision. Before applying the project, compare its complete content with each row, including image implications.

Simple products with one SKU

Use an introduction, a meaningful close-up, size or capacity, package contents and care when all five topics matter. For a plain storage container, a lid mechanism may deserve the close-up. For a decorative object, dimensions and finish may be more useful than a long care section. Avoid repeating the same full-product picture merely to fill the page.

Electronics and compatibility-dependent accessories

Put compatibility near the beginning. Record supported model names, connector type, relevant electrical specifications and exclusions from the approved technical record. Show a real close-up of the connector or controls. Separate physical fit from supported operation: matching the shape of a port does not prove that a device supports every function.

Use a specifications module or adjacent text for values and limitations. A multi-image module can explain setup if the approved instructions contain a sequence. Do not generate a cable routing, connector pinout or operating diagram from a product photo. If compatibility is uncertain for a model, leave it out until confirmed.

Clothing, textiles and size variants

Explain how the buyer should choose the size using the approved garment or product measurements. Distinguish product measurements from body measurements and keep the stated units consistent. Use actual detail photos for weave, fastenings and construction. AI should not change the fit, transparency or colour of the fabric to make it appear more flattering.

Localise measurements and care wording carefully. If you show two unit systems, calculate and review the conversion outside the model, decide the appropriate rounding, and retain the original measurement. Reuse a fabric description across variants only when their compositions and construction match.

Bundles and multipacks

Make the count and contents explicit. Show the actual included pieces in a reviewed arrangement, with item names where identification matters. Keep decorative objects visually separate or remove them. For a two-pack, check that the header, contents module, copy sheet and applied ASIN all say two; one correct line cannot repair a contradictory picture.

Record included accessories separately from optional accessories. If a gift box exists only for a different variant, avoid using its photo in the shared content. A bundle and a single item usually require different content modules even when the core product photograph can be reused.

Several models from the same brand

A comparison module can help buyers distinguish models by size, capacity, compatibility or included components. Choose attributes that affect selection and use the same measurement definitions across columns. Mark an unknown value as missing internally; do not invent one to make the table look complete.

Apply the current A+ comparison restrictions. Use the supported same-brand products and approved attributes, with correct ASIN associations. Do not disguise competitor references as an unnamed other brand. If the products differ mainly by colour, a comparison chart may add little; a clear variant photo and selection explanation can be more useful.

Food, beauty and products with sensitive claims

Start from the approved label and instructions. Keep ingredients, quantities and directions exact, and have the responsible reviewer check any proposed certification, efficacy, health or environmental wording against the applicable category and A+ rules. A product record is not permission to include every claim it contains.

Reject generated before-and-after results, treatment promises or imagery implying an unverified outcome. If the model introduces a benefit absent from the approved wording, remove it rather than softening it with a vague qualification. Use permitted descriptive facts and instructions when the evidence does not support a broader claim.

Furniture and products requiring assembly

Explain the assembled dimensions, relevant space requirements and package contents from the engineering or owner records. Use approved assembly steps and real parts. A sequence module can show a small number of verified operations; link the internal content plan to the current manual revision so a changed fastener or step is not missed.

AI-generated diagrams can change hole positions, support structures or the number of components. Redraw from approved drawings or annotate photographs instead. State necessary tools or exclusions only when confirmed, and keep safety wording under the product owner's review.

Reflective, transparent and individually variable products

Retain real photographs when reflections, translucency, engravings or surface patterns influence the buying decision. A white edge left by a cutout can change the apparent shape of glass; a generated reflection can make a polished surface look different. Use the original photo in a tile if a clean cutout cannot be achieved.

For handmade or variable finishes, choose imagery representative of the actual offer and preserve the owner's approved variation explanation. Do not imply that every unit has an identical speckle or grain pattern. The sample mug image shows one item; it cannot establish consistency across a real production batch.

Review images, text and mobile readability together

Before submission, compare the finished page with the brief and actual product. Check each native field as well as embedded labels. Ask a reviewer to read the page without your internal notes: can they identify the variant, understand its dimensions, and tell what arrives in the box?

Amazon's A+ guidelines specify supported RGB image formats and files below 2 MB, and prohibit blurry images, watermarks and text too small to read on mobile. Export in RGB, inspect the result, and use the chosen field's dimensions. If the file is rejected, check its actual format and size rather than changing only the filename extension.

Preview desktop and mobile in A+ Content Manager. Look for cropped product details, text colliding with a native overlay, awkward line breaks, unreadable diagram labels and a sequence that changes meaning when stacked. Shorten the copy or change the module before shrinking all the text to force it into an image.

Check alt text for every image field that provides it. A source photograph used in two different crops needs descriptions appropriate to those crops. Review accessibility alongside ordinary readability; the local kit cannot establish how Amazon's final page behaves for every assistive technology.

If you introduce photorealistic AI-generated people, follow the current A+ disclosure instructions. Amazon describes the contains-synthetic-performer keyword in the image's dc:subject metadata, and an AI-generated-people option in Creative Assets that applies the metadata. The pure-background example here contains no people. Recheck the rules before adding a synthetic model or a person holding the product.

Check the draft with the review kit

The five-module review kit contains the product brief, module plan, copy exports, source assets, builder, review board and checker. Open the board, compare each module with the records, and record a decision plus a useful note. A note such as capacity checked against the current measurement record is more informative than looks good.

The claim ledger records the example's facts and copy. For your product, retain the source and policy decision for each claim. Unsupported suggestions belong in internal notes, never in shopper copy.

The checker verifies the configured module assets, record references, generated copy, selected numerical bindings and common prohibited phrases. The accompanying test record reports the actual local checks and rejected changes. It does not prove that every possible misleading statement will be detected. A sentence can use the correct number while describing the wrong thing, and an accurate photograph can imply an accessory is included.

For an automated rebuild, replace the sample records and source files, copy your chosen alternative to module-plan.json and its matching selection to selected-plan.json, then update the specifications to the live fields. Rebuild and review the exports. The selection records the intended module IDs and order, so an accidentally missing module still fails the check. If you edit a final text field or graphic after checking it, review the changed version again. Use the README for setup and the checker for optional automated checks. The checker covers the configured files and selected wording; seller review covers the actual offer and final Amazon preview.

Apply the content, submit it and check the live result

Follow the current creation instructions for your account. After adding the modules and completing preview, use Apply ASINs to select the intended products and apply the content. Inspect that list carefully, especially when a family contains different quantities or specifications.

Choose Review & submit only after the final text, assets, language and ASIN associations are correct. Retain the copy sheet and exported files for that revision. Check the project's review status in A+ Content Manager, then inspect the ordinary product detail page in the intended marketplace and language after publication.

Amazon's publishing guidance says review can take up to seven business days, with longer waits during busy periods, and approved content can take up to 24 hours to appear. Check the current instructions and project status rather than treating those windows as a guaranteed completion time. After 24 hours, inspect the applied-ASIN status: an Error entry has a Details action. If the project says Published but the content is still missing, follow the technical-issue guidance, which may require resubmission; keep the content ID, ASIN, marketplace and language for seller support.

Check every applied variant, not just the first product. Confirm that the final page displays the correct images, native text and sequence on desktop and mobile. Record the project revision and date checked. If the content is approved but missing from the detail page, follow the status and troubleshooting guidance below rather than claiming publication from the approval label alone.

Fix the symptom you can see

Use the publishing-status guidance linked above and the rejection details in the project. Keep a copy of the message and identify the affected module or field. Correct the cause before regenerating the entire page.

For wording rejection, inspect embedded image text too. Deleting a promotional sentence from the body field does not remove it from an old graphic. For variant errors, review shared modules and the full ASIN application list. Correct the source record as well as the page so the next rebuild does not restore the mistake.

Update existing A+ or remove an outdated ASIN

For an existing page, open A+ Content Manager and search by ASIN or product name. Amazon's editing instructions say to select the project and choose Edit. Replace text in the native fields; to replace a picture, remove it with X, upload the new image and add its alt text. Check the applied ASIN list and resubmit. The revision goes through moderation again, while the previous content stays on the applied detail pages until the replacement is approved.

If only some variants have changed, inspect whether the edited project should still serve all its ASINs. A changed bundle may need separate content. To rename an already submitted project, Amazon directs you to Duplicate it, name the new version, apply its ASINs and submit; retain the old revision until you have checked the new application.

When an old page must stop describing a particular offer, use the ASIN removal workflow. Edit the project, open the ASIN tab, select the affected ASIN and choose Remove, then review and submit. For large application lists, use the documented ASIN report and bulk-upload procedure. To suspend the content from all applied ASINs, select the project and use Actions → Suspend. Amazon says changes may take up to 24 hours to process; inspect the ordinary detail pages afterward.

Do not confuse replacing a picture with removing a product association. The first changes the content for its applied products; the second changes which products receive it. If an incorrect claim must be removed promptly, check the suspension/removal options rather than assuming an edited draft has already replaced the public page.

Keep the published content useful as the product changes

Recheck A+ when packaging, accessories, materials, compatibility or care instructions change. Keep a revision record tying the current photographs and copy to the current product. Retire content that still describes a discontinued bundle, and check language versions independently after an update.

For another marketplace, localise native copy, measurements and any embedded labels as a separate version. Review translations of care and compatibility instructions with the responsible product owner. A fluent translation can still change a limitation or measurement definition.

If the product is eligible for Manage Your Experiments, use the supported experiment workflow to compare A+ versions. Choose a specific change, such as replacing a repeated hero module with a compatibility explanation, and let the experiment's results guide the decision. A before-and-after sales comparison also reflects price, stock, ads, seasonality and other changes; it cannot by itself establish the A+ revision's effect.

For the final handoff, retain the approved brief, editable design, image exports, native copy, review notes and submitted ASIN list together. When a product fact changes, those files let the next editor find every affected module and verify the updated live page.