Should A+ copy be inside the image or in Amazon's text fields?

Inventory the information before arranging it

List the heading, explanation, measurements and labels needed for one buyer question. Identify which words have to sit beside a specific feature and which can be understood as ordinary text. For a hypothetical desk organizer, a divider label may need a visual pointer, while a sentence explaining removable compartments can sit beside the product view.

Keep exact approved wording in a separate copy record. CartVisual generates A+ visual concepts; it does not return Amazon-native text fields or editable typography layers inside the raster image. A convincing layout can help review the intended hierarchy, but it does not settle the destination’s publishing structure. Decide that structure before treating the concept as the final asset.

Give each channel of information a job

Amazon’s News_Amazon guidance recommends using module text fields and limiting embedded image text. Apply that principle to the actual module options available in your account. It supports deliberate information placement, not a promise that a particular arrangement improves ranking or sales.

These are editorial choices, not universal field names or account permissions.

Plan the concept and publishing asset separately

In A+ product pages, use approved facts to explore the product view and module sequence. Review generated text character by character. If the desired deliverable is a mostly visual asset with separate destination copy, prepare that separation in your external design workflow rather than assuming the generated lettering can be switched off or extracted as editable layers.

A concept can contain temporary copy for internal discussion, but label its purpose in the handoff. Give the publisher the approved text record and an asset suitable for the selected Amazon module. Do not ask the publisher to transcribe a tiny raster paragraph as the only authoritative version of the product description.

Use fictional organizer O4/r2 and buyer question “Will the opening fit my item?” Map image D2 to the feature view, native heading H2 to the question, native body B2 to the owner-confirmed opening description, and short embedded label L2 only to the relevant arrow when the chosen module permits and the final crop is legible. Keep the authoritative copy sheet outside D2. If the available arrangement has no suitable text field for the explanation, choose another supported arrangement or simplify the visual; do not claim that leaving the image-copy input empty guarantees text-free output.

Handle revisions as information changes

Suppose the organizer’s verified compartment width changes after a product revision. Find every place that value appears: diagram label, native body text, specification field and alternate-language copy. Update each applicable record and replace the affected asset. Editing the ordinary text alone leaves the old raster number visible; replacing the image alone may leave stale supporting copy.

Apply the same check when shortening a heading for another language. A native field and a picture may wrap or crop differently. Review the real destination preview after upload. Avoid assuming that a readable large workbench image will retain the same hierarchy once the selected module places its own text beside it.

Suppose O4/r1 said opening width 180 mm and the new owner-approved O4/r2 record says 170 mm. Replacing B2 with 170 while D2 still labels 180 is a failed handoff; updating the picture but leaving an alternate-language B1 at 180 also fails. Change the affected value and unit everywhere it is actually used, without needlessly rewriting an unchanged outer-width fact. Treat these as invented product revisions, not measured specifications. In the final destination preview, confirm both the image and native text belong to r2 before submission.

Handoff an information placement sheet

For each module, record the buyer question, selected destination module, image filename, native heading, native body and any indispensable embedded labels. Include the evidence owner for exact specifications. Mark the concept separately from the file intended for upload so an internal mockup is not published by accident.

Use the mobile reading guide to check the resulting sequence and the deliverable guide to choose visual scope. Prepare image descriptions in the destination as a separate task. The placement sheet governs where information is carried; it does not replace alternate descriptions, platform review or an actual publication check.

Amazon’s design guide favors ordinary copy over embedded image text for small-screen reading. That guidance is stronger than “any label is fine”: keep an embedded pointer label only when needed for its visual relationship and supported by the selected arrangement, then repeat essential verified information in suitable ordinary text. The separate diagram-description handoff covers the text alternative. None of the O4 placements, crops or Amazon fields has been uploaded or tested here.