Review Google Product Studio Videos Before They Enter Your Asset Library

01

Why Save should be treated as an approval gate

Google asks merchants to review generated Product Studio videos and save or dismiss them. A D2C brand should place its internal approval gate before that choice, not after it.

Product Studio can assemble videos from Merchant Center product imagery, uploaded images, selectable themes, branding, text, and music. It supports horizontal, vertical, and square orientations. Google recommends watching the generated preview and editing the video until the result is satisfactory. Google also describes Product Studio as experimental and warns that generated content may be inaccurate, offensive, or otherwise unsuitable. Google Merchant Center Help

Merchant Center’s Video assets area changes the operational significance of saving a video. According to Google, saved videos appear in “Your videos” and may be highlighted in organic Google results. When Merchant Center is linked to Google Ads, videos in that area are also shared with the Google Ads asset library and can be selected during campaign creation. Google Merchant Center Help

That does not mean every saved asset is immediately running as an ad. It does mean the asset becomes easier to find and reuse. Your internal process should therefore distinguish a generated preview from an approved brand asset. A draft that is visually appealing but has the wrong variant, old packaging, or unsupported copy should remain outside the approved library.

1. Approve: The exact version and format are accurate, authorized, documented, and ready for the assigned distribution scope.
2. Revise: The concept is usable, but identified inputs or outputs must be corrected and regenerated.
3. Dismiss: The output should not be distributed or reused because it is inaccurate, unsuitable, untraceable, redundant, or not reasonably repairable.

02

Create one review-log record per generated version

Do not use one record for an entire generation session. Every preview that could be saved, downloaded, dismissed, or circulated should have its own identifier and decision.

A version-level record prevents approval from leaking from one output to another. For example, a square version may be accurate while the vertical version crops the package quantity. Likewise, version 03 may contain corrected copy while version 02 remains in a download folder. A blanket note saying “video approved” cannot resolve either situation.

Use a stable identifier such as PS-[offer ID]-[orientation]-v01. Preserve the original source references rather than relying only on a final exported filename. If your team already has an AI provenance identifier, use it instead of creating a second naming system.

1. Asset ID, generation date, Merchant Center account, Product Studio history reference, and sequential version.
2. Source imagery: filenames, image URLs, feed references, or uploaded-image identifiers. Mark each source as an original feed image, uploaded image, or AI-enhanced image.
3. Mapped product: Merchant Center offer ID, internal SKU, current product title, variant, pack quantity, and market.
4. Generation settings: theme, horizontal/vertical/square format, logo source, colors, fonts, music, and any relevant visual choices.
5. Copy: exact headline, subhead, price, promotion, call to action, and disclaimer as rendered. Mark the origin as human-written, AI-suggested, or edited from an AI suggestion.
6. Governance: reviewer, review date, Approve/Revise/Dismiss decision, revision instructions, disclosure decision, approval evidence, and final status.
7. Distribution scope: Merchant Center, Google organic surfaces, Google Ads, website, named social channels, internal use only, or another specifically approved destination.

03

Google Product Studio video review checklist

Run the following checks against the rendered preview, its recorded inputs, and the current product record. Watch once at normal speed, then pause through transitions and final frames.

Google specifically recommends reviewing the generated preview and using “Edit video” to change images, text, colors, fonts, or music when necessary. Google Merchant Center Help

The checklist should be completed by someone authorized to assess both the product and the brand. A creative reviewer may detect visual artifacts but miss an obsolete formula or incorrect bundle. Route specialized claims to the appropriate internal owner rather than asking one reviewer to infer whether they are valid.

1. Source imagery: Confirm that every image belongs to the logged product and variant. Reject obsolete packaging, colors, formulas, accessories, bundle contents, or product photography that the brand cannot reuse. Preserve both original and enhanced versions when AI enhancement was used.
2. Product mapping: Match the Merchant Center offer ID, SKU, title, variant, quantity, and market to the product actually shown. Do not approve under a generic parent-product record when the creative depicts a specific variant. Google’s Video assets workflow includes product mapping and asks merchants to verify featured products. Google Merchant Center Help
3. Product representation: Check labels, packaging text, material, color, texture, dimensions, proportions, included items, and apparent quantity. Lifestyle imagery must not imply that props or accessories are included with the purchase.
4. Format: Review horizontal, vertical, and square outputs independently. Check product visibility, text size, safe placement, masks, opening context, final frame, and silent viewing. Record decisions such as “square approved; vertical revise” instead of approving the concept globally.
5. Generated copy: Transcribe every visible word. Verify spelling, capitalization, product names, quantities, prices, promotional dates, claims, qualifications, and market language. AI-suggested text requires the same substantiation and approval as human-written text.
6. Brand accuracy: Verify the current logo, logo proportions, padding, colors, typography, animation style, music, and tone. Product Studio can draw on Merchant Center branding or uploaded brand elements, but availability in the tool does not make a treatment brand-approved. Google Merchant Center Help
7. AI artifacts: Look for warped labels, invented writing, changing geometry, color shifts, flicker, duplicate objects, disappearing details, broken masks, unnatural shadows, misleading scale, or inappropriate generated material. Any artifact that could change what a shopper believes about the item blocks approval.
8. Sound: Listen for unsuitable music, abrupt edits, distracting levels, or audio that conflicts with the intended brand and product context. Also confirm that the central message remains understandable without sound.
9. Disclosure decision: Record whether the asset was created or materially edited using AI, the approved markets and placements, whether an in-product label was selected, whether the creative carries its own disclosure, and who made the decision. Google provides AI content-label settings but says using them does not by itself guarantee legal compliance. Google Ads Help
10. Reuse authorization: Assign a limited distribution scope. Saving the file does not automatically authorize unrestricted use across ads, storefronts, email, affiliates, or social channels. Google describes its Ads asset library as a place to organize and reuse creative assets, which is why the approved scope should travel with the file. Google Ads Help

04

Write revision notes that produce a testable next version

A revision request should identify the failed element, the required change, and what must be checked again. Avoid comments such as “off brand,” “fix crop,” or “needs work.”

A useful note might read: “Replace source image 03 because it shows the previous package. Regenerate the vertical format with the current image. Change the subhead to the approved wording in brief B-142. Recheck the package quantity at 00:04 and the logo clear space on the final frame.”

Product Studio lets an operator return to earlier steps, adjust inputs, and generate another preview. The regenerated output should receive a new version number and its own review record; do not overwrite the failed version or silently transfer its approval. Google Merchant Center Help

1. Name the failed frame, image, copy line, format, or setting.
2. State the replacement input or exact correction required.
3. Identify which formats must be regenerated.
4. Create a new version rather than replacing the old record.
5. Repeat all affected checks; do not review only the requested edit.
6. Link the new version to the superseded version and preserve both decisions.

05

Apply consistent decision standards

Approval should mean that a specific version is accurate and permitted for a specific use. It should not mean that the reviewer likes the concept or expects it to perform.

Approve only when the product and variant are correct, sources are traceable, copy is verified, branding is acceptable, visible AI errors have been ruled out, disclosure status is recorded, distribution scope is assigned, and a named reviewer has signed off.

Choose Revise when a defined input or treatment can be corrected. Choose Dismiss when the product is materially misrepresented, rights or provenance cannot be established, claims cannot be supported, the concept conflicts with brand standards, or the output is unsuitable for its intended placement. Google says dismissed Product Studio videos do not appear in “Your videos,” although they may remain temporarily in Product Studio history until expiration. Keep your internal dismissal reason even when the active platform view changes. Google Merchant Center Help

1. Generated
2. Under review
3. Revision requested
4. Regenerated
5. Approved
6. Saved to Merchant Center
7. Released to approved asset library
8. Distributed
9. Superseded
10. Retired

06

Keep approval, availability, and performance separate

The review log governs whether a creative is accurate, traceable, and authorized. It cannot establish whether the video will perform well in a campaign.

An asset can be approved but not yet saved. It can be saved but restricted from paid use. It can be distributed and later retired when packaging, claims, pricing, or brand standards change. Controlled statuses prevent “available in the library” from being mistaken for “approved everywhere.”

Performance metrics should be evaluated only after the relevant platform has delivered the creative. Do not add speculative performance labels such as “high-converting,” “winning,” or “best performer” during prepublication review. Those terms require recorded results and an agreed comparison method.

1. Retire or supersede the video when a depicted package, claim, price, promotion, formula, or brand element is no longer current.
2. Identify the replacement asset rather than simply deleting the old record.
3. Before activating the approved asset in a campaign or storefront, perform a separate launch QA check for destination, tracking, placement, dates, and market settings.

07

How ATIYO can preserve the review history

ATIYO can organize the brief, product context, source references, generated versions, reviewer decisions, revision notes, approval scope, final asset, and reusable learnings in one creative-strategy workflow.

The practical value is continuity: the approved file remains connected to why it was made, which product it represents, which version passed review, what was rejected, and where reuse was authorized. Teams can preserve original and revised assets instead of relying on filenames, chat threads, or memory.

ATIYO does not connect to ad accounts, buy media, calculate ROAS, or automatically know a customer’s performance. Media performance remains in the ad platform, and ATIYO preserves creative context and learnings. If a user records later results, those observations can remain associated with the creative history without turning the prelaunch review into a performance prediction.

For teams that need a structured home for briefs, assets, iterations, and approvals, start a seven-day card-confirmed ATIYO trial. The workflow remains useful as a spreadsheet or database checklist even without ATIYO.