ItemlumeA+ product pages / PRODUCTION GUIDE
Should A+ copy be inside the image or in Amazon's text fields?
Decide where each piece of A+ information should live before generating a finished visual. A sentence placed inside an image becomes pixels; a supported Amazon text field remains a separate publishing element. Use each for an appropriate job, then keep the approved wording outside the generated artwork so corrections and language changes remain manageable.
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. Itemlume 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.
| Information | Useful starting location | Reason to reconsider |
|---|---|---|
| Module heading | Supported native heading field | Image repeats the same heading unnecessarily |
| Full explanation | Supported native body field | A paragraph becomes tiny raster lettering |
| Pointer label | Beside the feature in the image | The label is unreadable after the actual crop |
| Essential specification | Accessible ordinary text as available | Only the generated diagram carries the value |
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.
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.
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.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Are words inside an Itemlume A+ image editable text fields?
No. Treat the generated output as raster artwork and retain approved copy separately.
Should every word be removed from the image?
No. A short label tied to a visible feature can be useful when readable; avoid embedding an unnecessary paragraph.
Does using native text guarantee better Amazon search visibility?
No. This workflow improves information placement and maintenance; search and sales effects are not measured here.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open A+ product pages Check pricing and credits