How to QA product images before marketplace upload

QA a translated product image with one stop-or-release gate before upload. Compare the final file with the original, the approved target-language copy, and the current product data. Check the complete layout at listing size, confirm the file against current official marketplace requirements, and record named human approval.

This checklist reduces translation and handling errors. It does not guarantee marketplace compliance, approval, acceptance, ranking, or sales. Requirements vary, so use the current official source for the marketplace, product, and market involved.

Check translation meaning

Review should begin with a controlled package, not a file sent in chat with no context. The package should contain the untouched source image, the exact final candidate, the approved source copy, the approved target-language copy, and a product-fact sheet. Add the product or listing reference, intended market, asset ID, and names of the people responsible for language, product facts, design, and upload.

Compare every source text region with the approved target copy. Confirm that no headline, label, qualifier, footnote, or small caption has disappeared. A fluent reviewer for the intended market should check meaning, tone, spelling, punctuation, and unnatural phrasing. Give every region an ID so a correction can be traced back to the exact wording that failed.

Define the decision before review starts. Release means every applicable check has an owner and a passing result. Stop means at least one required answer is missing, a reviewer disagrees, or the final file differs from the file that was inspected. A deadline does not turn an unknown into a pass.

Verify names, numbers, and claims

Isolate every commercial fact. Compare product names, model numbers, quantities, measurements, units, sizes, materials, prices, offer wording, dates, warnings, instructions, and promotional claims with the approved data for that market. Translation is not the source of truth for those values. If a number or claim is missing from the approved product record, stop and ask the owner.

Use a manual record for the review:

1. Paste the approved source and target wording beside each region ID.
2. Mark sensitive facts and name their source.
3. Record the language reviewer's decision and date.
4. Record any qualified review needed for legal, regulated, or safety-sensitive text.
5. Recheck the final pixels after corrections are made.

Do not approve wording simply because it sounds fluent. It also has to match the intended product and the approved scope of every claim.

Inspect layout at listing size

Compare the original and candidate side by side at full size. Check that the product, color, shape, packaging, labels, background, icons, and other visual details have not changed unexpectedly. Look for missing text, duplicated text, broken letters, odd punctuation, clipped lines, uneven spacing, and text placed over an important product feature.

Then reduce the image to a realistic listing view. A line can be technically present but impossible to read once the image is displayed in context. Check the main message first, then supporting copy and qualifiers. Do not solve readability by shrinking required information beyond practical review.

Inspect the full image edges and likely crop areas. Confirm that the hierarchy still leads the eye to the intended message and product. If you used an AI image process, pay special attention to small product details and background areas that were not supposed to change. A visually polished result can still contain a subtle defect.

Confirm file requirements

Open the exact candidate selected for upload. Confirm its asset ID, product reference, language, market, version, and filename. Verify the file against current official requirements for the target marketplace. Record the source and date used. Do not copy dimensions, file limits, or content rules from an old checklist without confirming them.

The risk table is not a compliance assessment. Escalate legal, regulated, technical, or safety-sensitive questions to the appropriate qualified person. Keep a note of unresolved questions rather than rewriting them as confident claims.

Record approval before upload

Run this checklist immediately before upload:

• The untouched source and prior approved version are available.
• The final candidate has a unique asset ID and stable filename.
• Product, listing, language, market, and intended image position match the asset map.
• Every visible text region was reviewed against approved target copy.
• Names, numbers, units, sizes, materials, offers, warnings, and claims match the current source of truth.
• A fluent reviewer approved the language for the intended market.
• Required qualified reviewers approved sensitive content.
• The full image and listing-size view passed visual review.
• The product and background contain no unexplained changes.
• The current official file and content requirements were checked and logged.
• The upload operator is selecting the same file that passed QA.
• A named person recorded the release decision and date.

Follow the marketplace's current official guidance and use the controls available to the account. Preview the selected file before saving when that option is available. Afterward, inspect the listing or account view accessible to your team. Confirm the correct image, product, market, position, crop, and readable text. Record the upload result, operator, date, destination, and any screenshot or reference permitted by your process.

If the visible result fails any check, restore the prior approved image and mark the candidate as stopped. Fix the source problem, create a new version, and repeat the relevant QA. The final release record should say what was checked, who approved it, and what appeared after upload. That record is more useful than a vague filename that merely says final.