Choose which fields need generation
Amazon's A+ Content instructions describe opening A+ Content Manager, starting content creation, choosing a content type, and adding a module. Modules supporting the documented AI workflow display an AI Ready badge. The seller can select specific text and image fields for AI assistance instead of treating the complete A+ page as one indivisible image.
That distinction changes the creative decision. A module may need a new explanatory heading while its approved product photograph remains suitable. Another module may need a carefully documented diagram while its existing text is already correct. Generating both fields unnecessarily introduces additional material to review.
| Need | Starting route | Evidence to retain |
|---|---|---|
| New module wording | Eligible AI Ready text field | Approved product facts |
| Source-controlled diagram | External image preparation | Approved source and annotations |
| New field-level image concept | Eligible AI Ready image field | ASIN and visual comparison |
| Exact existing photograph | Upload suitable reviewed asset | Photograph identity and edition |
The existing native-text-versus-image-copy guide explains where information should appear. This article instead determines whether Amazon's field-level AI assistance or an external creative process should produce it.
Prepare the Amazon account and ASIN evidence
Amazon documents A+ Content for eligible Professional sellers with appropriate brand enrollment or assigned selling roles. Confirm access to the actual content type and AI Ready modules in the destination account; a public feature description does not establish individual account availability.
For the documented AI route, select an AI Ready module and choose Select content to generate. Select the intended text or image fields, choose Generate content, enter a brand-owned ASIN in the side panel, and initiate generation. Amazon says its process can draw on ASIN-related information and category insights.
That source description is not a guarantee that every fact, photograph, or variation will be used correctly. Record the exact receiving product, package revision, included items, and approved claims before reviewing the result.
For an external image, prepare the approved asset and identify the Amazon module field that will receive it. Keep the exact accompanying copy outside the raster file when the selected module provides appropriate native text fields. An externally created image is not automatically an editable Amazon module.
Hypothetical example: a refillable soap dispenser
Hypothetical editorial exercise. No Amazon account was accessed and no AI content was generated or submitted. A fictional seller offers dispenser D-400, a 400 mL bottle with one pump, and D-600, a 600 mL bottle with a different pump assembly. These are invented product records, not real ASINs.
The approved source for D-400 contains photograph PHOTO-D400-R2 and copy record COPY-D400-R3. Its proposed A+ module explains how the pump is removed. Within this fictional scenario, the team has an approved source photograph of the pump but wants a shorter heading.
For D-400, the editorial plan is to evaluate AI Ready assistance for the heading while retaining the approved pump image. For a separate dimension diagram, the team prefers externally prepared artwork because the exact measurement arrows and source values need direct verification.
If an AI-generated heading says that both dispenser models share the same pump, reject it: the fictional source records establish different assemblies. If a generated image depicts the D-600 pump while the module is intended for D-400, reject the image rather than attempting to fix the mismatch through adjacent text.
Neither failure is an observed Amazon result. They demonstrate why field selection and product-source reconciliation are separate decisions.
Complete the fictional evidence set before drawing the diagram: DIM-D400-R1 is the owner-approved engineering record for D-400, stating overall height including pump 220 mm and maximum bottle width 70 mm. These invented teaching values are not measurements from an AI image or specifications for a real product. An acceptable diagram labels those two dimensions and uses the correct endpoints. A height arrow stopping at the bottle shoulder, a 22 mm transcription, or an invented D-600 dimension fails this exercise even if the illustration looks convincing.
Use internal teaching identifier M-D400-01 for the module. Before a real run, replace the blank destination-ASIN entry with the actual verified D-400 ASIN; D-400 itself is not an ASIN. Record the account and content type, confirm the AI Ready badge on the chosen module, and select Heading as the only intended generation field. The external photograph and dimension diagram are not selected for this proposed operation. This selection is an intention, not proof that every other field survives subsequent editing unchanged: compare both fields again in the actual resulting module and preview.
Review the selected fields and continue through Amazon
Inspect generated text against the approved copy record and inspect generated imagery against the exact product edition. If only the heading is wrong, revise or replace that field without assuming the entire module must be regenerated. If the visual depicts a different assembly, return to the source and image choice.
After the module is prepared, Amazon documents Apply ASINs, Apply Content, and Review & submit. Approved content appears on the respective detail pages in the selected language. A generated field is therefore neither a submitted page nor proof of publication.
Use the A+ publishing handoff guide for those downstream states. Use the ASIN and media reconciliation guide when product media and catalog identity disagree.
CartVisual can help prepare external A+ visual concepts, but it does not select Amazon AI Ready fields or submit Amazon content. Its raster output also does not create editable native Amazon text fields. Hold any module whose product facts, source ASIN, or final preview remain unverified.
If the intended module lacks AI Ready, the proposed field-generation route is unavailable in that context; supply reviewed external copy or investigate the actual account/module eligibility instead of assuming a brand-enrolled account has every AI feature. If the heading is satisfactory but the photograph has changed, hold the module and restore the correct approved image before submission. If the dimension source is absent, hold that diagram rather than deriving dimensions from the generated picture. Record the resulting text/image edition and actual outcome; all rows below remain unexecuted examples.
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Destination product / ASIN / module | Approved source evidence | Selected AI fields | Proposed route | Expected condition | Actual output / observation | Decision / next action |
|---|---|---|---|---|---|---|
| D-400 / actual ASIN not recorded / M-D400-01 | COPY-D400-R3 | Heading only, if AI Ready is available | Evaluate field-level heading assistance | Describe D-400 assembly; no shared-pump claim | Not generated; record result text/edition | Hold until actual ASIN, eligibility and wording are checked |
| D-400 / actual ASIN not recorded / M-D400-01 | PHOTO-D400-R2 | Photograph not selected | Use reviewed external image | Correct D-400 image still present after module edits | Not uploaded or inspected | Compare actual field to source; hold/restore if changed |
| D-400 / actual ASIN not recorded / M-D400-01 | Owner-approved fictional DIM-D400-R1: 220 mm overall height; 70 mm maximum width | Diagram not selected | Externally prepare diagram | Height includes pump; width uses widest bottle points; units mm | Not prepared or inspected | Reject shoulder-only arrow, 22 mm typo or unsupported value |
| D-600 image proposed for D-400 module | PHOTO-D600-R1 | Not applicable | Do not substitute other pump assembly | Wrong assembly must not be represented as D-400 | Hypothetical failure case; no output observed | Keep product and image records separate |
| ENTRY TEMPLATE |
What the sources establish
- Amazon: A+ Content: Current official instructions verified for eligibility, AI Ready badges, field selection, brand-owned ASIN input, Apply ASINs, Apply Content, Review & submit, and approval-dependent publication.
- Amazon: A+ Content design guide: Official guidance for content types, supported module planning, preview, draft saving, and review. Does not establish the accuracy of AI-generated results.
Choose the least disruptive route for a changed field
The production decision is not simply “Amazon AI or another tool.” It is which field needs new material and which evidence should remain fixed. Amazon documents specific field selection in eligible AI Ready modules. Confirm the controls in the actual account; a public description does not prove that every module offers the same operation.
Illustrative field-change exercise: a brand has an approved photograph showing the correct handle on a kitchen canister. The module heading is too long for the intended reading hierarchy. The photograph is not the problem. The team proposes evaluating a shorter heading while retaining the photograph and its verified product relationship.
Record the source photograph, current heading, exact supported facts and intended replacement field. If AI Ready is available, select only the intended heading assistance through Amazon's controls. If it is unavailable in that context, prepare reviewed copy externally rather than assuming the entire module must move to another content type. Neither route should create a new handle design or imply an untested airtight claim.
After any change, compare both the targeted field and the fields intended to remain unchanged. A field-selection plan is not a substitute for inspecting the resulting module. If the photograph is replaced, restore the authorized image and repeat the preview. If the heading adds “leakproof” without evidence, reject that wording even if it fits beautifully.
Use a separate external diagram only when the task needs controlled annotation or source-specific evidence. Keep the measurement record and endpoints visible in the handoff. Do not draw a value from a generated image or treat a brand-owned ASIN as a complete substitute for current product evidence.
Pass the creative stage when the changed field meets its narrow objective, the retained fields still match their approved sources and no new unsupported claim appears. Continue through the actual Amazon product-application and review steps; this exercise has not generated, submitted or published any content. CartVisual can help develop an external visual concept when needed, but cannot operate the destination's AI Ready controls.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Amazon: A+ Content · Review date not separately recorded
- Amazon: A+ Content design guide · Review date not separately recorded
Frequently asked questions
Can I use AI Ready for one A+ text field without replacing the product photograph?
Amazon documents selecting specific text and image fields for AI generation. Confirm that the intended module is AI Ready and that its actual field controls permit the requested selection.
Does entering a brand-owned ASIN guarantee accurate AI-generated content?
No. Amazon documents the ASIN as an input to generation, not as a guarantee of factual accuracy. Review each generated field against the correct product record before applying and submitting content.