Select the receiving field before selecting a canvas
Choose the Amazon module and image field that will receive the asset, then build the visual for its current requirements. A generic square, landscape or tall output ratio is a creative planning choice. It does not establish that a particular Amazon field will accept the file or display all its information. Check the actual account and module before treating an export as upload-ready.
CartVisual can generate a complete A+ detail-page concept as one tall composite, or a selected individual visual. Neither is an editable Amazon page or a promise of separate files for every included section. The complete-page view can help agree on sequence; a destination image field may need a more focused asset with separate native copy.
Record a field-specific output brief
Ask the publisher to identify the destination marketplace, language, content type, module and exact image field. Record the dimensions, format, file-size limit and any relevant crop behavior shown in the current receiving workflow. Do not infer Premium availability from seeing another brand's page. Keep the observed requirement and check date beside the asset brief so the creative team knows what it is designing for.
Amazon's design guide distinguishes module options and recommends limiting embedded image text for mobile reading. It is useful background, but it does not remove the need to inspect the field you will actually use. Module labels and account availability can change.
Separate the information that belongs in the image from the heading and explanation that can use supported native fields. A canvas does not become suitable merely because every word fits in the master file. The relevant question is whether the receiving layout communicates the intended evidence.
Use proportions to diagnose a mismatch, not to approve an upload
Compare the visual's width-to-height ratio with the receiving field. If they differ substantially, determine whether the destination crops, scales, pads or rejects the file in that context. Do not stretch a product to force a match. Cropping may be harmless for an expendable background but unacceptable when it removes a dimension endpoint or an included accessory.
Illustrative geometry only: an internal comparison graphic is 1200 × 1200 pixels and a hypothetical receiving rectangle has a 2:1 shape. Filling that rectangle by cropping the square could remove useful content above and below; fitting the whole square could leave unused space. These invented dimensions are not Amazon module specifications. The final choice must follow the actual field's behavior and content needs.
If the task is one product detail, rebuild the composition for that detail rather than shrinking a full-page poster into the field. If it is a complete concept review, retain the tall composite as an internal reference and plan the actual destination assets separately.
Work through a measurement module
Illustrative preparation: a merchant has a tall concept showing a lamp hero, a width diagram and a brand story. The publisher needs one measurement image for a selected A+ field. Cropping the middle of the composite leaves the width arrow but cuts off its endpoints and the lamp base. Resizing the entire poster keeps everything but makes the measurement nearly unreadable.
The team creates a focused measurement brief using the owner-approved lamp width and a source view showing the true widest points. The image contains the relevant product silhouette and clearly related annotation; the selected native text fields carry the supporting explanation where available. The brand story remains a different task.
The actual export is then checked against the receiving field. If the destination crops the diagram, the team revises the composition and repeats the preview. It does not solve a missing endpoint by changing the stated dimension or stretching the lamp. If no valid measurement source exists, the diagram remains held regardless of canvas size.
Inspect the exported file and the destination preview
- Open the actual downloaded file and confirm dimensions, format and revision against the output brief.
- Check product identity, wording, digits, units and annotation endpoints against authorized sources.
- Load the asset in the selected destination field through the authorized publisher's workflow.
- Inspect desktop and mobile previews for crop, hierarchy and text readability without zooming to rescue the design.
- Record the actual preview result separately from submission or approval status.
Pass the asset stage when the received file satisfies the observed field requirements and preserves the essential information in the real preview. Hold it when any requirement is unknown or a crop removes necessary evidence. Passing this stage is not proof of publication, policy acceptance or shopper comprehension across every device.
Keep a reusable brief, not a universal export rule
Store the chosen module/field, observed requirements, asset filename and copy record together. If the module, account context or language changes, revisit the brief rather than assuming the same canvas remains correct. A translated heading may require a different information allocation even when the image dimensions are unchanged.
Preserve the uncropped source separately from the upload edition. If the publisher later needs a different field, the team can return to the approved evidence and recompose it deliberately. Repeatedly cropping an already cropped export can remove context and make it harder to identify which annotation or product edge was lost.
In CartVisual A+ product pages, choose the individual visual or complete concept that matches the task and inspect the displayed output and quote before generation. Workspace planning generally requires sign-in. Continue with native versus embedded copy and the publishing handoff for the separate downstream decisions. CartVisual does not automatically upload the asset, create Amazon text fields or guarantee review approval.